[riot-devel] WDT questions
joakim.gebart at eistec.se
Wed Apr 29 17:08:14 CEST 2015
Create a multi-channel software watchdog that in turn pokes the hardware
watchdog when all parameters are met.
We could configure different timeouts for different channels and each
critical process can have its own channel(s) which they update
Some risks of this approach is that it will be possible for software errors
to make the software watchdog misbehave and poke the hardware watchdog and
keep the system running when it should be reset.
Thanks for your explanations. I understand why it is counter productive.
But how RIOT will make sure that the board is not stuck in a deadlock? This
is mandatory for industrial context.
2015-04-29 15:07 GMT+02:00 Joakim Gebart <joakim.gebart at eistec.se>:
> It has to do with the difficulty of providing a reliable way of poking the
> watchdog in an event driven, tickless, system such as RIOT. Maybe it is
> time to start discussing a watchdog api?
> In order to get any traction within industry applications I believe it
> will be necessary to at least provide an api for applications to use the
> Best regards,
> Joakim Gebart
> Eistec AB
> On Apr 29, 2015 2:43 PM, "Baptiste Clenet" <bapclenet at gmail.com> wrote:
>> I've got two questions concerning WDT:
>> - Why do we disable it on the samr21 at launch time?
>> - Why doesn't RIOT provide a wdt.h in drivers/include/periph?
>> *Clenet Baptiste*
>> devel mailing list
>> devel at riot-os.org
> devel mailing list
> devel at riot-os.org
devel mailing list
devel at riot-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel