• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 784 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320C6678: a data verification error occurred, file load failed

Mike ITGeek
Expert 1320 points
Part Number: TMS320C6678

I started getting the below error as I try to load my .out file ... it is an openmp project and used to load just fine until recently.

I get the below error window in CCS 9.2. 

In the console I get the below error:

C66xx_0: File Loader: Verification failed: Values at address 0x895AF2C1 do not match Please verify target memory and memory map.
C66xx_0: GEL: File: C:\Users\Mike-laptop\workspace_v9_2\ark_cpplab\Debug\ark_cpplab.out: a data verification error occurred, file load failed.

Please let me know what that means ....

Regards

  • 0
    Expert 1320 points

    I had reinstalled the CCS so i guessed I had to recreate the target configuration file... and issue is resolved for now... still need to know what that error message means .... 

    66xx_0: File Loader: Verification failed: Values at address 0x895AF2C1 do not match Please verify target memory and memory map.
    C66xx_0: GEL: File: C:\Users\Mike-laptop\workspace_v9_2\ark_cpplab\Debug\ark_cpplab.out: a data verification error occurred, file load failed.

  • 0 in reply to Mike ITGeek
    TI__Guru** 114410 points

    Generally, the issue occurs when the ELF loader in CCS loads binary image to platform memory but the read back fails either due to issue with DDR initialization issues or some other issue with initialization. it can also be caused due to if some of the CCS target files are corrupted and the memory is not recognized as valid memory. The issue in your case seems to be occuring at a address location in external DDR3 memory.

    Glad to know that the reinstall has solved the issue. Please mark the issue as closed unless you have more questions regarding this issue.

    Regards,

    Rahul