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.

[FAQ] How to Trick the CCS debugger into providing a blocked TI-RTOS (SYS/BIOS) task call stack on Cortex-M devices

Other Parts Discussed in Thread: SYSBIOS

Beginning with SYS/BIOS release, the Task module provides a non-invasive per task CallStack ROV view.

The instructions below are for SYS/BIOS versions before (that do not support these built in ROV views).

After connecting to the Cortex-M core:

  1. Using the disassembly window, find the address of this symbol: ti_sysbios_knl_Task_swapReturn
  2. Put that address + 4 into the PC register.
  3. In the Task ROV 'Raw' view, find the 'context' field of the task Instance State you're interested in.
  4. Place the value of 'context' into both the MSP and PSP registers.
  5. Single step ONE instruction (using "Assembly Step Into") for M3/M4 targets or TWO instructions for M4F targets. The debugger window should now show you a rough approximation of the task's call stack. The program is NOT continue-able at this point because the register context at the point of halting the CPU is lost.