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.

RTOS/CC3220SF-LAUNCHXL: How to debug Hwi_excHandler

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

Tool/software: TI-RTOS

Hi

I have a customer who is using CC3220 with simplelink_cc32xx_sdk_1_50_00_06.
They encounter unexpected exception during development and wants to know which is the cause of the exception.
  
 
Is there any recommended way to debug such situation?
Customer already tried to change Hwi.enableException setting to true in SYSBIOS *.cfg file, but it does not work.
Is this supported on CC3220?

/*

* The following options alter the system's behavior when a hardware exception

* is detected.

*

* Pick one:

* - Hwi.enableException = true

*     This option causes the default m3Hwi.excHandlerFunc function to fully

*     decode an exception and dump the registers to the system console.

*     This option raises errors in the Error module and displays the

*     exception in ROV.

* - Hwi.enableException = false

*     This option reduces code footprint by not decoding or printing the

*     exception to the system console.

*     It however still raises errors in the Error module and displays the

*    exception in ROV.

* - Hwi.excHandlerFunc = null

*     This is the most aggressive option for code footprint savings; but it

*     can difficult to debug exceptions. It reduces flash footprint by

*     plugging in a default while(1) trap when exception occur. This option

*     does not raise an error with the Error module.

*/

m3Hwi.enableException = true;

//m3Hwi.enableException = false;

//m3Hwi.excHandlerFunc = null;

Thanks and regards,
KoT