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.

DRV8889-Q1EVM: how to burn software into EVM

Part Number: DRV8889-Q1EVM
Other Parts Discussed in Thread: DRV8889-Q1

Tool/software:

Hi team,

For below download software for DRV8889-Q1EVM, how can we burn this software into EVM? Which software should we use to load the code? What‘s the version of the software?

BR,

Bengi

  • Hi Bengi,

    You won't need to burn any software/firmware into the EVM. The MSP430 MCU onboard comes preprogrammed with the necessary firmware in the EVM for use with the GUI app. The correct version of the GUI for this EVM is 1.1.17. Here's the link for the cloud based GUI, https://dev.ti.com/gallery/view/MotorDriversBSM/DRV8889-Q1/ver/1.1.7/.

    The desktop app can be installed using the installer in this zip file.

    Thank you.  

    Regards, Murugavel

  • Hi Murugavel,

    Customer has problem communicating with our EVM. They linked four SPI pin and use their MCU to control our device. Firstly they pull up nSLEEP, then they send command, and there's no reply. What may be the cause here?

    The SPI waveform is like:

    BR,

    Bengi

  • Hi Bengi,

    The DRV8889-Q1 has a wake up time tWAKE ~ 1ms. So after nSLEEP = 1 the customer must wait at least 1 ms before starting an SPI transaction. Assuming this was already considered based on the SPI waveform, SDI is 0x0000 which implies the customer is trying to write 0x00 to the FAULT status register which is a read only register. To read this register customer must transmit 0x4000 to SDI. Note the address for registers are in B13 to B9 see below and W0 must be 1 for a read operation.

    Also the EVM has a 3V3 regulator from the USB to power the VSDO pin. Was the EVM connected to the USB? If not VSDO must be provided either 3.3V or 5V depending on their MCU logic voltage requirements. Could we try with 0x4000 for SDI and capture the SDO using the analyzer? Thank you.

    Regards, Murugavel