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.

DRV8301: DRV8301 sending every possible fault over SPI

Part Number: DRV8301

I have done a new hardware design based on the Odrive schematics. I have flashed the STM32F405 with different versions of there firmware and setup debugging to find I'm having issues with the DRV8301, I have put 2x boards together to make sure I don't have faulty DRV. 

The buck converter on the DRV is working fine so this confirms the GND PAD is connected well. I have attached an Image with the Faults being returned and the SPI registers. For some reason, it's sending every possible fault the DRV has, but it does not stay active in the SPI registers, I'm not sure if it's briefly faulting and then returns to normal. All the resisters for the faults indicate FALSE under the debugging. The Odrive firmware is using the TI DRV8301 SPI Library.

These are the faults returned when I try to calibrate a motor, the DRV faults out instantly, the motor does not try to do anything at all and the same happens with no motor connected. I can clear the faults and when I try again I get the exact same faults. This is identical on both boards. I have checked the GVDD voltage and I have 11V so that seems to be working within specs. I have checked for noise on the scope and everything looks good. 

Could this be caused by the types of MOSFETs I'm using or more likely hardware layout issues? I don't know what else to test to get to the bottom of this.

(DRV8301_FaultType_FETLC_OC | DRV8301_FaultType_FETHC_OC | DRV8301_FaultType_FETLB_OC | DRV8301_FaultType_FETHB_OC | DRV8301_FaultType_FETLA_OC | DRV8301_FaultType_FETHA_OC | DRV8301_FaultType_OTW | DRV8301_FaultType_OTSD | DRV8301_FaultType_PVDD_UV | DRV8301_FaultType_GVDD_UV | DRV8301_FaultType_GVDD_OV)

  • Matthew,

    Thanks for posting on the MD forum!

    If you are getting all faults reporting then your SPI is likely not working correctly (software or hardware issue).

    Have you checked the status of the nFAULT pin? 

    Have you used a scope to check the SPI output from the DRV directly? 

    Please post scope images if possible.

    Regards,

    -Adam