SPRADL7 July   2025 F28E120SC

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Key Differences Between EPWM and MCPWM
  6. 3 Time-Base Submodule Differences
    1. 3.1 Register Differences
    2. 3.2 Driverlib Differences
  7. 4 Counter-Compare Submodule Differences
    1. 4.1 Register Differences
    2. 4.2 Driverlib Differences
  8. 5 Action-Qualifier Submodule Differences
    1. 5.1 Register Differences
    2. 5.2 Driverlib Differences
  9. 6 Dead-Band Submodule Differences
    1. 6.1 Register Differences
    2. 6.2 Driverlib Differences
  10. 7 Trip-Zone Submodule Differences
    1. 7.1 Register Differences
    2. 7.2 Driverlib Differences
  11. 8 Event-Trigger Submodule Differences
    1. 8.1 Register Differences
    2. 8.2 Driverlib Differences
  12. 9 Global Load Differences
    1. 9.1 Register Differences
    2. 9.2 Driverlib Differences
  13. 10Summary
  14. 11References

4.2 Driverlib Differences

The driverlib differences between EPWM and MCPWM for the Counter-Compare Submodule are listed in Table 4-2.

Table 4-2 Counter-Compare Submodule Driverlib Differences Between EPWM and MCPWM

EPWM Function

MCPWM Function

Explanation

-

MCPWM_getCounterCompareShadowValue

Addition of memory mapped CMPx shadow registers

-

MCPWM_setCounterCompareShadowValue

Addition of memory mapped CMPx shadow registers

EPWM_getCounterCompareValue

MCPWM_getCounterCompareActiveValue

Function name change to indicate difference between active register and shadow register

EPWM_setCounterCompareValue

MCPWM_setCounterCompareActiveValue

Function name change to indicate difference between active register and shadow register

EPWM_disableCounterCompareShadowLoadMode

-

Shadow mode is not enabled or disabled on MCPWM. Only shadow load event is selected and correct active or shadow register is written to.

EPWM_getCounterCompareShadowStatus

-

Shadow register full flag replaced by memory mapped shadow register that can be read or written to by the user.