debuggingmicrocontrollerautosartrace32lauterbach

How to debug the software reset in the ECU


I would like to understand how to debug and find the root cause of a software reset or a Vector Catch reset. Suppose I am using the AUTOSAR framework, and when I flash the code, I am experiencing continuous resets.

I want to know what the possible ways are to debug the software reset in the ECU. Some of the ways I found like stack trace, logs print, etc.

Are there any other ways?


Solution

  • If you are able to run the code for at least some instructions sets, I will recommend first to have a look at the reset flags of status registers. Depends on the microcontroller, you can get useful information for the beginning in order to isolate your reset cause and understand from which module/zone is coming the reset/vector catch.

    The search area for such things is quite large and there can be problems on the order of read/write RAM, incorrect PORT initialization, etc.