Bootloader doesn't load application with watchdog

RE: Bootloader doesn't load application with watchdog

Vidar Berg — Tue, 23 Oct 2018 06:21:45 GMT

Yes, in SDK 15:)

RE: Bootloader doesn't load application with watchdog

Fabien Comte — Mon, 22 Oct 2018 19:12:20 GMT

Hello,

Is this supported now ?

RE: Bootloader doesn't load application with watchdog

Vidar Berg — Wed, 21 Feb 2018 08:47:53 GMT

Unfortunately, I don't see any other alternatives. The current bootloader implementation requires modifications to support the WDT. This has been reported as a feature request internally, and may be added in a future release.

RE: Bootloader doesn't load application with watchdog

gkovelman_tap — Tue, 20 Feb 2018 15:59:34 GMT

I thought of this, but the watchdog reset also clears gpregret & gpregret2 so I can't use buttonless DFU

RE: Bootloader doesn't load application with watchdog

Turbo J — Tue, 20 Feb 2018 15:55:28 GMT

The watchdog reset clears the watchdog, too. So you can try starting the bootloader with a watchdog reset. Consider using a shorter timeout than 5 minutes.

RE: Bootloader doesn't load application with watchdog

gkovelman_tap — Tue, 20 Feb 2018 14:23:09 GMT

Using a WDT is common and it's expected from the bootloader to handle such case.
it's very unfortunate that I have to discover this at such late stage.

Is there another workaround? Another way to overcome this without updating the bootloader?

RE: Bootloader doesn't load application with watchdog

Vidar Berg — Tue, 20 Feb 2018 13:12:55 GMT

Hi,

The bootloader implementation attempts to clean up everything before booting the app. The reason for doing this is to ensure that the app boots into the same state as it would if you didn't have a bootloader present. This could be useful if you had an app that didn't use the LF clock source. Although, most applications uses it.

The WDT will automatically request the LF clock as you said, and I'm afraid the only solution apart from not using WDT is to remove clock uninit from the bootloader code.