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.

MSP430 data verification error with given code

Other Parts Discussed in Thread: MSP430G2553, DRV2667

Hey, I'm using the DRV2667 EVM that comes with an MSP430G2553. I downloaded the original source code for the DRV2667 EVM and I'm trying to reprogram the MSP by connecting a launchpad to the EVM by spi-bi-wire. I imported the code provided by TI and tried to debug it, but it keeps giving me a data verification error. I tried updating the linker file to the most recent, but it hasn't helped. I haven't changed anything else about the code.

Can anyone help me with this error? Any help would be appreciated. Thanks.

  • Data verification error sounds like a problem synchronizing the debugger with the MSP after download. So it isn’t a problem with the source code and the build , but rather with uploading the binary to the target and then attaching to it. I’d check the connection. (especially for cracked traces near the FET connector on the target).
    Also, when using SBW, low signal capacitance is important. Keep the SBW connection as short as possible.
    Or shorter. Every inch is an inch towards connection failure.

  • Thanks for the reply,

    I've got the spi-bi-wire connected to the headers on J4 directly, so wire length shouldn't be an issue. And after re-importing the project several times, have managed to get the data verification error to go away, however, CCS now tells me it can't find the msp430, even though it could before, and I haven't touched anything. I haven't touched the project settings from the imported project. I've also got the test and reset unhooked on the launchpad. Any reasons for this?

  • Not finding the MSP can have multiple reasons. Physical absence, missing supply, and also the most severe form of a distorted JTAG communication. Since you had verification problems before (which can be caused by a distorted JTAG connection too), I think this is the most likely cause.
    SBW is quite fragile and very sensitive to line capacitance and line length. Personally, I use the more robust and also much faster 4-wire JTAG wherever possible. And even there I sometimes get problems. Usually, removing and re-applying the supply voltage or re-plugging the JTG connector solves the problem. Or manually shorting RST to GND right before trying to update the firmware.

**Attention** This is a public forum