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.

Data verification failed C6747 platform

Hi,

After building the project I loaded it in OMAP-L137EVM without any problem. However, I've changed some buffer sizes with no overlaped sections and CCS shows next dialogs:

 

As can be seen buffers sections are placed at 0xC2000000 and 0xC2100000. If I back to change buffer sizes, program loading no longer works as before and error persist. How can I avoid this?

  • The data verification failed error is fairly straight forward, meaning that CCS tried to write to that location but read back something different from what it wrote, usually this would be associated with bad memory mapping (i.e. loading to an invalid location) or bad memory configuration (i.e. external memory not configured). However for the case you describe the location seems valid for external SDRAM, and the memory configuration should not have changed with changing buffer sizes.

    To dig into this further, I would be interested to see if you can access that 0xC0139000 with CCS's memory view window, you should be able to double click on the location in the memory view to try to modify the value and see if it actually changes. 

    • If you still cannot modify the value from the view memory window than you may want to double check the memory configuration. In this case my suspicion would be that something about how your code changed when you increased the buffer sizes corrupted the SDRAM configuration, so a deeper analysis of how your buffer size changes impacted other aspects of the system would be in order.
    • If you can modify the location from the view memory window reliably than you may want to check into updating your CCS to the latest service release through the update adviser under the help menu. In this case my suspicion would be that you may be running into some bug with CCS that is confusing the loader, making sure you are using the latest service release may help to fix such odd problems.
  • even more simple, after doing a Project->Build Clean everything goes well as ever.

    Bernie, thank you for your tips anyway.