From: Daniel Ann <ktdann@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Watchdog timer reset
Date: Thu, 12 May 2005 21:05:32 +0900 [thread overview]
Message-ID: <9b7ca657050512050554c9e1dd@mail.gmail.com> (raw)
In-Reply-To: <20050511222348.19029C1512@atlas.denx.de>
On 5/12/05, Wolfgang Denk <wd@denx.de> wrote:
> > Just wondering, does u-boot support periodical reset of watchdog timer
>
> Yes, of course it does.
I'd really appreciate it if you could point me to a file or a function
to take a look.
> If your watchdog i worth it's money it comes up enabled after reset,
> and you can just disable it once and forever. A watchdog that can be
> switched of is not worth to be called by that name.
Actually this is really software driven timer we developed on an 8bit
micom. So, disable/enable isnt much of bother, but like you said about
watchdog, I'm trying to avoid disabling watchdog altogether.
> > How does people normally do this ?
>
> Have a look at the code.
:P sorry for trying an easy way out, but if you happen to know good
place to start, dont hesitate (please) :)
> No, we cannot. U-boot is strictly single-tasking and has no notion of
> signals and the like. Also, your code makes no sense to me.
Okay, its basically using alarm() to produce SIGALRM every 10 seconds.
(assuming alarm() takes second as an argument) And using signal() we
are calling runme() function everytime it is woken up by SIGALRM.
Natually, runme() will do whatever it needs to do, and sets another
alarm before it ends. Not shown in the code, is probably a block read
so it keeps the program running.
Hopefully this makes more sense than a code :P
--
Daniel
next prev parent reply other threads:[~2005-05-12 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 11:05 [U-Boot-Users] Watchdog timer reset Daniel Ann
2005-05-11 22:23 ` Wolfgang Denk
2005-05-12 12:05 ` Daniel Ann [this message]
2005-05-12 13:35 ` Wolfgang Denk
2005-05-13 1:46 ` Daniel Ann
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=9b7ca657050512050554c9e1dd@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=u-boot@lists.denx.de \
/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