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.

collecting data for offline stack backtrace

Other Parts Discussed in Thread: SYSBIOS

We are going to run lots of application on C6657 running sysBios and CGT 7.3.1, which were previously designed for Linux or vxWorks on host processor.

To prepare for the unexpected, we would like to have the capability to do a stack back trace on DSP without jtag connection and not talking with CCS. As no stack back trace tool is available, we plan to use exception handler to capture the core registers including pc and sp, as well as the associated stack, system stack or task stack. Our host processor can grab these data and save it into files which we can later load into a target running the same version of code using jtag and CCS. We hope that we get some information on how  we get the exception.

We heard that there is a jtag backtrace buffer which keeps track of the stack frames and jtag/ccs use it to build the backtrace. Is there any information on it so that we can make use of it for our debugging as well.

thnaks

WEichun

thanks

Weichun

  • Weichun,

    I don't know of a jtag backtrace buffer.  The C6657 device does have an Embedded Trace Buffer.  This is onchip memory that can be used to store trace data instead of sending it out over pins.  Typically you capture PC or data trace.  There is a set of libraries available that you can embedded in your application for controlling trace and managing the ETB.

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

    Regards,

    John