CODECOMPOSER: Issues with TM4C1294NCPDT FreeRTOS debug linked at Non-Zero address

Hello,

What exact CCS version is being used?

Can you reproduce the issue while generating a debug server log? Then zip the log and post it to this thread:

https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

John Gerthoffer said:

Is there some way to command the debug pod to set CPU registers/SRAM memory when loading the program for debug?  

This can be done with a startup GEL file:

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-gel.html

Thanks

ki

CCS v12.5.0.202309161830

It took a couple tries to recreate the issue.  Ultimately, I connected an EK-TM4C1294XL ICDI in addition to the XDS200 JTAG debugger that I use on my board.

Now, XDS200 does not load the program properly. (even after I removed the Stellaris ICDI).

DebugServerLog03.zip

Thanks. I will try to reproduce the issue with my EK-TM4C1294XL and XDS200 when I have access to the hardware.

I tried with the timer_edge_capture example with CCS 12.5.0 via Blackhawk XDS200 debug probe with a EK-TM4C1294XL. I set APP_BASE to 0x00004000 in the linker command file. It loads fine every time.

John Gerthoffer said:

Ultimately, I connected an EK-TM4C1294XL ICDI in addition to the XDS200 JTAG debugger that I use on my board.

I have a modded board where the ICDI connection is disabled so it is a straight XDS200 connection only.

If you don't connect the ICDI, does the XDS200 work every time?

If I start out with only my board and the XDS200 interface, yes.

The real issue seemed to be having two boards and two debug pods connected at the same time.  Even with "Manage the project's target configuration automatically" turned off and the debug config was set to the XDS200, it did not work correctly.

However, when I would debug the EK board with the ICDI built in, it worked every time regardless whether my board with the XDS200 interface was connected or not.

John Gerthoffer said:

The real issue seemed to be having two boards and two debug pods connected at the same time.

Ah ok, this is the a key information that was missing before. The issue is when you have both ICDI and XDS200 connected, which each connection going to a separate board. Are you launch a simultaneous debug session for each board at the same time? Or does the issue still occur when the ICDI is physically connected but not used in any debug session (while the XDS200 one is)?

Ki said:

the issue still occur when the ICDI is physically connected but not used in any debug session

This

Thanks for looking into it.  At least I figured out that I need to disconnect my EK board ICDI when debugging my board with the XDS200.