WDT: store debug data for reboot

RE: WDT: store debug data for reboot

Edvin — Thu, 02 Jul 2020 14:17:01 GMT

Hello,

A colleague of mine said that you can try this solution:

https://devzone.nordicsemi.com/f/nordic-q-a/30075/saving-the-location-of-watchdog-timeout

The RAM is not reset during a WDT reset.

BR,

Edvin

RE: WDT: store debug data for reboot

lubedence — Thu, 02 Jul 2020 14:08:12 GMT

Hi,

I am pretty sure it is not a WDT configuration problem. Even though, I would be still interested how to tackle such a problem.

Regarding UART: already tried that, is too slow :(

Regarding RTT: I would be very happy if I do not need to use RTT + JLink, but I guess I have to try that as a last resort.

Isn't there another solution?

Thanks

RE: WDT: store debug data for reboot

Edvin — Thu, 02 Jul 2020 13:56:05 GMT

Hello,

Have you tried to log something in the WDT event handler? As you say, you only have two cycles of the LFCLK, but if you use RTT logging I believe you will be able to log some information. (UART is too slow, so no point in using that).

From where do you feed the WDT? Is it possible that you only feed it in certain events, and that you simply didn't have any events firing causing the WDT to time out?

What is your watchdog configuration? (pause/run in sleep/halt) You can check this by reading out the CONFIG register after the WDT is initialized.

Best regards,

Edvin