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.

DRV8434A: Thermal shutdown and overcurrent faults are latched/do not automatically recover

Part Number: DRV8434A
Other Parts Discussed in Thread: DRV8434

We are seeing the same behavior described in this topic where the DRV8434A does not seem to automatically recover after a thermal shutdown (OTSD) or overcurrent condition (OCP) like the datasheet says it should. (With a thermal imager, we are seeing that the thermal shutdown kicks in around 160 C and then the driver cools down to under 40 C without restarting.) Instead, pulsing nSLEEP or power cycling the chip is necessary to resume operation.

It doesn't seem like the discussion was resolved in the other topic (I would have posted there, but it is now locked). However, we can answer the questions Wang Li asked in his last reply ("According to Table7-7, would you check nFault pin and VCP-VM voltage?"): after a thermal shutdown, nFAULT remains low, and the charge pump appears to remain disabled (with VM = 24V, we measure 29V on VCP before the fault and 23.6V after).

We have not been able to obtain a DRV8434 (the version without stall detection) to test this on, but according to its datasheet, the ENABLE pin determines whether the OCP and OTSD faults are latched (Hi-Z means they are latched; >2.7V makes the driver automatically retry). However, the DRV8434A datasheet does not mention anything about the EN pin affecting the fault behavior, and putting >2.7V on EN does not seem to make a difference for either fault.

Is the datasheet incorrect and are the thermal shutdown and overcurrent faults on the DRV8434A always latched until they are cleared?