• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 308 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.

Initiating the debugger is time consuming....

Markus Grunwald
Expert 2060 points

Hello,

I'm using CCS only as a debugger for the Integra platform. Code ( a syslink application) is written and compiled on linux. Whenever I start to debug, I have to:

  • start the firmware on the device
  • Open the debug dropdown in CCS and select my integra.ccxml. The debugger starts.
  • Click run -> load ->  App.xe674 to load the symbols
  • Right click on " Texas Instruments XDS100v2 USB Emulator_0/C674X_0" and select  "connect target"
  • wait, then: wait some more.
  • set breakpoints (sometimes - sometimes, the breakpoints from the last session are sufficient.)
  • Change my blocking variable, which prevents the firmware from "running away" before the debugger is ready to 0
  • "Continue" debugging

Each of the steps is necessary, but is there some way to automate this? In gdb I would just write a short script which does all the work and I hope something similar is possible in CCS, too...

Thanks for your help,

Markus

  • 0
    TI__Guru**** 171729 points

    Markus,

    There is a way to shave a few steps:

    You can automate a bit the launch and symbol loading by modifying the Debug Configurations - check the short clip Multicore debug launch made easy at the CCSv5 Video Tutorials page:

    http://processors.wiki.ti.com/index.php/Video_Tutorials_CCSv5

    Also, you can import/export the breakpoints to a file. Just right-click on the Breakpoints view and there are two options at the bottom of the drop down menu.

    I can't think of an easy way to automate the modification to the value of the variable, though.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 2060 points

    Hello Rafael,

    many thanks for your reply. Automatically loading the symbols is a relief that I very much appreciate :) The breakpoints are almost no issue, but it's good to know.

    So the main problem is solved, thank you :)

    I understand that the debugger is generally not scriptable?

    cu

    Markus