• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 443 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.

DRV8350S-EVM: cannot initialize driver

Frederik Baars
Intellectual 2115 points
Part Number: DRV8350S-EVM
Other Parts Discussed in Thread: DRV8350

Hi

we could do some idle tests with the DRV8350S-EVM, unfortunately after the last initialization the driver cannot be initialized anymore.

When pressing Enable, I always get the Unknown Error, see graphic: 

Any advice?

Thanks

Fred

  • 0
    TI__Mastermind 21805 points

    Hi Fred,

    We need to isolate the issue to the DRV8350, MSP430, or interface to the PC.

    Can you check the following:

    • Is the DRV8350 is powering ON? Confirm DVDD (pin 29)  is 5.0V and VCP (pin 4) is VM+10V. When powered on is nFAULT staying ON (red LED).
    • Is the MSP430 ON? Check that +3.3V is present on pin 18/50 of the MCU. Check voltage on V18 (pin 67) and VCORE (pin 20)
    • Is USB power applied? Check TP1 on the USB side of the isolation boundary and TP2 on the driver side.

    Thanks,

    Matt

  • 0 in reply to Matt Hein
    Prodigy 190 points

    Hey Matt, 

    the DRV is powering ON, i am able to enable it over the DRV8350 GUI on my PC, I also could read out the Registers so I guessed Connection between PC, USB, MCU and DRV should work.
    but i rechecked Pin29 on C57, measured 4,967V and VCP is VM +~10V. When Powering on there is no Fault on DRV Fault LED 

    Pin 18 on MCU = 3,288V 
    V18 on Pin 67 = 1,796V 
    VCore on Pin 20 = 1.932V

    VUSB = 5,043V 
    VTP2 = 3,29V

    When Trying to Enable DRV8350 via GUI on my PC, RED mcu Fault LED is on 

  • 0 in reply to Frederick Runte46
    TI__Mastermind 21805 points

    Hello Fred,

    Can you also check the VGLS pin? Pin 31. If this is low then the VGLS regulator is damaged.

    Bit 6 of the VGS Status register is flagging, which corresponds to either a VCP or VGLS failure. VCP looks OK based on your measurements.

    I see that you have configured IDRIVE to 150mA source and 300mA sink. This could be too much for the MOSFETs on the EVM and eventually causing damage to the driver over time. (see [FAQ] Selecting the Best IDRIVE setting and Why this is Essential)

    Thanks,

    Matt

  • 0 in reply to Matt Hein
    Prodigy 190 points

    Hey Matt, 

    I guess i Measured 4,9xx V there as well, But while Mesurement i Shorted something with the Tip, So i now lost Voltage after Buck... VBuck ~0,3V. 

    I bet i need a new board anyway.... Thanks for your Assistance

  • 0 in reply to Frederick Runte46
    TI__Mastermind 21805 points

    Hi Frederik,

    4.9V on VGLS would indicate that this LDO is damaged - it should be more like 10-11V. It sounds like the buck output is broken now as well.

    Thanks,

    Matt