• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 81 subscribers
  • Views 2767 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.

Original question:

Allow access to BSL memory on 2132

CCS/MSP430FG4618: File Loader: Verification failed when adding BSL as in slaa600d

Hugo Hernandez
Prodigy 30 points
Part Number: MSP430FG4618

Tool/software: Code Composer Studio

I have an application running with the original linker file and no BSL code.

Following the slaa600d I created a bootloader code and modified the linker file as needed for both the bootloader and the application.

At this point I can download both images to the MSP430 with out a problem.

Later trying to download only the application with the original linker file for debug reasons I receive this message:

MSP430: File Loader: Verification failed: Values at address 0x00010 do not match Please verify target memory and memory map.
MSP430: GEL: File: C:\cygwin\home\Hugo\workspace\PocketProgrammer\msp430\Release\PoP.out: a data verification error occurred, file load failed.

Right now I am not able to debug only the original app with the original linker file and I can't find any solution for it.

"Connection options" and "Download options" are greyed

  • 0
    TI__Mastermind 49692 points

    Hello Hugo,

    Did you make sure to rebuild your project after changing linker files?

    This issue could be related to not erasing a certain section of memory as discussed in the following threads. Besides the recommendations in these threads, I would recommend keeping two separate CCS workspaces: one for the MSPBOOT project, another for the typical project with default linker file.

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    Prodigy 30 points

    James,

    Yes I did rebuild (clean and build) the project.

    I also have 2 different projects for MSPboot and one for the app. Will try with 2 different workspace and let you know but I don't understand how that would change anything

  • 0 in reply to James Evans
    Prodigy 30 points

    Having 2 different workspace solved my problem. 

    Or at least it appears to solve it in the few tries I did.

    the question is now: HOW?

  • 0 in reply to Hugo Hernandez
    TI__Mastermind 49692 points

    Hello Hugo,

    Unfortunately, I'm not an expert on CCS and TI compilers, but I suspect that there was some behind-the-scenes linking between the two projects, even though you were using the default linker file. Other community members with more experience in this area may have more details on exactly why this fixed the issue. I'm happy to hear it solved your issue though! Thanks for letting me know.

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    TI__Guru**** 171004 points
    Hi,

    Depending on how the debug session is launched, CCS will create a Debug Launch Configuration that matches its project/target config filename and holds many parameters. These Debug Configurations are created and stored in the .metadata directory of each workspace.

    In this case, if you debug your projects (applications?) by selecting them and clicking on the green bug button, an individual Debug Configuration will be created per project. If somehow the Debug Configuration for one of the projects was corrupted or held invalid values, it could easily affect only this particular project.

    Changing workspaces would start with a clean slate.

    To workaround this and use the same workspace, you can delete the problematic Debug Configuration as mentioned in step 3 of the reference below:
    processors.wiki.ti.com/.../Troubleshooting_CCSv7

    I suspect that is what is going on in your case.

    Hope this helps,
    Rafael

**Attention** This is a public forum