OMAP-L138 DSP backtrace

Will Lentz

Other Parts Discussed in Thread: OMAP-L138

Hi,

My OMAP-L138 DSP application is having a problem and so it calls SYS_abort(). I'm trying to figure out why, so I compiled with: -g --symdebug:dwarf --opt_level=0

Even with those options my backtrace in CCS 4 is limited to:

0 app_fatal_error()

1 lclDspAbort()

2 SYS_abort()

Is there any reason the backtrace should stop at SYS_abort()? Or is there any way to get the backtrace to go further?

Thanks,

Will

over 14 years ago

0 desouza over 14 years ago

TI__Guru**** 169794 points

Will,

Usually the backtrace goes back to where the stack still maintained its integrity - i.e., if it happens a corruption of the memory region where the stack was allocated the information is lost or bogus. I wonder if that is what may be happening in your case.

There is a reference and some interesting discussions about call stack in the embedded software forums, therefore you may want to ask this question there as well with additional details about the BIOS version and any components you may be using (Link, Codec Engine, etc).

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

http://e2e.ti.com/support/embedded/f/355/p/48855/174257.aspx#174257

http://e2e.ti.com/support/embedded/f/355/p/50011/177280.aspx#177280

Hope this helps,

Rafael