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/LAUNCHXL-CC26X2R1: Deciphering CPU Exceptions Using TI-RTOS and ROV to Parse Exceptions > not working

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi,

CCS: 8.3.1.00004 

XDS: 3.51.2.21

SDK: simplelink_cc13x2_26x2_sdk_3_10_00_53

Doc: simplelink_cc13x2_26x2_sdk_3_10_00_53/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#ti-rtos-object-viewer

Using simle peripheral, I have applied the patches as shown but the exceptions are not decoded, please advise on the missing steps :

  • Updated '.cfg.' with 'execHandlerHook'
  • Patched package.xs for ROV Classsic
  • ???

For sole purpose of demonstrating the following screenshot I have set a pointer to NULL using the debugger. 

  • Hi Jerome,

    The reason it looks a bit odd is that the code that's supposed to fill in the exception context object isn't executed.

    It seems that you have combined the excHandlerFunc = null that existed in the cfg file with the excHookFunc = "&myExcHook"; from the documentation. Let me recommend that you just comment out excHandlerFunc, and add an extra line with the hook function.

    You should also find that commenting out the ROM part at the top of the .cfg file makes CCS more willing to understand and decode the call stack. Alternatively you can load the symbols for the RTOS ROM content via Run -> Load -> Add symbols -> Browse -> <sdk>\kernel\tirtos\packages\ti\sysbios\rom\cortexm\cc26xx\cc26x2v2\golden\CC26xx\CC26X2V2_rtos_rom_syms.out. You will find zipped sources for the ROM build in the same folder.

    Best regards,
    Aslak