Hi,
I'm using the mcu_plus_sdk_243x.
During the code development , sometimes I get into HwiP_undefined_handler.
Is it possible to read the pc , lr,sp registers to find crash origin ?
Thanks,
Eli
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.
Hi,
I'm using the mcu_plus_sdk_243x.
During the code development , sometimes I get into HwiP_undefined_handler.
Is it possible to read the pc , lr,sp registers to find crash origin ?
Thanks,
Eli
Hi Eli,
You can check the LR register to see the last jump. Which might give some insight.
Can you share the more detail on the application. Is this a SDK application? What is scenario and when you are running into this issue?
Regards,
Ankur
Hi,
Somewhere I have a call to compiler's new instead of pvPortMalloc and then all crashes.
Thanks,
Eli
Hi Eli
Have you tried stepping into the new function and been able to isolate the exact access which causes the crash?
We have taken an action to see if we can provide more debug log functionality in the TI default handlers to make debugging such issues easier. In the interim, if you could step through the code and isolate the point of crash that would help rootcause the exact issue you are facing.
Regards
Piyali
Hi Piyali,
Is there any short log that can be built like a cyclic buffer trace to look at just after the crash, like there's a core dump in Linux ?
Thanks,
Eli
Hi Eli,
You can get a short trace using the CCS core trace feature. Please check https://www.youtube.com/watch?v=PXMvAnzA7Vs
Regards,
Ankur