• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1086 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.

Debbuging DM3730 ARM and DSP simultaneously

Avner Gidron
Prodigy 90 points

Other Parts Discussed in Thread: DM3730

Hi,

I am using the DM3730 with logicpd torpedo SOM and CCS v5.3 with an Emulator spectrom digital xds200.

I want to debbug both of the CPUs simultaneously. the Arm should run an apk while the DSP should run a ccs project.

for now, I manneged to debbug the DSP from the CCS and the xds200 and the apk from ADB. the problem is that the two can't work togther...

is there a way to debbug them both?

thanks alot!

Avner

  • 0
    TI__Guru**** 171729 points
    Avner,

    I am not well versed on using CCS to debug Android applications using ADB (perhaps the experts in the DaVinci forum will be able to help you better on this particular topic), but we do a similar thing with Linux debugging, where we simultaneously launch a JTAG/low-level debug session that connects to the core (or cores) and a GDB session that connects to the Linux application running on the master core.

    For details on how we do this, check section 5 of the page below:

    processors.wiki.ti.com/.../Linux_Debug_in_CCSv5

    An older page that touches the same subject but uses older components can be found at:

    processors.wiki.ti.com/.../Debugging_the_DSP_side_of_a_CE_application_using_CCS

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 90 points
    Hi Rafael,
    thanks for the response! I tried something simaller to what was written in the links you posted and at first it didn't work. but when I changed my OS to UBUNTU it suddenly worked. I now able to load the symboles of my code to the DSP while the ARM is running the app with the ADB connected. if anybody come across this problem again a few steps that I recommend about are:
    (1) making sure you are building your program in debug mode.
    (2) making sure the code that is running is the same as the symbols that you are loading.
    (3) if you want to debug the slave CPU you must make sure that the master will take it out of reset.
    (4) as I said, it only works for me when I use Linux but I'm not sure that this is a must.

    So thanks again and happy debugging to me :)
    Avner