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.

TMS320F280049: Jitter issue with High-resolution period used for multi-phase interleaved LLC

Part Number: TMS320F280049
Other Parts Discussed in Thread: C2000WARE, TIDM-1001

Dear Champs,

I am asking this for our customer.

On F28004x TRM

http://www.ti.com/lit/ug/sprui33a/sprui33a.pdf

 

Sec 19.2.4.4.1 (Page 1856)

 

It says,

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.

In our understanding, EPWMxSYNC will introduce +-1 or 2 cycle jitters when using high-resolution period.

For multi-phase interleaved LLC, say 3-phase interleaved LLC, we are confused how we implement high-resolution period because we have to use EPWMxSYNC to sync between interleaved LLC PWM modules.

 

Do you have any comment or suggestion for us to sync between 3-phase PWM for LLC DC/DC while avoiding this jitter issue?

Even 1 clock cycle (1/100 MHz = 10 ns) leading to large output ripples is not acceptable in our application.

 

Wayne Huang

 

 

  • Hi Wayne,

    Due to the holidays, the reply from our team might be delayed. We will get back to you on 12/31/2018. Thanks.

    Regards,
    Chen
  • Wayne,

    One soution to this issue is to not issue a sync all the time. Do an initial one time sync and use global link and global load mechanisms to load all the registers are the same time.

    We have used this method in 1Mhz type LLC converters.

    Note the sync is only usefull in preventing an inadvertent cycle miss due to radiation etc. It is not required all the time.

    Now, we do have some mechanisms that make use of hi-res phase shift which we demonstrate on the example

    C:\ti\C2000Ware_DigitalPower_SDK_1_02_00_00\c2000ware\device_support\f2837xd\examples\cpu1\hrpwm_deadband_sfo_v8

    Which the customer can look at if they really need the sync always, this requires some extra CPU bandwidth.
  • Manish,

    To implement one-time synchronization between multiple EPWM modules via Global Load mechanism, is this the correct procedure to use:
    - set GLDCTL[GLD] to 1 (Global Load) on all EPWMs
    - set GLDCTL[GLDMODE] to 1111 (load when GLDCTL2[GFRCLD] is triggered) on all EPWMs
    - set GLDCTL[OSHTMODE] to 1 (enable one-shot mode) on all EPWMs
    - link GLDCTL2 registers in Slave EPWMs to Master EPWM
    - write 1 to GLDCTL2[OSHTLD] in Master EPWM
    - write 1 to GLDCTL2[GFRCLD] in Master EPWM
    ?

    Does Global Load transfer TBPHS to TBCTR (including High Resolution part)?

    Thank you!
  • Hi PavelM,

    For the procedure, please take a look at the TIDM-1001 as an example which uses one time global load mechanism.

    No, the registers that will be reloaded are covered in the GLDCFG register. Please check the TRM about this register. Thanks.

    Regards,
    Chen

  • PavelM,

    I closed this post.
    If you have another question about using global reload or others, you may use "Ask a related question" or "Ask a new question".


    Wayne