• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 451 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F28335: What makes ePWM/eCAP/eQEP "enhanced" vs standard MCU peripherals?

Josel Go
Expert 7355 points

Part Number: TMS320F28335

Hi TI team,

I am working with the C2000 MCU series, specifically the TMS320F28335, and I have a question regarding the naming of its control peripherals.

I see that modules such as ePWM, eCAP, and eQEP use the "e" (enhanced) prefix. What was the original intent behind this designation?

Does "enhanced" mainly refer to improvements over earlier TI architectures, or was it intended to distinguish these peripherals from the more basic timer-based PWM/CAP/QEP modules commonly found in other general-purpose MCUs?

More specifically, what architectural features or control- and power electronics-focused capabilities make these modules different from typical MCU timer peripherals?

Any insights into the design philosophy or historical background would be greatly appreciated. Thank you!

Regards,

Josel

  • 0
    TI__Expert 5995 points

    Hi Joel,

    It was a ground-up architectural redesign targeting power electronics and motor control, and the "enhanced" label signals that transition explicitly.

    The table below summarizes the key architectural upgrades from the 281x Event Manager to the 2833x enhanced peripherals.

    Feature
    281x Event Manager
    2833x Enhanced Peripherals
    Timer/Counter width
    16-bit
    32-bit
    Capture buffers
    2-level FIFO
    4 capture buffers per channel
    Capture modes
    Limited
    Absolute time, delta time, APWM mode
    Speed measurement
    None
    Frequency + period-based, dedicated hardware
    Shaft stall detection
    None
    Built-in watchdog timer
    Phase/count error checking
    None
    Input error detection logic
    PWM dead-band
    Basic
    Adjustable leading/trailing edge, hardware-generated
    Fault protection
    Limited
    Cycle-by-cycle trip zones, latched mechanisms
    Multi-module sync
    None
    Daisy-chain synchronization scheme
    DMA access
    None
    DMA-accessible register mapping
    PWM resolution
    Standard
    High-Resolution PWM (~150 ps typical)

    The "e" prefix answers both parts of your question simultaneously:

    • Historically, it marks the replacement of the 281x Event Manager with a more capable architecture — 32-bit counters, more capture stages, dedicated speed/position hardware, and hardware fault protection 
    • Philosophically, it reflects C2000's identity as a DSC purpose-built for power electronics control, where features like dead-band generation, trip-zone protection, HRPWM, and ADC-synchronized triggering are first-class hardware requirements — not software workarounds on top of a generic timer.

    A general-purpose MCU timer gives you a counter, a compare register, and an interrupt. The C2000 enhanced peripherals give you a coordinated real-time control subsystem. 

    If you're migrating from the 281x Event Manager to the 2833x, TI's migration guide SPRAAQ7B – Migration from 281x to 2833x/2823x Control Peripherals is the most direct reference for mapping legacy EV functionality to the new peripheral architecture. And if you're exploring HRPWM specifically, the dedicated application report [9] covers the 150 ps resolution capability and its trade-offs in detail.

    Hope this helps clarify the design intent!

    Thanks,

    Ira