• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 478 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.

CCS/TMS320DM642: Debugger XDS560v2 LC (Traveler) not working on Windows 10 with CCS7.3

user4990587
Prodigy 195 points

Part Number: TMS320DM642

Tool/software: Code Composer Studio

When trying to load software to the target or debug software on the target, CCS outputs the following error message:

C64x: File Loader: Verification failed: Values at address 0x80000000 do not match Please verify target memory and memory map.
C64x: GEL: File: C:\project\example.out: a data verification error occurred, file load failed.

The development PC has Windows 10 installed.The CCS version is Version: 7.3.0.00019. The TI processor is TMS320DM642. Initially the debugger was working on Windows 10. The last time working with this debugger was one or two months ago. The software was not modified.

Does anyone can give support for this problem?

Thanks in advance.

  • 0
    TI__Guru**** 171839 points

    Hi,

    The error message is not related to the Debug Probe itself, but instead to the code being loaded and possibly the status of the hardware while trying to load it. 

    My suspicion is the latter, especially because address 0x80000000 is SDRAM and requires initialization. Check the section Available Target Memory of the Troubleshooting page below:

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

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 195 points

    Hi Rafael,

    thank you for responding to my support request. I tried the same with several processors of this type, with a second debugger of same type and with several different compiled software (.out) on two PCs. The error stays the same. So I assume it has to do something with a Windows 10 update, especially because the same constellation already have been worked a few weeks ago. It is the only thing in the setup that changed.

    I do not understand what could have changed from one to the other day. I am not able to access flash memory.

    Do you have any other idea?

    Best regards,

    Daniel

  • 0 in reply to user4990587
    TI__Guru**** 171839 points

    Daniel,

    If the error on all the hosts is exactly the same as the one you sent before, I really don't think the issue is with the OS update. Otherwise, CCS would throw an error where it would not be able to access the Debug Probe at all - a much more premature error when compared to the error you are showing here, which is completely related to the target itself and therefore past the host-Debug Probe iterations. 

    Did you check the troubleshooting steps on the reference I mentioned? Namely the process of manually connecting to the target and verifying if the memory address is available.

    My suspicion is that something have changed on the target configuration file used in your environment - does it have a GEL script associated with the C64x core of the device? This GEL script helps configure the SDRAM before the code is loaded (a configuration for the EVMDM642 already pre-configures this GEL script from us). 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 195 points

    Hi Rafael,

    you are totally right, it is not a problem of the OS update. When trying to follow the troubleshooting steps on the reference you give, I noticed that no GEL initialization script was specified. So your second question is the correct one. I specified the GEL script within the "Advanced" tab of my target configuration and now debugging works again.

    Thank you very much for your help!

    Best regards,

    Daniel