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.

TMS320F280049C: Will the DCAEVT1.sync or DCBEVT1.sync cause a Jitter on HRPWM?

Part Number: TMS320F280049C

Hi,

I want to use the HRPWM module for design. After reading the mannul I found that DCAEVT1.sync and DCBEVT1.sync can still be used in HRPWM (as shown in Fig.18-84).

But I also found :

"When high-resolution period mode is enabled, an EPWMxSYNC pulse will introduce +/- 1 - 2 cycle
jitter to the PWM (+/- 1 cycle in up-count mode and +/- 2 cycle in up-down count mode). For this
reason, TBCTL[SYNCOSEL] should not be set to 1 (CTR = 0 is EPWMxSYNCO source) or 2 (CTR =
CMPB is EPWMxSYNCO source). Otherwise, the jitter will occur on every PWM cycle with the
synchronization pulse.
When TBCTL[SYNCOSEL] = 0 (EPWMxSYNCI is EPWMxSYNCO source), a software
synchronization pulse should be issued only once during high-resolution period initialization. If a
software sync pulse is applied while the PWM is running, the jitter will appear on the PWM output at
the time of the sync pulse."

I wonder if the DCAEVT1.sync or DCBEVT1.sync cause a Jitter on HRPWM?

There will be a DCEVT.sync signal during each period (but I don't know when it will occur) and I want to use this signal to set the CTR to zero or other value (through loading the phase )

But there is:

TBPHSHR must not be used. Instead TRREM (HRPWM remainder register) must be used to mimic
the functionality of TBPHSHR."

So will the phase value loaded without jitter?

Thanks!