CCS/UCD3138A: UCD3138A_ACOMP error?

you lee1

Intellectual 300 points

Part Number: UCD3138A

Tool/software: Code Composer Studio

i used HSFB_029_Fireware:

when i set the FaultMuxRegs.ACOMPCTRL0.bit.ACOMP_B_THRESH = 81，test ok；

when i set the FaultMuxRegs.ACOMPCTRL0.bit.ACOMP_B_THRESH = 74，hiccup protect turn to latch protect!

i used USB_adapter read the message, i found supply_state == STATE_REGULATED, and restart_counter == 0,

but DPWM no pluse?

any one know where error?

give me an idea, thanks!

over 7 years ago

0 Amiel Hussain over 7 years ago

TI__Expert 4070 points

Hello,

Your question has been forwarded to the appropriate engineer.

0 Ian Bower over 7 years ago

TI__Genius 17090 points

It sounds like you are triggering a fault on the DPWM with the lower threshold. We recommend that you read from the fault status register on the DPWM, rather than from the registers in the fault mux. Sometimes they may not show the fault detection but the DPWM will. If the DPWM gets a fault, you need to disable the DPWM and then reenable it to clear the fault.

0 you lee1 over 7 years ago in reply to Ian Bower

Intellectual 300 points

Hi ian,

i used follow code,

debug_buffer[28] = Dpwm3Regs.DPWMFLTSTAT.all & 0x00FF;
debug_buffer[29] = Dpwm2Regs.DPWMFLTSTAT.all & 0x00FF;
debug_buffer[30] = Dpwm1Regs.DPWMFLTSTAT.all & 0x00FF;
debug_buffer[31] = Dpwm0Regs.DPWMFLTSTAT.all & 0x00FF;

fault_status1 = FaultMuxRegs.FAULTMUXINTSTAT.all;

debug_buffer[25] =(fault_status1 >> 16) & 0x00FF;
debug_buffer[26] =(fault_status1 >> 8) & 0x00FF;
debug_buffer[27] = fault_status1 & 0x00FF;

but, when the fault happened, fault_status1 = 0x002000000,

the DPWMFLTSTAT always zero.

p.s. my debug_buffer is 32 data.

0 liwei qi over 7 years ago

Expert 1160 points

Hi! Do you have slove the question?

0 you lee1 over 7 years ago in reply to liwei qi

Intellectual 300 points

not yet

Power management

Power management forum

CCS/UCD3138A: UCD3138A_ACOMP error?