• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 100 subscribers
  • Views 891 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Debugging SYSBIOS based DSP side executable of an ARM+DSP application

Rahul Prabhu
Guru** 116020 points

Hi everyone,

I am trying to debug an ARM+DSP application on DM8148 where in the ARM application loads a BIOS 6 based excutable on the DSP. The debugging steps and setup is as  mentioned in the wiki mentioned below.

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

The code on the DSP side uses framework components to allocate and manage EDMA resources using IRES interface. To debug the application I have enabled the logging and debuging in framework components using

http://processors.wiki.ti.com/index.php/Trace_in_Framework_Components#Framework_Components_3.20

The code on the DSP uses log_print statements to create a debug log which I need to be able to see in the RTA tool in CCS. However when I load the symbols from the executable after halting the ARM side application, CCS does not allow me to open the RTA window after I connect to the DSP. This prevents me from collecting all the debug log information that is being obtained from the DSP side of the application.  Has any body tried this debug setup? Are there other ways of collecting trace.

I have posted a similar question in the CCS forums but I am not sure they have tried this debug environment in their test setup.

Regards,

Rahul