Nrf Connect SDK program halt after a few days

RE: Nrf Connect SDK program halt after a few days

Alexandre Desgagne — Thu, 09 Dec 2021 17:00:16 GMT

Thanks !

Alexandre

RE: Nrf Connect SDK program halt after a few days

Marjeris Romero — Thu, 09 Dec 2021 16:53:05 GMT

Hi Alexandre,

The changes have been merged upstream but it's not in our Zephyr fork yet. The easiest in the meantime is just to change the variable type to int64_t locally inside the file zephyr\subsys\task_wdt\task_wdt.c

Best regards,

Marjeris

RE: Nrf Connect SDK program halt after a few days

Alexandre Desgagne — Tue, 07 Dec 2021 14:03:39 GMT

Hi Marjeris,

It seems exactly like my problem. I wonder if you know how I can update Zephyr to get these change on my side?

Thanks a lot!

Alexandre

RE: Nrf Connect SDK program halt after a few days

Marjeris Romero — Tue, 07 Dec 2021 10:43:40 GMT

Hi Alexandre,

I think this issue could be linked to the bug reported in this PR: https://github.com/zephyrproject-rtos/zephyr/pull/40363

The fix inside the PR, changing the 'current_ticks' variable to a 64-bit integer in zephyr\subsys\task_wdt\task_wdt.c in the SDK should fix the overflow issue.

Best regards,

Marjeris

RE: Nrf Connect SDK program halt after a few days

Alexandre Desgagne — Mon, 06 Dec 2021 15:29:52 GMT

UPDATE:

Hi,

As I mentioned previously, I did a debugger session to try to find something. The firmware stopped working after 36h24m30sec. The tasks stopped working and the program started looping somewhere. I pressed "pause" in my debugging session and here's the result.

The program seems to halt in the set_absolute_alarm function in the nrf_rtc_timer.c file.

This is the call stack:

As I can see, I think it may be something about the task watchdog. Maybe I have something not properly set?

I will continue to debug.

Thanks!

Alexandre