CCS/LAUNCHXL-F28379D: Why are we first syncing TBCLK and then again de-syncing?

Utsav Sharma12

Tool/software: Code Composer Studio

Hello Team TI,

In the following lines,

EALLOW;
    ClkCfgRegs.PERCLKDIVSEL.bit.EPWMCLKDIV = 1;
    CpuSysRegs.PCLKCR0.bit.TBCLKSYNC = 0;
    EDIS;

    InitEPwm1Example();
    InitEPwm3Example();

    EALLOW;
    CpuSysRegs.PCLKCR0.bit.TBCLKSYNC = 1;
    EDIS;

TBCLKSYNC is frist zero and then one. What would happen if I omit this step?

over 5 years ago

0 Pramod P over 5 years ago

TI__Expert 5430 points

Hi Utsav,

The TBCLKSYNC is used to globally sync all the enabled PWMs. More details on this is provided in the device TRM (section 15.4.3.2 " Time-Base Clock Synchronization") the link for which is given below.

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

Please click on the "verify answer" button at the bottom of this post if this response resolves your query.

Thanks & Regards

Pramod

C2000™︎ microcontrollers

C2000 microcontrollers forum

CCS/LAUNCHXL-F28379D: Why are we first syncing TBCLK and then again de-syncing?