From: Dan Malek <dan@netx4.com>
To: Jeff Millar <jeff@wa1hco.mv.com>
Cc: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>,
Pavel Roskin <pavel_roskin@geocities.com>,
"Wohlgemuth, Jason" <jason_wohlgemuth@gilbarco.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Software Emulation Exception...
Date: Mon, 10 Apr 2000 22:03:23 -0400 [thread overview]
Message-ID: <38F287EB.BE201D4@embeddededge.com> (raw)
In-Reply-To: 001001bfa35e$cb0021a0$0201a8c0@home
Jeff Millar wrote:
> .... So, is it a
> problem with the RPX board or the Sandisk?
Like I said before. I can't guess, and neither should you. The fact
is the software emulation trap is caused by fetching an instruction
that can't be properly decoded. We need to determine what it fetched
and where that came from. These are some fundamental engineering
skills we are trying to use here. Why aren't we using them?
The PCMCIA interfaces have their timing requirements. On the 8xx,
these are all very programmable. Look at the card specifications and
the values programmed. Do they seem reasonable? Don't simply run
maximum, excessively long timing on the PCMCIA. This can be just as
bad on some cards or other external devices as running too fast.
Attach a logic analyzer. Does the timing on the 8xx bus look reasonable?
Use one of the GPIO pins to trigger the analyzer when you trap the fault
(as early as possible). Look at the bus signals. What really happened?
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-11 2:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 13:54 Software Emulation Exception Wohlgemuth, Jason
2000-04-07 15:20 ` Pavel Roskin
2000-04-07 15:44 ` Dan Malek
2000-04-10 9:37 ` Marcus Sundberg
2000-04-10 16:26 ` Dan Malek
2000-04-11 2:36 ` Jeff Millar
2000-04-11 2:03 ` Dan Malek [this message]
2000-04-11 8:50 ` Marcus Sundberg
2000-04-11 12:08 ` Dan Malek
2000-04-11 14:51 ` Marcus Sundberg
2000-04-10 3:14 ` Unpacking the mvista kernel RPMs Graham Stoney
2000-04-10 3:25 ` Jason Wohlgemuth
2000-04-10 4:50 ` Graham Stoney
2000-04-10 17:47 ` Pavel Roskin
2000-04-10 16:18 ` Joe Green
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=38F287EB.BE201D4@embeddededge.com \
--to=dan@netx4.com \
--cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=jason_wohlgemuth@gilbarco.com \
--cc=jeff@wa1hco.mv.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pavel_roskin@geocities.com \
/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).