public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 15:55:21 +0200	[thread overview]
Message-ID: <f870da1805082506554eda3f76@mail.gmail.com> (raw)
In-Reply-To: <430DBEC0.1080809@smiths-aerospace.com>

On 8/25/05, Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com> wrote:
>
> 
> Pointing out the obvious... looking at the disassembly, it isn't
> enabling the watchdog (SWE).  I'm guessing that you disassembled code
> where you had the watchdog disabled?

The instruction
fff031a0:       60 84 ff c3     ori     r4,r4,65479 
actually enables watchdog (65479 dec = ffc7 hex) and SWE is bit 29 of SYPCR.
 
> I see you have PBME and LBME enabled (I'm looking at an 8260 manual,
> assuming the 8247 is the same - feel free to correct me :-).  Do you
> have a 60x bus and a local bus?  Is it possible you are having an
> inadvertant bus error?  This wouldn't explain why it only happens when
> you enable the WDT, however.  Puzzling.

The 8247 does not have local bus, only 60x, but setting/clearing LBME
does not affect the operation. If I don't enable the watchdog the
system works fine.

Another thing I've noticed, most or even all 8260 based systems have
#undef CONFIG_WATCHDOG
in their config 

-- 
	Sincerely Yours,
		Mike.

  reply	other threads:[~2005-08-25 13:55 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
2005-08-25 12:51     ` Jerry Van Baren
2005-08-25 13:55       ` Mike Rapoport [this message]
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=f870da1805082506554eda3f76@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox