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.

CCS/MSP430FR2355: Data Verification Error

Part Number: MSP430FR2355


Tool/software: Code Composer Studio

Am using MSP430FR2355 launchpad, It was working well, and I was using the debugging session as normal, but today morning, while I was trying to debug on it, it gave me a data verification error, and am not able to use it anymore.

I knew this is related to linker or writing on non-writable memory, but I didn't change anything regarding this. The last thing I changed was using the following interface to adjust the SMCLK frequency, I called it with the following arguments: CS_initFLLSettle(24000,720); to 24 MHz. I don't believe this damaged anything in the uC.

The error in details is:
MSP430: File Loader: Verification failed: Values at address 0x088A4 do not match Please verify target memory and memory map.
This is in FRAM as per the linker file.

  • Hello Ahmed,

    It sounds like you have already seen the below guide. But if you have not, please do read it:

    http://software-dl.ti.com/ccs/esd/documents/troubleshooting-data_verification_errors.html

    Ahmed Hosny1 said:
    The error in details is:
    MSP430: File Loader: Verification failed: Values at address 0x088A4 do not match Please verify target memory and memory map.
    This is in FRAM as per the linker file.

    This error seems to be an issue of where memory was written to, but the data check (if the values were written correctly) failed.

    Ahmed Hosny1 said:
    The last thing I changed was using the following interface to adjust the SMCLK frequency, I called it with the following arguments: CS_initFLLSettle(24000,720); to 24 MHz. I don't believe this damaged anything in the uC.

    What happens if you revert these changes back? Does the issue go away?

    Thanks

    ki

  • Hello,
    I haven’t heard back from you, hence this issue is being closed. If you wish to continue the discussion, please post a reply with an update below (or create a new thread).

    Thanks,
    ki