From: Mike Rapoport <mike.rapoport@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Software watchdog on mpc8247
Date: Thu, 25 Aug 2005 14:35:31 +0200 [thread overview]
Message-ID: <f870da1805082505352147f50@mail.gmail.com> (raw)
In-Reply-To: <430DAE38.2090903@smiths-aerospace.com>
On 8/25/05, Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com> wrote:
>
> What did you set the SYPCR to (actual values, preferably from a
> disassembly/dump)?
Here's the output of "objdump -dS u-boot" :
/* Initialise the SYPCR early, and reset the watchdog (if req) */
/*--------------------------------------------------------------*/
lis r3, (CFG_IMMR+IM_REGBASE)@h
fff03198: 3c 60 f0 01 lis r3,-4095
#if !defined(CONFIG_COGENT)
lis r4, CFG_SYPCR at h
fff0319c: 3c 80 ff ff lis r4,-1
ori r4, r4, CFG_SYPCR at l
fff031a0: 60 84 ff c3 ori r4,r4,65479
stw r4, IM_SYPCR at l(r3)
fff031a4: 90 83 00 04 stw r4,4(r3)
#endif /* !CONFIG_COGENT */
#if defined(CONFIG_WATCHDOG)
li r4, 21868 /* = 0x556c */
sth r4, IM_SWSR at l(r3)
li r4, -21959 /* = 0xaa39 */
sth r4, IM_SWSR at l(r3)
Actual SYPCR setting is 0xFFFFFFC7
I verified that this code is executed.
I've tried to add WATCHDOG_RESET() call in board_init_f just before
the initialization sequence was run, but it didn't change anything.
> What is your bus clock?
66MHz
> What do you figure your timeout to be?
2 sec
> Do you write to the SYPCR only once to set up the WDT
> (only the first write to the SYPCR "works").
Yes
--
Sincerely Yours,
Mike.
next prev parent reply other threads:[~2005-08-25 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 5:46 [U-Boot-Users] Software watchdog on mpc8247 Mike Rapoport
2005-08-25 7:04 ` Wolfgang Denk
2005-08-25 10:42 ` Mike Rapoport
2005-08-25 11:40 ` Jerry Van Baren
2005-08-25 12:35 ` Mike Rapoport [this message]
2005-08-25 12:51 ` Jerry Van Baren
2005-08-25 13:55 ` Mike Rapoport
2005-08-25 14:40 ` Jerry Van Baren
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=f870da1805082505352147f50@mail.gmail.com \
--to=mike.rapoport@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.