• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 226 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.

DRV8329AEVM: Using Different Microcontroller

Silas Willson
Prodigy 15 points
Part Number: DRV8329AEVM

Tool/software:

Hello,

I am trying to make my own bldc motor controller, and I am using the DRV8329AEVM for its power MOSFETs and gate drivers. For the MCU, I am using the F28035 Piccolo card (not the launch pad that connects easily with the DRV8329AEVM pins). I am trying to connect the pwm signals from the f28035 to the INHx and INLx pins of the EVM. Whenever a voltage is applied to the INHx and INLx pins, the nfault is toggled and the gate driver appears to be disabled (all the GHx pins read 6 volts and all the GLx pins read 0 volts). My question is what might be causing this? Can I use the f28035 microcontroller or is the EVM only compatible with the LAUNCHXLF280049C LaunchPad?

Thank you in advance for any Help!

  • +1
    TI__Genius 15475 points

    Hi Silas,

    I'm not entirely familiar with using a different MCU with our EVMs. If you're still trying to use our GUI then you would have to use the Launch pad.

    Are you only connecting the input pins to the MCU? Have you taken a look at what the launch pad connects too? Maybe your missing a few connections?

    www.ti.com/.../slvucf5a.pdf

    Regards,

    Yara

  • 0 in reply to Yara Al Shami
    Prodigy 15 points

    Hi Yara,

    I am not trying to use the GUI, so I don't think I need the launch pad. I was hoping the only connections I would need would be the input connections, but I did consider the other pins. I already found the tables you shared and tried making the additional connections that the launch pad would have used to no avail. 

    However, upon further testing, I discovered that it is only the INHA pin that triggers a fault when used. I believe the board I am using may have damage somewhere in the phase A part of the circuit. If not for this damage, I believe the board will work with my MCU.

    I will mark this issue as resolved because there is not much more I can do until I get a new board, but if you or anyone else thinks of any connections or configuration changes I may need to make please feel free to reply to this message with suggestions. 

    Regards, 

    Silas