From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ppc44x - watchdog timers reboots during the image loading
Date: Mon, 4 Oct 2010 10:49:09 +0200 [thread overview]
Message-ID: <201010041049.10151.sr@denx.de> (raw)
In-Reply-To: <20101001153639.GA28486@crust.elkhashab.com>
Hi ame,
On Friday 01 October 2010 17:36:39 ame wrote:
> > 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.
>
> Well, ok, kind of. cpu.c is correct, cpu_init.c that actually sets up the
> watchdog timer is not though. It still has the lower case register names.
>
> #if defined(CONFIG_WATCHDOG)
> val = mfspr(tcr);
> ...
> mtspr(tcr, val);
>
> val = mfspr(tsr);
> val |= 0x80000000; /* enable watchdog timer */
> mtspr(tsr, val);
> ...
> #endif /* CONFIG_WATCHDOG */
Ah, correct. I missed those. I'll fix it soon. Thanks for pointing out.
> I've added some prints and turned on debug and find that it makes it all
> the way to the jump to the kernel. So it must be an issue with the setup
> or config of the kernel. Does the device tree require any changes to work
> with the watchdog? Thanks for your help.
Depends on the watchdog device driver. The Book-E driver doesn't seem to need
anything here, AFAIK. I suggest you enable the debug early-printk feature
and/or look the __log_buf to see how far Linux really comes. This is not U-
Boot realted any more though. So further questions/mails should be moved to
linuxppc-dev.
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
prev parent reply other threads:[~2010-10-04 8:49 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
2010-10-01 15:36 ` ame
2010-10-04 8:49 ` Stefan Roese [this message]
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=201010041049.10151.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