From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ppc44x - watchdog timers reboots during the image loading
Date: Fri, 1 Oct 2010 16:45:42 +0200 [thread overview]
Message-ID: <201010011645.43264.sr@denx.de> (raw)
In-Reply-To: <20101001143755.GA28063@crust.elkhashab.com>
On Friday 01 October 2010 16:37:55 ame wrote:
> > void reset_4xx_watchdog(void)
> > {
> >
> > /*
> >
> > * Clear TSR(WIS) bit
> > */
> >
> > mtspr(SPRN_TSR, 0x40000000);
> >
> > }
> > ...
> >
> > Definitely upper-case here.
>
> Ok, confirmed the new one has it in there. sorry about that. The logic
> is the same as the one that is in the old code though.
Sure.
> > > Any thoughts or help are appreciated. I did notice the comments in
> > > cpu-init.c that my tcr is setup with 0xF0000000, I *think* this is
> > > actually 10s on a 800MHz board. Not sure where the 2.684 numbers
> > > originates as stated in the comments. I also changed the acknowledge of
> > > the watchdog to the following, though neither my changes nor the
> > > original have any effect. I've also verified that the code is getting
> > > included and built. Not sure what to try next.
> >
> > Note that you need to enable the watchdog support in the Linux kernel as
> > well. Otherwise Linux will of course reset once the watchdog timer times
> > out. Did you enable the book-e watchdog timer in Linux?
>
> Yes, that is enabled. But from the looks of the boot trace up above, am I
> correct in saying that it never even made it to Linux? Isn't u-boot still
> in control at the point that it loads the ramdisk into ram?
Sure, while loading/copying the ramdisk control is still under U-Boot. But
from your first email I read:
> The last message
> I see is ...
>
> Verifying Checksum ... OK
>
> ## Flattened Device Tree blob at ff3e0000
>
> Booting using the fdt blob at 0xff3e0000
> Uncompressing Kernel Image ... OK
> Loading Device Tree to 007fa000, end 007ffd2f ... OK
> Loading Ramdisk to 1ec58000, end 1efffc0c ... OK
So the ramdisk is already copied. Or do I miss something here? Please check
the code (add some printf's etc) to see if you are still in U-Boot or not.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2010-10-01 14:45 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
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 [this message]
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=201010011645.43264.sr@denx.de \
--to=sr@denx.de \
--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