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.

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

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.DPWMMUX.bit.DPWM0_SYNC_FET_SEL = 2; /
   LoopMuxRegs.DPWMMUX.bit.DPWM1_SYNC_FET_SEL = 2

   FeCtrl2Regs.RAMPCYCLE.bit.SWITCH_CYC_PER_STEP = 1;//
   FeCtrl2Regs.RAMPCTRL.bit.SYNC_FET_EN = 1; //
   FeCtrl2Regs.RAMPCTRL.bit.RAMP_EN = 1; //
   FeCtrl2Regs.RAMPCTRL.bit.SYNC_FET_RAMP_START = 0; //
   FeCtrl2Regs.RAMPDACEND.bit.RAMP_DAC_VALUE = 1100; //
   FeCtrl2Regs.DACSTEP.bit.DAC_STEP = 10;
}
I know this program is to configure the RAMP function of DPWM0B and DPWM1B.

I don't know if I understand it right?

RAMP is increased from 0, one step per 2 switching cycles, each step is 10, and after 220 cycles, RAMP is increased to the final value of 1100.

I still have a question, that is why the final value of RAMP is 1100. How is this 1100 obtained?