• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 1274 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.

CCS/AM5728: Connecting to application with GDB Debugger

Rob Barton
Expert 2220 points
Part Number: AM5728


Tool/software: Code Composer Studio

I have the processor training hands on with Linux SDK.

In the section for debugging with CCS and GDB it covers how to make the connection and debug with GDB debugger.

In the case of a file being built, the source code being provided, how do I use code composer to 'run' the application on the Linux AM5728 platform and debug it with code composer?

Can I somehow 'load the symbolic debug information' and point to where the C files are and be able to step through the code, even though I haven't compiled it through code composer?  ie:   I haven't create a project file.... the file was compiled directly with a make file no code composer.

We are talking about building an application that runs on the Linux on the AM5728.

Or must I create a project file, compile it with code composer, copy the file to the target system, run it with GDB Debugger, and then debug it?

  • 0
    Expert 2220 points

    If I can I'd like to extend this question a bit.  I have a Linux PC that can connect via GDB debugger, to the A15, and I can connect to the PRU's and the DSPs as well.  However I'm noticing that to connect to the PRU_0_ICSS1 I have to suspend both A15's, it's as if there is some interaction going on there that prevents it from connecting.

    Also, how do I load symbolic information on the PRU's, is it as simple as Run|Load|LoadSymbols and select the compiled symbol file for it?

    Where can I find the startup process of interaction between the A15 and the PRUs to understand what happens when I reset the PRU, what is it waiting for from the A15, I seem to have to run the A15, to get it past startup, then halt the A15 to connect to PRU0...

    If I want to debug between the PRU and the A15, if I am using GDB Debugger on the A15, what is a 'startup' procedure to have them interact nicely?

    Thanks.

  • 0
    TI__Guru**** 171309 points
    Hi,

    >>In the case of a file being built, the source code being provided, how do I use code composer to 'run' the application on the Linux AM5728 platform and debug it with code composer?

    In general the GDB server in the target processor is the responsible to load the application to memory and halt its execution waiting for a remote GDB client to be connected. The GDB client will then control the GDB server and run, halt, set breakpoints, etc.

    >> Can I somehow 'load the symbolic debug information' and point to where the C files are and be able to step through the code, even though I haven't compiled it through code composer?

    Certainly so. The GDB client will be the responsible for loading symbols to the debugger interface - in Eclipse/CCS this is done via the menu Run --> Load --> Load Symbols.

    >> Or must I create a project file, compile it with code composer, copy the file to the target system, run it with GDB Debugger, and then debug it?

    For a better debugging experience, the code built from inside CCS will allow a more thorough navigation of the various source files, libraries, etc. However, building the application externally and loading the symbols as mentioned above also works, but with some extra effort to properly navigate the source tree.

    I think the training below will be very informative for your Linux application debug using CCS.
    https://youtu.be/JpXJ-F5QqOo

    Hope this helps,
    Rafael