Debugging DSPLink - CCS4

Weihua Sheng

Other Parts Discussed in Thread: OMAP3530

Hello,

I am following the link to use CCS4 debugging DSPLINK apps

http://tiexpressdsp.com/index.php/Debugging_the_DSP_side_of_a_DSPLink_application_on_OMAP_using_CCS

I am using a XDS510USB PLUS to connect to the board. The development (compilng dsplink apps, etc.) is done on Linux, CCS4 is just used as a debugger. There's a particular step using "CCS Parallel Debug Manager" which I could not find in the CCS4 version. Where can I find this in the new CCS4? Also, I would like to see trace (e.g. LOG_print*) in the trace window. I somehow loaded the dsp code in (assembly/c can be seen), but the trace window is grayed - it says this hardware is not trace enabled. How can I enable the trace on?

Thank you.

over 16 years ago

0 Brad Griffis over 16 years ago

TI__Guru*** 125430 points

http://tiexpressdsp.com/index.php/Multi-Core_Debug_with_CCS

Note also that the "GEL" menu from CCS 3.3 has been replaced with the "Scripts" menu in CCS 4.

0 Weihua Sheng over 16 years ago in reply to Brad Griffis

Intellectual 600 points

Well, thanks for the link, but our situation is a bit different. Let me explain.

The wiki article is about to debug a project being developed in CCS. Our development is solely on linux, therefore we just use non-project debug session in CCS. We used tskMessage as an example (we also tried our own developed code). Here's the following procedure:

1. start CCS-> load TI debugger (we use the MISTRAL_OMAP3530_XDS... as target).

2. then we run "messagegpp message.out 1" (we changed the code according to the wiki article, http://tiexpressdsp.com/index.php/Debugging_the_DSP_side_of_a_DSPLink_application_on_OMAP_using_CCS), and ARM runs till "Hit Key..."

3. In CCS, we do "connect...", it's succesful and we load message.out, so we could see C/Assembly code and move PC after the while loop (see wiki article) and debug a bit.

4. The problem is no trace (see screenshot), We would like to see LOG_printf from the dsp code in this example.

Any suggestions to make the LOG_printf work TRACE window?

Thanks!

0 Brad Griffis over 16 years ago in reply to Weihua Sheng

TI__Guru*** 125430 points

Make sure you do "load symbols" and not "load file". Also, please see this article on RTA issues:

http://tiexpressdsp.com/wiki/index.php?title=DSP/BIOS_Real-time_Analysis_%28RTA%29_troubleshooting

Specifically look at Section 2.3 "Trace must be enabled". That section applies specifically to DSP/BIOS Link which happens to turn off some of the necessary trace masks by default. That's likely your issue.

Brad

0 Weihua Sheng over 16 years ago in reply to Brad Griffis

Intellectual 600 points

Yes, we did "load symbols". Thanks for the wiki link, we followed it and still couldn't get the TRACE working. Any suggestions that we would look into elsewhere?

Another question is that for most the wiki-articles, people develop dsp applications using CCS and debug them thru JTAG. In our situation, we develop apps (both arm and dsp) on Linux and just use the CCS as debugger to see DSP inside. Is it the recommended way?

Thanks

0 Brad Griffis over 16 years ago in reply to Weihua Sheng

TI__Guru*** 125430 points

Ah, yes, I just looked at your screenshot and that triggered some memories. I've had some issues getting the log viewer to work. There's a slightly different way to do it by going to Tools -> ROV. Then you can go to ti.bios.LOG and view the trace logs from there.

This video shows you the process, though it's near the very end if you don't want to watch it all. It was made a while ago so there may be some slight changes to the menus/names between then and the final CCS 4 version.

Brad

Processors

Processors forum

Debugging DSPLink - CCS4