I'm trying to debug the following assertion:
ti.sysbios.gates.GateMutex: line 114: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details.
I understand the meaning of the assertion and it is certainly possible I have a print or something else getting called from an ISR that I shouldn't be called that way. I have fixed similar issues by assuming the source of the problem, but this isn't a very efficient way to work. It would be much better to get a stack trace so I can see exactly what is leading to the GateMutex assertion.
My question is similar to the one posed here but I can't glean from this thread how to get myself a stack trace on assertion: http://e2e.ti.com/support/embedded/f/355/p/107518/379888.aspx. I changed the RTSC build profile from whole_program to debug but this is all the stack info I get in the debug window when the assertion fails:
abort() at exit.c:99 0x00299DC0 (abort has only skeletal debug info)
What am I missing in my build that prevents the debugger from giving me a stack trace?
Thanks in advance.
Environment info:
ti.targets.C64P
ti.platforms.evm6472
SYS/BIOS 6.31.04.27
XDCtools 3.20.08.88
CCS 5.0.2
