TM4C1294NCPDT: data verification error in CCS12

The Console shows this:

CORTEX_M4_0: GEL Output:
Memory Map Initialization Complete
CORTEX_M4_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
CORTEX_M4_0: File Loader: Verification failed: Values at address 0x0002FFA0 do not match Please verify target memory and memory map.
CORTEX_M4_0: GEL: File: C:\Programming\TI_v12\N374_010\Debug\N374_010.out: a data verification error occurred, file load failed.

br

Henning

Hi,

 Before I send your question to our CCS experts, can you try to load a simple program like blinky or hello example using CCS12 and XDS100V2?

 Do you have other debug probes such as XDS200? Can you repeat the problem on a different probe?

I tried with a simple application like hello, same problem.

I don't suspect the XDS100V3, because it loads fine with Uniflash and if I connect it to a PC with CCS v10. I only have this probe.

Hi,

  I will forward your question to our CCS experts. Perhaps there is an issue with the XDS100 driver for CCS12 but will let the experts comment.  

I can connect to my TM4C1294NCPDT target using an XDS100v2 debug probe in my Windows 11 PC.

Henning Christiansen said:

Values at address 0x0002FFA0 do not match

If you look at that address in the memory browser view, is it indeed incorrect?

I start the Debugger only loading symbols and then manually loading the program.

You mentioned CCSv10 works fine. Is this also on the same new Windows 11 PC?

I just installed CCSsv10.1.0 on the new Windows 11 PC. Debugging and load with XDS100v2 works fine on it.

If I switch to CCSv12 I am still not able to load a file without getting an data verification error.

Can you share the out file you are trying to load? Please start an E2E private conversation if you wish to share privately.

Thanks

ki

When I load this file (blinky.out) in CCSv12 I get the verification error.

But only if I delete the flash first. I think the file i ok because it loads fine in CCSv10

I am not able to upload the file to the post, but its just a blinking demo.

Maybe CCSv12 does not support the XDS100v2 probe. Also deleting the flash from the debugger does not work in CCSv12.

Henning Christiansen said:

I am not able to upload the file to the post, but its just a blinking demo.

Yes I used the same demo successfully earlier with CCS 12.7.0, XDS100v2, on a Windows 11 PC.

CCS 12.x definitely supports XDS100v2. I have been using XDS100v2 with CCS 12.x successfully. 

Henning Christiansen said:

But only if I delete the flash first

Please explain this. Are you saying that on CCSv12, the issue only occurs when you explicitly erase all flash prior to flashing the program?