For sometime now, I've heavily relied on print statements to debug my Linux user code when developing.  With Code Composer Studio (CCS) v5 supported on a Linux host, I decided to take a look at how to leverage the IDE to debug my Linux user level code.  To my surprise (well not much since it's Eclipse based),  CCS leverages the GNU Debugger (GDB) remote capabilities to allow for Linux debugging on TI devices.  The most difficult part of using CCS for this was to find a compatible GDB (for host PC) and GDBserver (for the target).

I've outlined some basic information and steps to get you going.  The topic uses the SysLink product as an example but the concepts are applicable to most any Linux debugging environment.  

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

Enjoy

Anonymous
Parents
  • Arnie,

    Thank you for the post. I'm currently running Ubuntu 10.4 LTS, so my MPS430 development options seem to be (1)  Stop what I'm doing and switch to MSWInXP every time I want to do MSP430 development -- and then reboot to Ubuntu afterwards, or (2) use mspgcc and mspdebug, which I am currently doing, or (3) try to get ccsv5.1 running under a VM such as VirtualBox.

    Any word on when MSP430/CCS/Linux will be available, that is, when CCS v5.2 will be released?

    Thanks...

    Frank McKenney

Comment
  • Arnie,

    Thank you for the post. I'm currently running Ubuntu 10.4 LTS, so my MPS430 development options seem to be (1)  Stop what I'm doing and switch to MSWInXP every time I want to do MSP430 development -- and then reboot to Ubuntu afterwards, or (2) use mspgcc and mspdebug, which I am currently doing, or (3) try to get ccsv5.1 running under a VM such as VirtualBox.

    Any word on when MSP430/CCS/Linux will be available, that is, when CCS v5.2 will be released?

    Thanks...

    Frank McKenney

Children
No Data