From: Bastos Fernandez Alexandre <alebas@televes.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: RE: Watchdog on MPC82xx
Date: Thu, 20 Apr 2006 12:26:56 +0200 [thread overview]
Message-ID: <1145528816.444761f0a9962@webmail.televes.com:443> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B85964A@ismail.innsys.innovsys.com>
Rune,
> On our 8265/8280 board, the max timeout of the watchdog timer was ~1.3
> seconds, so it kept resetting before the heartbeat function got called
> on boot.
>
> I had to add a watchdog reset to time_init() because it woud pause there
> for about 2 secondfs trying to see if there was a realtime clock.
>
I think that you are OK. Using the while(1) test suggested by Paul Bilke,
I could verify that time_init() is the cause for the reset. In fact, I have
no RTC on my board (so I suppose the delay looking for it will be maximum).
Thanks
Alex Bastos
next prev parent reply other threads:[~2006-04-20 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 14:29 Watchdog on MPC82xx Rune Torgersen
2006-04-20 10:26 ` Bastos Fernandez Alexandre [this message]
2006-04-21 10:33 ` Watchdog on MPC82xx [SOLVED] Bastos Fernandez Alexandre
-- strict thread matches above, loose matches on Subject: below --
2006-04-19 15:23 Watchdog on MPC82xx Pelton, Dave
2006-04-17 8:31 Bastos Fernandez Alexandre
2006-04-12 9:48 Bastos Fernandez Alexandre
2006-04-12 11:44 ` Bastos Fernandez Alexandre
2006-04-17 7:02 ` Mike Rapoport
2006-04-19 11:13 ` Bastos Fernandez Alexandre
[not found] ` <005401c663a9$e1fd8930$6401a8c0@CHUCK2>
2006-04-19 14:59 ` Bastos Fernandez Alexandre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='1145528816.444761f0a9962@webmail.televes.com:443' \
--to=alebas@televes.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=runet@innovsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).