• Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 1306 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.

CCS: Exception call stack <symbol is not available>

Matthew Hall
Intellectual 435 points

Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

I'm trying to determine the cause of an exception. I have a breakpoint set in my handler exception hook, which receives the Hwi_ExcContext pointer. Unfortunately, when I read the Hwi module, the Exception call stack shows the very unhelpful message of "<symbol is not available>"

What is the solution here? I do not have a stack overflow. 

The issue I'm having is exactly the same as found here: e2e.ti.com/.../2094531

Sadly, the linked thread's solution is not helpful. It simply points to a wiki which describes how to use outdated software.

  • TI__Guru**** 483321 points
    Hi Matthew,
    I see that you have posted in the TI-RTOS forum. Did you create a new thread there as Todd requested? The folks in that forum can help you best.

    Thanks
    ki
  • in reply to Ki
    Intellectual 435 points
    I created the new thread here, in the CCS forum, as this is an issue I'm having with CCS. Is this the incorrect forum? Can you please just help me answer the question?
  • in reply to Matthew Hall
    TI__Guru**** 483321 points
    CCS is the debugger being used but the issue appears to be specific to TI-RTOS. There is a dedicated forum for TI-RTOS. I see that you had replied to an existing thread there. I will move this thread to that forum.

    Thanks
    ki
  • in reply to Ki
    TI__Genius 12025 points

    Matthew,

    Debugging exceptions is a challenge on a good day. But the Hwi exception dump is your best tool in these situations. As detailed in the FAQ below, your first step is to take the PC, SP, and LR register values from the dump and put them into their respective registers in the CCS Register View. Hopefully, this will recreate a useful call stack.

    Exception Dump Decoding Using the CCS Register View

    If this does not yield a useful call stack, then your next step is to rebuild the TI-RTOS kernel with debug profile. Look in your program cfg file and change the BIOS library type to debug.

    var BIOS = xdc.useModule('ti.sysbios.BIOS');
    BIOS.libType = BIOS.LibType_Debug;

    What device are you using?

    What software release are you using?

    ~Ramsey