UCD3138: Questions about void init_loop_mux(void){} in hard-switched full-bridge firmware for UCD3138

zoujiangyilang

Part Number: UCD3138

Hello, I'm learning about the UCD3138's hard-switched full-bridge firmware.
I have some problems with void init_loop_mux(void){}.
Void init_loop_mux(void)
{

LoopMuxRegs.FECTRL0MUX.bit.DPWM0_FRAME_SYNC_EN = 1;

LoopMuxRegs.FECTRL2MUX.bit.DPWM1_FRAME_SYNC_EN = 1;

LoopMuxRegs.FECTRL1MUX.bit.DPWM2_FRAME_SYNC_EN = 1;

}
I know that the above program synchronizes a certain PWM frame to a front end,

but I don't know exactly what frame synchronization means. Is frequency synchronization or simultaneous activation?

over 6 years ago

0 Yitzhak Bolurian over 6 years ago

TI__Mastermind 18370 points

There are two triggering signal that go from DPWM to FE. The sample trigger and the FRAME_SYNC.

FRAME_SYNC is the signal that triggers the advancement in the ramp counter of front end (FE).

So, if not connected ramp will not work. Another important thing about FRAME_SYNC is that DPWM will generate this signal even if the DPWM outputs are disabled.

0 zoujiangyilang over 6 years ago in reply to Yitzhak Bolurian

Genius 4560 points

Got it！
Thank you very much.

Power management

Power management forum

UCD3138: Questions about void init_loop_mux(void){} in hard-switched full-bridge firmware for UCD3138