[riot-notifications] [RIOT-OS/RIOT] drivers/include: add header definition for wdt (#11527)
notifications at github.com
Tue May 21 11:31:47 CEST 2019
> We should make sure that applications time the warning callback so that the warning is issued at the watchdog timeout, and the reboot is `WDT_WARNING_PERIOD` after. Or the other way around. Just consistent. :)
The first option sounds like it's trying to be too clever for it's own good ;)
Having the callback `WDT_WARNING_PERIOD` *before* the timeout sounds about right.
And if `WDT_WARNING_PERIOD` = `max_time` - `min_time` than that's fine.
> When a callback is set, what happens if a minimum is set and then the wdt is kicked too early?
As I understand it, the warning interrupt is useful if you run a completely event-based system.
There is no periodic loop to 'kick' the watchdog, but instead you have a periodic watchdog interrupt that does the kicking or schedules the dirty work within your event system.
If you kick the dog too early than that's an error and the system should be reset.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications