• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 265 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

BOOSTXL-DRV8323RH: Reading address and fault reset - Simulink

Andrea Carraro
Prodigy 10 points
Part Number: BOOSTXL-DRV8323RH
Other Parts Discussed in Thread: LAUNCHXL-F28069M, DRV8323, DRV832X

Hi Team,

I’m new to the field of embedded programming. For this reason, I used Simulink PWM blocks to control the speed of a DC motor with a LAUNCHXL-F28069M and a potentiometer. The motor seemed to run fine, but after some time (minutes) the motor was spinning, I noticed the BOOSTXL board overheated and a failure occurred.

Now I’m completely stuck because I can’t detect the fault (red LED on) and reset the board. I unsuccessfully tried to look at Matlab documentation to find some examples on how to read register addresses to detect that kind of fault and reset it.

Could you help me providing a piece of code (Simulink or CCS) to run and see what’s happening and maybe reset it?

Thanks,

Andrea

  • 0
    TI__Mastermind 26046 points

    Hi Andrea,

    A few suggestions when testing faults with a BOOSTXL-DRV8323 EVM board:

    • BOOSTXL-DRV8323RH is hardware version of the DRV8323. A fault is reported through the nFAULT pin, but there is no way of determining what type of fault it is unless if you monitor waveforms and can see whether a VGS or VDS fault has occurred, or if something more catastrophic like a CPUV fault has occurred.
    • BOOSTXL-DRV8323RS is SPI version of the board. You can debug faults using SPI. 
      • If on powerup, nFAULT is not lit up, then the IC should be fine and you should be able to debug any faults by reading SPI registers when nFAULT goes low
      • If on powerup nFAULT is lit up, the IC may be damaged from the overheating. You should double check my measuring impedance of the gate drive output pins to GND and comparing with a known good device to see if there is any opens or shorts from the bad IC.
    • In regards to overheating, can you ensure you are using a sufficient IDRIVE setting? IDRIVE controls gate drive current and defaults to 1A source, 2A sink in DRV832x. IDRIVE should be set to a low value when initially evaulating spinning a motor. 

    Thanks,

    Aaron