ASSERTION FAIL [m_cb[p_instance->drv_inst_idx].state == NRFX_DRV_STATE_POWERED_0

[moose]

Hello, I attempted to enable the zephyr task watchdog model but whenever I configure it to enable the hardware watchdog module I get the error above. Any idea why I am getting this? My code is very similar to the sample project and I have the following config statements:

CONFIG_WATCHDOG=y
CONFIG_WDT_LOG_LEVEL_DBG=y
CONFIG_WDT_DISABLE_AT_BOOT=n
CONFIG_TASK_WDT=y
CONFIG_TASK_WDT_MIN_TIMEOUT=100

Thanks!

[moose]

Simon, as mentioned I am using the zephyr task wdt module which internally configures the hardware wdt. I call the task_wdt_init function first, then task_wdt_add, and finally task_wdt_feed on a periodic event. Here is the link for the module code link. In the code, you can see that wdt_setup function is called within task_wdt_add.

Please note that within task_wdt_add,  task_wdt_feed is called before wdt_setup which in turn call wdt_feed function. Not sure if this problematic. 

Any ideas on how to proceed? Has the task_wdt module ever worked on a nordic SoC? Thx!

[Simon]

I tested the sample zephyr\samples\subsys\task_wdt with an nRF52833dk_nrf52833 and it seemed to run fine.

I got the same log output as mentioned in https://github.com/nrfconnect/sdk-zephyr/tree/a409bc732b62ce659462114ccf2870ada1724e1c/samples/subsys/task_wdt#sample-output 

However, setting CONFIG_ASSERT=Y triggered the same assert you got. It seems like this subsystem is quite new and recently added to Zephyr (15th of March), so that's why it might be some undiscovered bugs. Would you be able to create a Zephyr issue https://github.com/zephyrproject-rtos/zephyr/issues/new/choose? If you don't get an answer, please get back to me here and I will look into it. If you resolve it, it would be nice if you could share the solution.

Best regards,

Simon