SPRUIM2H May 2020 – October 2023 AM2431 , AM2432 , AM2434 , AM6411 , AM6412 , AM6421 , AM6422 , AM6441 , AM6442
An effective PWM peripheral must be able to generate complex pulse width waveforms with minimal CPU overhead or intervention. It needs to be highly programmable and very flexible while being easy to understand and use. The EPWM unit described here addresses these requirements by allocating all needed timing and control resources on a per PWM channel basis. Cross-coupling or sharing of resources has been avoided; instead, the EPWM is built up from smaller single-channel modules with separate resources and that can operate together as required to form a system. This modular approach results in an orthogonal architecture and provides a more transparent view of the peripheral structure, helping users to understand its operation quickly.
In the further description, the letter x within a signal or module name is used to indicate a generic EPWM instance on a device. For example, output signals EPWMxA and EPWMxB refer to the output signals from the EPWMx instance. Thus, EPWM1A and EPWM1B belong to EPWM1, EPWM2A and EPWM2B belong to EPWM2, and so forth.
The EPWM module represents one complete PWM channel composed of two PWM outputs: EPWMxA and EPWMxB.
As also described in Section 12.4.3.3.1.2, Daisy-Chain Connectivity between EPWM Modules, the EPWM modules are chained together via a clock synchronization scheme that allows them to operate as a single system when required. Additionally, this synchronization scheme can be extended to the Enhanced Capture (ECAP) peripheral module. The EPWM modules can also operate stand-alone.
The device has nine instances of the EPWM modules.
Table 12-4306 shows the EPWM allocation across device domains.
Instance | Domain | |
MCU | MAIN | |
EPWM0 | - | ✓ |
EPWM1 | - | ✓ |
EPWM2 | - | ✓ |
EPWM3 | - | ✓ |
EPWM4 | - | ✓ |
EPWM5 | - | ✓ |
EPWM6 | - | ✓ |
EPWM7 | - | ✓ |
EPWM8 | - | ✓ |
Figure 12-2223 shows the EPWM module overview.