linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: <robin.gilks@tait.co.nz>
Cc: ppc embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Exception handling on mpc8xx cores
Date: Wed, 8 Dec 2004 08:06:56 -0500	[thread overview]
Message-ID: <003801c4dd26$d0e30090$0301a8c0@chuck2> (raw)
In-Reply-To: 1102498710.414.98.camel@linpc003.aimsys.nl



> On Wed, 2004-12-08 at 05:15, Robin Gilks wrote:
> > Greetings
> > 
> > Any Freescale lurkers out there?
> > 
> > The mpc866 manual implies that if the internal core times out an 
> > external Transfer Acknowledge bus signal (by exerting the internally 
> > generated Transfer Error Acknowledge signal) an exception is generated.
> > 
> > I've tried extending the external TA signal well beyond 2040 clock 
> > cycles the maximum timeout allows and I see the busses start up again 
> > (indicationg that they are no longer waiting) but I don't see anything 
> > on TEA and I don't get an exception thrown.
> > 
> > Any clues? Manual error?, silicon error?, my brain error?
> 
> Did you enable the bus monitor in the SYPCR register?
> 

You've also got to have ME set in MSR to get the exception.  For whatever 
it's worth, I have an mpc852 design (part of 866 family) that uses external
acknowledge and it works as advertised.  I've seen the acknowledger,
a DSP, fail, and we get a machine check exception.  (I've never 
looked at TEA, though).

Mark Chambers

  reply	other threads:[~2004-12-08 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  4:15 Exception handling on mpc8xx cores Robin Gilks
2004-12-08  9:38 ` Jaap-Jan Boor
2004-12-08 13:06   ` Mark Chambers [this message]
2004-12-08 20:32     ` Robin Gilks

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='003801c4dd26$d0e30090$0301a8c0@chuck2' \
    --to=markc@mail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=robin.gilks@tait.co.nz \
    /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).