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: D3 led/ FW_led indicating firmware not running in microcontroller in DRV8350S-EVM

Part Number: DRV8350S-EVM


Hello,

I'm working with DRV8350S-EVM in Sensored mode for my motor application. The evaluation board was working fine with my setup and I was able to test my motor application.

But I have encountered a problem, the GUI is not identify the code dumped in the microcontroller as sensored code. It shows that a new USB connection has been established but the the code is not identified and hence I:+'m unable to run my motor. I found that the D3 LED or FW_Led was not on, which means the firmware was not running in the microcontroller. How can I resolve this issue?

Regards,

Abhishek K Singh

  • Hello Abhishek,

    Does loading the old FW work after?

    Just to make sure its clear, there really isn't anything different from a HW point of view to update the FW. Just the USB and CCS. Some users more familiar with flashing MSP FW, will try to use an external launchpad and JTAG emulator to the JTAG ports and brute force some FW.

    Best,

    -Cole

  • Hi Abhishek,

    Thanks for your question!

    First of all - can you confirm if the motor power supply was ON when you try to connect with the GUI? I think the MSP430 on the board is powered through the VM (via a buck & LDO)

    Thanks,

    Matt

  • Hello Matt,

    The power supply to evaluation board was ON and was reading the given value (35 V) on "VM" test-point. The 3.3 V and 5 V supplies were present on "J1" connector. The MSP430 is getting analog power of 3.3 V at pin 11 named "AVCC1" in schematics. There are no test-points provided for checking this "AVCC1". So I checked the midpoint of decoupling ckt (where R15 resistor and C14 capacitor have been used) which is going to pin 11 on the board and it is 3.3 V. 

    The main issue was that after establishment of connection to the port the GUI doesn't identified the evaluation board configuration as "Sensorless" or "Sensored". The difference I noticed on the board is that the "D3" LED/"FW_LED" and "MCU FAULT" LED were not glowing. I checked in the user guide and in it D3 LED /FW_LED indicates whether the firmware is running on the micro-controller.

    Regards,

    Abhishek Kumar Singh

  • Hi Abhishek,

    Please also note Cole's comment & question above - Does loading the old FW work after?

    Just to make sure its clear, there really isn't anything different from a HW point of view to update the FW. Just the USB and CCS. Some users more familiar with flashing MSP FW, will try to use an external launchpad and JTAG emulator to the JTAG ports and brute force some FW.

    Did you make modification on our existing firmware, or are you using the original firmware image?

    I agree, firmware does not appear to be running on the MCU.

    Thanks,

    Matt