How to get reset reason

[thomas oggier]

Hi,

I would like to get some information about the reset's reason of my nrf9160 like

- The reason is due of an assert type "xxx"

- Where is the stack pointer

- ...

Exist it some function in Zephyr already implemented to get this informations?

After, when the program starts, he will send this informations via MQTT to my server to be able to remotely troubleshoot the device.

Thanks for your help!

[Håkon Alseth]

Hi,

 

We do not have an example that shows storing errors/fault information to flash, unfortunately.

 

The fault handling in zephyr is described here:

https://devzone.nordicsemi.com/f/nordic-q-a/54899/zephyr-recommended-unexpected-exception-handling-method

 

The zephyr fatal docs can be found here:

https://docs.zephyrproject.org/latest/reference/kernel/other/fatal.html

 

Note that since you're using nrf9160, you have two regions. Secure and non-secure. The type of fault will determine which region you end up in, for instance a hardfault will end up in the secure domain.

You can read more about this in ARMs M33 docs: https://developer.arm.com/documentation/100235/0004/the-cortex-m33-processor/exception-model/exception-types?lang=en

 

Kind regards,

Håkon

[thomas oggier]

Hi, thanks for your help,

Do you know if there is some possibility to get the last log value (print before the reset) when the program starts?

Like read the log_queue?

[Håkon Alseth]

I am sorry, but I'm not aware of such a function. I could not find any references to such in the logging module API or docs:

https://docs.zephyrproject.org/latest/reference/logging/index.html

 

Kind regards,

Håkon