zephyr software timer cannot trigger periodically.

[hjq]

I am using the NRF54L05.When I was using the timer function of the Zephyr software, I created a timer with a 10ms cycle. After my system had been running for a long time (for example, 12 hours), after executing sys_reboot(SYS_REBOOT_COLD);, there was a probability of encountering a timer anomaly. It did not trigger as I expected; it only triggered once, and the next trigger time was much later;

相关代码使用：   

FRAME_INTVAL_UINT 10  // 毫秒

  k_timer_init （& delay_timer ，delay_timer_handler ，NULL ）；

  k_timer_start （& delay_timer ，K_MSEC （（uint32_t ）FRAME_INTVAL_UINT ），

                K_MSEC （（uint32_t ）FRAME_INTVAL_UINT ））；

I obtained the trigger count and the next time from the delay_timer through k_timer_status_get(&delay_timer) and k_timer_remaining_get(&delay_timer) respectively.The results I got were 1 and 11814496;

I can confirm that my clocks are all functioning properly, and my delay_work and threads are also running normally. I have no idea how to proceed to identify the problem;

Thank you very much for your help;

[Benjamin]

Hi,
Do you have any application logs that demonstrate this issue?

Regards,
Benjamin

[hjq]

Hi,

In the main function, I use the k_timer_remaining_get function to query the next expiration time of the clock once every 1 second.

The log printing time is as follows:

[Benjamin]

Thanks, and do you see this remaining time decrease?

[hjq]

yes，The remaining time is decreasing, and it decreases by 1 second each time.

[Benjamin]

I’d like to forward this to someone who can provide a more detailed answer. Please confirm that I’ve understood your issue correctly.

You’re using a custom board with the nRF54L05. After the device has been running for about 12 hours and performs a sys_reboot(), the timer no longer fires as expected. When you call k_timer_remaining_get() after the issue occurs, it returns an abnormally large remaining time.

After this issue has occurred, can you fix it by power cycling or reflashing the firmware?
Also, have you been able to reproduce this issue on a DK (nrf54l15dk/nrf54l05)?

Regards,
Benjamin