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.

LAUNCHXL-CC1352P: ti154stack enter Main_excHandler

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P

Hi team,

Here's an issue from the customer may need your help:

Built on the CC1352P_2_LAUNCHXL\ti154stack\ccollector_2_4g project based on the simplelink_cc13xx_cc26xx_sdk_5_30_01_01 stack Networks.

About 30 sensor connected under the network, and the protocol for collector and sensor communication within the network is customized. Sometimes the collector enters Main_excHandler (UInt * excStack, UInt lr) and report hard fault.

The code that enters abnormality: xdcRomConstPtr, as shown in the following figure:

Issue:

The value of lr passed to the Main_excHandler (UInt * excStack, UInt lr) function is 0xFFFFFFFD, and the array of excStack has the following value:

Since IAR debug can only see the contents of the xdcRomConstPtr assembly section at error, the customer would like to know how to confirm where the exception occurred.

What are the factors that cause entry into Main_excHandler when running the xdcRomConstPtr function?

Is it related to the higher frequency of interaction between collector and sensor? The following figure shows a record of a partial packet capture:

The CFSR value is 0x00008200 at the time of hardfault:

Could you help check this case? Thanks.

Best Regards,

Cherry