This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

WDT & Bootloader

My application uses the WDT. In my application, I use a soft reset to enter the bootloader. Because the soft reset does not reset the WDT the program will reset while in the bootloader because of a watchdog timeout.

What is the best way to handle this issue? I see too options. Instead of performing a soft reset to enter the bootloader I could let the WDT in my application expire in order to perform a reset using a WATCHDOG reset. Alternatively I could add the watchdog service into the bootloader. I don't like that the watchdog is running during the initialization routines at the beginning of my application.Why does the softreset not reset the watchdog? Seems a bit odd.

Parents
  • Nordic, please can you fix your completely inflexible WDT config.

    The inability to reconfigure the WDT once started is fine in principle but anyone who has ever done any work in the embedded world will tell you how inflexible such a solution is.

    Furthermore the argument that the ability to reconfigure the watchdog once started would negate the protection of a watchdog is also nonsense. I could quite easily write a bit of code which trashed either the ARM or NRF51 register space that the WDT could not offer recovery from.

Reply
  • Nordic, please can you fix your completely inflexible WDT config.

    The inability to reconfigure the WDT once started is fine in principle but anyone who has ever done any work in the embedded world will tell you how inflexible such a solution is.

    Furthermore the argument that the ability to reconfigure the watchdog once started would negate the protection of a watchdog is also nonsense. I could quite easily write a bit of code which trashed either the ARM or NRF51 register space that the WDT could not offer recovery from.

Children
Related