SDK: 15.3.0
Device: EYSHJNZWZ (nRF52832)
Is there a way to know the cause of the reset?
I connect the PC to the device and run it in debug mode.
However, nothing is written to the log when the reset occurs.
I want to know what caused the reset.
SDK: 15.3.0
Device: EYSHJNZWZ (nRF52832)
Is there a way to know the cause of the reset?
I connect the PC to the device and run it in debug mode.
However, nothing is written to the log when the reset occurs.
I want to know what caused the reset.
Hi Takashina,
It's possible to know the cause of the last reset. In your code you can check the register RESETREAS to know the reset reason. Please have a look at section 18.6 in the NRF52 product specification.
However, it's most likely a reset when there is an assertion. Please follow this guide on how to set your device to debug mode and get the assertion reason printed out on the log: https://devzone.nordicsemi.com/question/60125/my-device-is-freezing-and-restarting/#60126
Thank you for answering.
I will try it.
I tried it the way I taught.
>> It's possible to know the cause of the last reset.In your code you can check the register RESETREAS to know the reset reason.
>> Please have a look at section 18.6 in the NRF52 product specification.
Indicates the "RESETREAS" status when a reset occurs.
At this time, I intentionally reset by WDT.
Other than "RESETPIN", it looks like "NotDetected".
I assumed that "DOG" would be "Detected".
Is the confirmation method bad?
Please tell me why this result.
>> However, it's most likely a reset when there is an assertion.
>> Please follow this guide on how to set your device to debug mode and get the assertion reason printed out on the log: devzone.nordicsemi.com/.../my-device-is-freezing-and- restarting / # 60126
I caused a reset by WDT in "DEBUG" mode, but no log was output.
Isn't log output when reset by WDT?
Please tell me.