From: Bastos Fernandez Alexandre <alebas@televes•com>
To: Mark Chambers <markc@mail•com>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs•org>
Subject: Re: Watchdog on MPC82xx
Date: Wed, 19 Apr 2006 16:59:51 +0200 [thread overview]
Message-ID: <1145458791.44465067c4afa@webmail.televes.com:443> (raw)
In-Reply-To: <005401c663a9$e1fd8930$6401a8c0@CHUCK2>
Mark,
>
> I haven't been following this closely, but are you sure it's a WDT
> reset? You can tell from the Reset Status Register (RSR).
> u-boot prints out a decode of this register, which also clears the
> bits, so you have to go by the printout when u-boot starts to see
> why the last reset occurred.
U-boot is reporting the Watchdog reset. You can see:
U-Boot 1.1.4 (Apr 11 2006 - 14:39:01)
MPC8272 Reset Status: Software Watchdog, External Soft, External Hard
MPC8272 Clock Configuration
- Bus-to-Core Mult 4x, VCO Div 2, 60x Bus Freq 25-75 , Core Freq 100-300
- dfbrg 1, corecnf 0x1a, busdf 3, cpmdf 1, plldf 0, pllmf 3
- vco_out 400000000, scc_clk 100000000, brg_clk 25000000
- cpu_clk 400000000, cpm_clk 200000000, bus_clk 100000000
- pci_clk 66666666
CPU: MPC8272 (HiP7 Rev 14, Mask 1.0 1K50M) at 400 MHz
Board: Televes XXX8248
Watchdog enabled
>
> Just trying to help brainstorm...
>
> Mark Chambers
>
Thanks,
Alex Bastos
next prev parent reply other threads:[~2006-04-19 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 9:48 Watchdog on MPC82xx 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 8:31 Bastos Fernandez Alexandre
2006-04-19 14:29 Rune Torgersen
2006-04-20 10:26 ` Bastos Fernandez Alexandre
2006-04-19 15:23 Pelton, Dave
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='1145458791.44465067c4afa@webmail.televes.com:443' \
--to=alebas@televes$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=markc@mail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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