• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 727 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/TM4C129CNCPDT: SWO Trace Debug w/XDS200 USB Debugger

Stuart Baker
Genius 10270 points
Part Number: TM4C129CNCPDT

Tool/software: Code Composer Studio

I'm working with a customer on getting SWO Trace Debug working.  We believe we have correctly followed the instructions from the following wiki page:

The target config has the following settings:

The programming connector has a 10k pullup on reset and TCK:

For example if trying to run interrupt profiling, we have the following settings (COM 11 is the user COM port):

And this results in the following error message:

We have tried starting the analysis both with the firmware free-running and after halting on a breakpoint after system clock initialization with the same result.

None of the other Hardware Trace Analysis features in the menu appear to work either.

We watched the TDO pin on an oscilloscope and it is stuck low when the XDS200 debugger is connected and in use. If we remove the debugger or let the board run on its own, the internal pull-up on TDO appears to pull it high. We are assuming the chip is successfully using SWD mode since we don’t see anything on TDO during programming or debug – we haven’t checked the entry sequence on TCK and TMS to confirm.

Is there something we need to do in the firmware to enable the ITM in the MCU or is there a Code Composer setting somewhere we are missing? We are using CCS 6.1.2.00015.

Thanks,

Stuart

  • 0
    TI__Guru**** 168367 points

    Stuart,

    The message you are getting comes from the fact the Trace analyzer is not able to properly get the system clock information from the device registers. At a certain point in time this was a problem for several devices, therefore it is possible this may be the case of the older version of CCS used.

    At any rate, the fix for this is quite simple: you can set the system clock manually by clicking on "Advanced Settings" and expanding the options below. 

    Fill the clock parameters with the correct System Clock configured for the system you are working on. 

    Hope this helps,

    Rafael