From: "Ami Levi Waves" <ami@waves.com>
To: "'Steve Iribarne \(GMail\)'" <netstv@gmail.com>,
"'linuxppc-embedded'" <linuxppc-embedded@ozlabs.org>
Subject: RE: 8541E and vector table.
Date: Tue, 20 Feb 2007 15:39:42 +0100 [thread overview]
Message-ID: <002d01c754fd$1f030860$0600000a@waves.com> (raw)
In-Reply-To: <b4b98b690702200620q3c70cba9j2d8046d4451686a1@mail.gmail.com>
Download the MPC8541 reference manual from Freescale web site.
Look in the chapter that says Exceptions (could be chapter 6)
You'll fine the different vectors addresses + explanations about each
vector.
Ami
> -----Original Message-----
> From: linuxppc-embedded-bounces+ami=3Dwaves.com@ozlabs.org =
[mailto:linuxppc-
> embedded-bounces+ami=3Dwaves.com@ozlabs.org] On Behalf Of Steve =
Iribarne
> (GMail)
> Sent: Tuesday, February 20, 2007 3:21 PM
> To: linuxppc-embedded
> Subject: 8541E and vector table.
>=20
> Hi.
>=20
> I must admit, this stuff always baffles me a bit, so I need someone
> who knows this to explain it to me.
>=20
> I am using an 8541E and my system randomly crashes. By randomly, I
> mean at different times. I have a BDI hooked up and it always jumps
> to offset 0x0000_0700
>=20
> I believe this to be a vector table offset, but I need to figure out
> which interrupt it is. I believe this is a hardware issued, because
> if I look at that value, it looks to be default values. In other
> words, I don't believe I have it setup.
>=20
> So the question I have is how do I figure out what that interrupt =
vector
> is?
>=20
> Thanks so much.
>=20
> -stv
>=20
> --
> /*
> * Steve Iribarne
> * Software Engineer
> * (aka Grunt)
> */
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2007-02-20 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 14:20 8541E and vector table Steve Iribarne (GMail)
2007-02-20 14:39 ` Ami Levi Waves [this message]
2007-02-20 15:29 ` Steve Iribarne (GMail)
2007-02-20 15:55 ` Kumar Gala
2007-02-20 16:06 ` Steve Iribarne (GMail)
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='002d01c754fd$1f030860$0600000a@waves.com' \
--to=ami@waves.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=netstv@gmail.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 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.