SDK15.0 DFU and WatchDog issue

RE: SDK15.0 DFU and WatchDog issue

Bruno Randolf — Mon, 22 Apr 2019 11:52:22 GMT

I have the same issue with a Serial DFU bootloader and SDK 15.3.0. See issue and a workaround in devzone.nordicsemi.com/.../

RE: SDK15.0 DFU and WatchDog issue

Sigurd — Mon, 11 Mar 2019 12:58:36 GMT

You should be able to fix it without migrating. In nrf_bootloader_wdt.c, try changing wdt_feed_timer_handler() so it look like this:

static void wdt_feed_timer_handler(void)
{
        NRF_LOG_INFO("Internal feed");
        wdt_feed();
}

RE: SDK15.0 DFU and WatchDog issue

abe — Fri, 08 Mar 2019 15:59:51 GMT

But this solution needs SDK update and migration!! With new project tests and certifications!!
There are no other way to solve the issue only on DFU mode??

RE: SDK15.0 DFU and WatchDog issue

Sigurd — Fri, 08 Mar 2019 15:40:33 GMT

This feature was actually added in SDK 15.0, from the release notes, "Added watchdog support to the bootloader. If application had enabled watchdog before resetting to the bootloader, it is fed in the bootloader.".

But in SDK 15.2 release notes, we have that "Fixed a bug where the watchdog feeding in the bootloader did not happen during a certain FW activation.", so I would recommend testing with SDK 15.2, and see if you have the same issue there abe.

RE: SDK15.0 DFU and WatchDog issue

abe — Fri, 08 Mar 2019 15:40:28 GMT

I'm not shure to good understand ... to use the Wdog a DFU source code modification is needed?
Some little questions:
- the WDOG has shut down possibility? How?
- where can I put the Wdog shut down (or the Wdog refresh) inside the DFU code?
Please help me!!

RE: SDK15.0 DFU and WatchDog issue

AmbystomaLabs — Fri, 08 Mar 2019 15:22:03 GMT

DFU is a second application. If you enable WDT in your app and switch to DFU, then you have no mechanism for refreshing the WDT. Hence you will get a WDT timeout and reset. So, you either need to shut down the WDT before you switch to DFU or put a WDT refresh routine in the DFU code to keep the WDT timer alive.