ccsv5_full_symb_debug.

hello Mushtaq,

Mushtaq Syed said:

when I run the code under CCSv5 with 'full symbolic debug' enabled, I am running out of MIPS and I am unable to debug.

I'm not sure how running with full symbolic debug is causing your application to run out of MIPS and unable to debug. Could you please explain this?

ki

Hi Ki-Soo:

When I enable 'Full Symbolic Debug' and build the DSP code, the size of the DSP code goes up to 6863723 (see below). If I use this, then I get underruns (see ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred below); however, if I strip off the debug code using the TI utility strip6x, then I don't have this issue.

Thanks a lot!

Cheers,

Mushtaq

-rw-------    1 root     root       6863723 Apr 19 10:16 audion.out
-r--------    1 root     root        268021 Apr 18 09:40 audion_orig.out

       0.691 DSP: Version Minor: 8
       0.691 DSP: Product Minor Version: 0
       0.692 DSP: Product Revision: 0

       0.692 DSP: SE VERSION HIGH BYTE: 28

       0.692 DSP: SE VERSION LOW BYTE: 15

       0.723 Ignoring: CodReadCnt = 1, nBytesRead = 1152
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
      11.675 [at.c]: ProcessResult AEC Configuration Test Results  ERL1: -6.9 dB ERL2: -6.9 dB ERL3: -6.9 dB ERL4: -6.9 dB
      11.676 [at.c]: ProcessResult AEC Configuration Test Results  ERLE1: 0.0 dB ERLE2: 0.0 dB ERLE3: 0.0 dB ERLE4: 0.0 dB
      11.677 Posting q.semTerminate1...
      11.679
      11.680 TRM: Current date and time: Fri Apr 19 10:18:18 2013
      11.681 TRM: B0:E54:? Normal Termination
      11.683

/g3n/badge/data/log.txt written.
[root@badge bin]#

Mushtaq Syed said:

When I enable 'Full Symbolic Debug' and build the DSP code, the size of the DSP code goes up to 6863723 (see below)

Yes, the out file size gets bigger because there is more symbolic information in the out file. This is fully expected. Note that this size is NOT your actual target code size. The symbols get loaded into the debugger, not the target. The actual target code is just a part of the out file.

Mushtaq Syed said:

If I use this, then I get underruns (see ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred below); however, if I strip off the debug code using the TI utility strip6x, then I don't have this issue.

All the strip does is remove the debug symbols. Your actual DSP code is the same. So really your target application should not run any different.

I don't know what this "underrun" is. Is that message coming from the target application?

Hi Ki-Soo:

Yes, the message is coming from the target application. As, I had mentioned in my first post, our platform has an OMAP L138 running under Linux. The underruns are from the ALSA audio codec driver. These underruns do not occur when I strip off the debug information.

Thanks a lot!

Cheers,

Mushatq

Can someone please point me where I can find the strip6x application?  I am using CCSv5 with the C2000 family.

Thank you!

Cyril Lance said:

Can someone please point me where I can find the strip6x application?  I am using CCSv5 with the C2000 family.

You'd want to use strip2000 instead. It comes with your compiler install:

<CCS INSTALL DIR>\ccsv5\tools\compiler\c2000_<version>\bin