From: ame <ayman@austin.rr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ppc44x - watchdog timers reboots during the image loading
Date: Thu, 30 Sep 2010 16:02:43 -0500 [thread overview]
Message-ID: <20100930210243.GA12007@crust.elkhashab.com> (raw)
In-Reply-To: <AANLkTi=khU_AvRb5qGhfP0iojPSFZcp1Rtt3m6AWMKJ=@mail.gmail.com>
On Thu, Sep 30, 2010 at 03:48:36PM -0500, Timur Tabi wrote:
> On Thu, Sep 30, 2010 at 3:15 PM, ame <ayman@phx1-ss-2-lb.cnet.com> wrote:
> > On my 460ex board, i've tried to add CONFIG_WATCHDOG to the config and it appears to
> > work until the board tries to boot. ?At that point I can count down about 10 seconds
> > and the reboot happens. ?The 10s correlates with what I think the watchdog is being
> > set to. ?I've inserted some WATCHDOG_RESET() invocations wrapping memmove_wd (which
> > admittedly should not be needed), but it does not have an effect.
>
> Looks to me like your implementation of WATCHDOG_RESET() is broken.
> It's not actually resetting the watchdog. That's what you should
> debug.
>
I suspect that that is the case, but trawling through the u-boot code it appears that
WATCHDOG_RESET is a macro that eventually does one of two things:
a) if asm, bl watchdog_reset
b) if c, watchdog_reset()
watchdog_reset in turn saves the interrupt state, disables interrupts, invokes
reset_4xx_watchdog, then restores the interrupt state.
Finally reset_4xx_watchdog does mtspr(tsr, 0xc0000000) where tsr is 0x150 IIRC.
All of this is in the u-boot source, mostly in cpu.c and watchdog.h (i.e. none of this is
custom for my board, it is part of the ppc44x code).
I've dumped the binary to make sure the methods are actually in the code, manipulating
the spr, and getting called.
ame
next prev parent reply other threads:[~2010-09-30 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 20:15 [U-Boot] ppc44x - watchdog timers reboots during the image loading ame
2010-09-30 20:48 ` Timur Tabi
2010-09-30 21:02 ` ame [this message]
2010-09-30 21:04 ` Timur Tabi
2010-10-01 13:35 ` Stefan Roese
2010-10-01 14:37 ` ame
2010-10-01 14:45 ` Stefan Roese
2010-10-01 15:36 ` ame
2010-10-04 8:49 ` Stefan Roese
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=20100930210243.GA12007@crust.elkhashab.com \
--to=ayman@austin.rr.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