Hardware setup
BLDC Control Demo User's Guide, Rev. 6, 06/2020
2 NXP Semiconductors
2. Supported development boards
There are three supported development boards with two Kinetis KV series motor-control MCUs for
motor-control applications. The development boards and supported MCUs are shown in Table 1.
The Tower System modular development platform and the Freedom development platform are targeted
for low-voltage and low-power applications with BLDC control type. The High-Voltage Platform
(HVP) is designed to drive high-voltage (115/220 V) applications with up to 1 kW of power.
Table 1. Supported development boards
—
Platform
FRDM TWR HVP
Power stage FRDM-MC-LVBLDC TWR-LV3PH HVP-MC3PH
MCU
KV11 FRDM-KV11Z —
—
KV31 FRDM-KV31F — HVP-KV31F512
KV46 — TWR-KV46F150M HVP-KV46F150
KV58 — TWR-KV58F220M HVP-KV58F220M
KE15Z FRDM-KE15Z — —
KE18F — TWR-KE18F HVP-KE18F
KE16Z FRDM-KE16Z — —
3. Motor Control vs. SDK Peripheral Drivers
The motor-control examples use the SDK peripheral drivers to configure the general peripherals (such as
clocks, SPI, SIM, and ports). However, motor control requires critical application timing because most
control algorithms run in a 50-µs loop. To optimize the CPU load, most peripheral-hardware features are
implemented for the PWM signal generation, analog signal sampling, and synchronization between the
PWM and ADC units.
The standard SDK peripheral drivers do not support the configuration and handling of all required
features. The motor-control drivers are designed to configure the critical MC peripherals (eflexPWM,
FTM, ADC, and PDB).
It is highly recommended not to modify the default configuration of the allocated MC peripherals due to
a possible application-timing conflict. The particular mcdrv_< board&MCU >.c source file contains
configuration functions of allocated peripherals.
4. Hardware setup
The BLDC sensorless application runs on Tower System and Freedom development platforms with a
default 24-V Linix motor.
To Next Page
Loading...
Need help?
General
