SPRZ496E October   2021  – August 2026 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1

 

  1.   1
  2.   TMS320F28003x Real-Time MCUs Silicon ErrataSilicon Revision 0
  3. 1Usage Notes and Advisories Matrices
    1. 1.1 Usage Notes Matrix
    2. 1.2 Advisories Matrix
  4. 2Nomenclature, Package Symbolization, and Revision Identification
    1. 2.1 Device and Development-Support Tool Nomenclature
    2. 2.2 Devices Supported
    3. 2.3 Package Symbolization and Revision Identification
  5. 3Silicon Revision 0 Usage Notes and Advisories
    1. 3.1 Silicon Revision 0 Usage Notes
      1. 3.1.1 PIE: Spurious Nested Interrupt After Back-to-Back PIEACK Write and Manual CPU Interrupt Mask Clear
      2. 3.1.2 Caution While Using Nested Interrupts With Repeat Block
      3. 3.1.3 I2C Slave Mode: Managing Status Flags in Applications with Long Interrupt Response Times
      4. 3.1.4 Security: The primary layer of defense is securing the boundary of the chip, which begins with enabling JTAGLOCK and Zero-pin Boot to Flash feature
    2. 3.2 Silicon Revision 0 Advisories
      1. 3.2.1  Advisory
      2.      Advisory
      3.      Advisory
      4. 3.2.2  Advisory
      5.      Advisory
      6.      Advisory
      7.      Advisory
      8.      Advisory
      9.      Advisory
      10. 3.2.3  Advisory
      11.      Advisory
      12. 3.2.4  Advisory
      13. 3.2.5  Advisory
      14.      Advisory
      15.      Advisory
      16.      Advisory
      17. 3.2.6  Advisory
      18.      Advisory
      19. 3.2.7  Advisory
      20. 3.2.8  Advisory
      21.      Advisory
      22. 3.2.9  Advisory
      23.      Advisory
      24. 3.2.10 Advisory
      25. 3.2.11 Advisory
      26.      Advisory
      27.      Advisory
      28.      Advisory
      29.      Advisory
  6. 4Documentation Support
  7. 5Trademarks
  8. 6Revision History

Advisory

ePWM: ePWM One-Shot/CBC Trip Event DCxEVTy.force Does Not Set the Trip Condition

Revisions Affected

0

Details

The DCxEVTy.force signal can be used as input for the one-shot trip events and cycle-by-cyle trip events. When setting DCxCTL[EVT1/2FRCSYNCSEL] = 1 (passes the DCxEVT signal through the async path) does not properly set the one-shot or cycle-by-cycle trip event condition and trip event is missed.

Workarounds

For devices with DCxCTL.EVT1/2FRCSYNCSEL and DCxCTL.EVT1/2LATSEL, there are two options. Otherwise, Sync Path is the only option to use for the one-shot or cycle-by-cycle trip event.

Async Path (passes the DCxEVT signal through the async path)

The following configurations must be made to latch the one-shot or cycle-by-cycle trip condition through the async path:

To Trip the PWMs, you can invert the EPWMXBAR state using XBAR_invertEPWMSignal().

  1. DCxCTL.EVT1/2FRCSYNCSEL = 1
  2. DCxCTL.EVT1/2LATSEL = 1

Sync Path (passes the DCxEVT signal through the sync path)

  1. DCxCTL.EVT1/2FRCSYNCSEL = 0