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.

Tiva Debug Error Message: 'a data verification occurred, file load failed.'

Other Parts Discussed in Thread: EK-TM4C123GXL, LMFLASHPROGRAMMER

Hi,

I just desoldered R9 and R10 from my Tiva EK-TM4C123GXL Launchpad for the purpose of being able to control PB6, PB7, PD0, and PD1 separately (https://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/334509/1166924). Now, when I launch the debug session, I receive the following error message:

Load program Error.

File:

C:\...\project.out: a data verification occurred, file load failed.

And in the Console I receive this message:

CORTEX_M4_0: GEL Output:
Memory Map Initialization Complete
CORTEX_M4_0: File Loader: Verification failed: Values at address 0x0000000000000000 do not match Please verify target memory and memory map.
CORTEX_M4_0: GEL: File: C:\...\project.out: a data verification error occurred, file load failed.

Did removing the resistors cause this somehow? Did I possibly apply to much heat in desoldering? Any help would be much appreciated.

Thanks!

Kyle

  • Hello Kyle,

    Unless the Solder heat or tip was touched to the device. Did you run a Erase-Blank Check via LMFlashProgrammer?

    Regards
    Amit
  • The solder tip did touch the pads, but not for an excessive amount of time.

    After running the Erase-Blank Check, I am able to run the debug session, but when I suspend the program, I receive this error:

    No source available for "__aeabi_memset8() at C:/.../project.out:{3} 0xea430112{4}"

    If I stop the debug session, then start it again, I receive the same error as before (Load program Error).

    I ran the Erase-Blank Check a second time, and achieved the same result.

  • Hello Kyle,

    I would suggest running a known set of example like udma_demo, blinky to see if they run normally or not. If they do then something in your new code could be causing the issue.

    Regards
    Amit
  • Amit,

    I ran udma_demo and blinky and they worked without any issues. I then stepped through my code and found that it was hanging in the SysCtlClkSet function. I remembered that yesterday I had changed the Config parameter from SYSCTL_XTAL_16MHZ to SYSCTL_XTAL_8MHZ (I'm not sure why I did that). I changed it back to SYS_XTAL_16MHZ and everything seems to run correctly now! Thank you for your help!

    Kyle
  • Hello Kyle,

    That would surely mess it up. The Crystal is 16MHz. By telling the System Control module it is 8MHz, the table for 8MHz will be loaded which would cause the PLL to be way out of spec causing a lock up.

    Regards
    Amit