Fri Dec 17 16:04:00 GMT 2004
It also depends upon the kind of use you want for your
Let's say, if you wish the watchdog to reset on
possible software locks, like deadlocks or starvation
scenarios, you should put your watchdog "kick" after
the calls that may cause the hang.
If you put a watchdog kick in a high priority
interruption, your software can stop working or lock,
but the interruption may keeps the dog happy, even
your main thread being locked.
I usually kick the watchdog in the last state of the
state machine, after all possible harmfull calls had
been called. But, this can cause problems in
assynchronous calls ...
--- Wayne Gemmell <email@example.com> escreveu:
> On Friday 17 December 2004 15:05, Gary Thomas wrote:
> > Wayne Gemmell said:
> > > Hi all
> > >
> > > The way I understand it the watchdog needs to be
> reset every >2.5 seconds
> > > or the hardware gets reset.
> > This is hardware/platform dependent, but in
> general, this is how watchdogs
> > work.
> > > Would the best way to implement this be to
> spread resets all over the
> > > program or to run a high priority thread that
> runs reset at the
> > > designated interval?
> > A high priority thread would do, or possibly a
> separate high priority timer
> > and service the watchdog in the ISR.
> > It's probably better to isolate the watchdog
> service to one location rather
> > than messing about all over the place.
> Thanks :-)
> Before posting, please read the FAQ:
> and search the list archive:
Daniel C. Gomes <firstname.lastname@example.org>
ICQ : 2278714
Belo Horizonte - MG - Brasil
Yahoo! Mail - Agora com 250MB de espaÃ§o gratuito. Abra
uma conta agora! http://br.info.mail.yahoo.com/
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss