• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 420 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.

SW-EK-TM4C123GXL: Debug information is missing when the configuration is launched manually

Mehmet Onur Cirit
Prodigy 35 points

Part Number: SW-EK-TM4C123GXL

Hello,

I have a question related to debugging by launching the target.ccxml. My problem is that the debug info is not loaded when I launch the .ccxml and connect to the target.

Let's assume I am trying to load blinky example;

If I start debugging by using the debug button there are no problems.

The code is resolved and I can put a breakpoint wherever I want.

However, if I launch the .ccxml and then connect the target, the debug information is not available.

What am I missing here? Is there an additional step to show the debug information to CCS when I debug it via launching the configuration?

Thanks in advance.

  • +1
    TI__Guru**** 191886 points

    Hi,

      In your first method by pressing the debug icon, the debugger will launch the target configuration, connect to the target and load your code by programming the firmware image to flash. In the second method where you manually launch target configuration and connect to the target, you need to also manually load the symbol of your application, in this case the blinky.out. Loading symbol will not reprogram the code but only load the symbol. See below.