linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "robert lazarski" <robertlazarski@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 85xx software reset problems from paulus.git
Date: Fri, 16 Nov 2007 15:44:20 -0500	[thread overview]
Message-ID: <f87675ee0711161244h46c23d8byadaf1abb923b3971@mail.gmail.com> (raw)
In-Reply-To: <473DB6DF.9010804@anagramm.de>

On Nov 16, 2007 10:27 AM, Clemens Koller <clemens.koller@anagramm.de> wrote:
> Hello, Robert!
>
> robert lazarski schrieb:
>  > Hi all, on my custom 85xx board I can't do a soft reset. I'm using
>  > u-boot 1.3rc3 that has the latest cpu/mpc85xx/cpu.c patch to fix some
>  > type of reset problem. When I press the software reset button on my
>  > board after my nfs kernel panic, I get this:
>
> Please define "software reset button" in your case. :-)
> I consider a "button" clearly as hardware.
>

I mean a hardware button that calls SRESET , ie, Soft reset machine check.

<snip>
>
> The SRESET# (pin AF20) is the soft reset input, causes
> an mcp assertion to the core.... (RTFM)
>

That's what we are doing. The 85xx docs say "Soft reset. Causes a
machine check interrupt to the e500 core. Note that if the e500 core
is not configured to process machine check interrupts, the assertion
of SRESET causes a core checkstop. SRESET need not be asserted during
a hard reset."

Is the 85xx kernel "not configured to process machine check
interrupts" ? Do I need to do that myself in my boards restart
function via the special registers? Is there code already for this?

Robert

  reply	other threads:[~2007-11-16 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 15:00 85xx software reset problems from paulus.git robert lazarski
2007-11-16 15:27 ` Clemens Koller
2007-11-16 20:44   ` robert lazarski [this message]
2007-11-16 21:28     ` robert lazarski
2007-11-16 21:46       ` Kumar Gala
2007-11-16 22:01         ` robert lazarski
2007-11-17 19:52           ` Kumar Gala
2007-11-26 17:41             ` robert lazarski
2007-11-26 20:20               ` Clemens Koller
2007-11-27  7:38                 ` Kumar Gala
2007-11-27 13:50                   ` Dale Farnsworth
2007-11-27 14:54                     ` Dale Farnsworth
2007-11-27 16:26                       ` Kumar Gala
2007-11-27 23:09                         ` Dale Farnsworth

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=f87675ee0711161244h46c23d8byadaf1abb923b3971@mail.gmail.com \
    --to=robertlazarski@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).