This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Watchdog
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Bob Koninckx <bob dot koninckx at mech dot kuleuven dot ac dot be>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Fri, 23 May 2003 02:55:40 +0100
- Subject: Re: [ECOS] Watchdog
- References: <1053292421.3520.4.camel@pc-002>
[ I'll reply to this too jsut in case]
Bob Koninckx wrote:
Hi list,
I want to use the hardware watchdog on my mpc555 board which does not
seem too difficult to implement.
It is however from the documentation not clear to me how to use it. Do I
need to instantiate, initialize and reset it from application code, or
is this taken care of by the kernel ?
Watchdog support only exists for those targets with a watchdog driver as
per the devs/watchdog directory. The target definition in ecos.db will
then list that package. It's then up to the application to start up the
watchdog driver. Have a look at some of the existing device drivers.
Note it just occurred to me with your other mention of watchdogs in
RedBoot that this means you would probably need to selectively enable an
interrupt to prod the watchdog - the RedBoot idle loop handler stuff could
delay too long. This isn't normal for RedBoot (ints are normally all
disabled), but is possible if you mask off all other interrupts. Bit of a
pain though.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss