analyze reboot reason

RE: analyze reboot reason

Håkon Alseth — Wed, 15 Sep 2021 10:21:45 GMT

Hi,

[quote user="kamacode"]one option: HW releted reset, may be due to the power cunsumption peaks of the modem[/quote]

This will show the reset value of RESETREAS, which is "none" in your implementation as it is now.

[quote user="kamacode"]

as I said, on some cases I do get failure and then kernel error prints , followed by resset. that's easy to analyze, I can always read crash prints, look at the map file , find the code in the relevant address and fix the issue

the problem is that some of the time I just get a reset without any warning.

[/quote]

To catch this, you need to debug the actual failure, and not the reset cause. The fault itself might cause the serial print to fail.

Try adding blocking assertions (for debug reasons), by setting CONFIG_RESET_ON_FATAL_ERROR=n (do this for secure region as well) and see if you can catch the fault.

Kind regards,

Håkon

RE: analyze reboot reason

kamacode — Tue, 14 Sep 2021 12:09:31 GMT

no, I do not get a print .

the problem is that some of the time I just get a reset without any warning.

one option: HW releted reset, may be due to the power cunsumption peaks of the modem

second option: some SW related reset

si I would like to know how can I best use the RESETREAS and any other means I have to analyze reset cause and source

thank you

RE: analyze reboot reason

Håkon Alseth — Tue, 14 Sep 2021 12:04:49 GMT

Hi,

[quote user=""]

in case I get "DOG", ok reason is clear, but usually I get "SREQ", what does it mean?

[/quote]

That is a soft reset, usually via firmware triggered reset (NVIC_SystemReset()):

https://infocenter.nordicsemi.com/topic/ps_nrf9160/power.html?cp=2_0_0_4_2_0_0_13#register.RESETREAS

The default behavior when you get an assertion or a fault in zephyr is to print the failure on serial and then do a soft-reset. Do you get a printed failure message or similar before it rebooted?

Kind regards,

Håkon