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

linux debug with CCS vs Other Gui GDB

ranchu
Guru 20755 points


Hello,

I would like to ask what is the added value of using CCS for linux debugging instead of other Gui GDB. As I understand CCS also used GDB.

Best Regards,

Ran

  • 0
    TI__Guru**** 171309 points

    Ran,

    CCS aggregates two debugging scenarios: Linux applications debugging (using GDB) and low-level device debugging (using a JTAG emulator).

    I agree with you regarding the first scenario; GDB debugging can be used by a multitude of IDEs and even using the command-line based GDB. CCS uses only open source components while debugging in this mode anyways.

    However, the second scenario is where CCS is crucial. By means of the JTAG emulator you are able to debug the Linux kernel and have complete visibility of the low-level internals of the device (useful for debugging the bootstrap, device drivers and other low-level components).

    You can also use both scenarios consecutively, in case you need to debug a kernel module that is called from a Linux application. Check:

    http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5#Mixed_Mode_Debug

    Regards,

    Rafael