From: "Mark Chambers" <markc@mail.com>
To: "Dan Malek" <dan@embeddededge.com>, "annamaya" <annamaya@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Is there a DER for the MPC82xx?
Date: Wed, 26 Jan 2005 15:33:52 -0500 [thread overview]
Message-ID: <00c001c503e6$64369fb0$0301a8c0@chuck2> (raw)
In-Reply-To: BD936D78-6FCC-11D9-A0FB-003065F9B7DC@embeddededge.com
From: "Dan Malek" <dan@embeddededge.com>
>
> On Jan 26, 2005, at 10:53 AM, annamaya wrote:
>
> > Can someone tell me if the BDI will be able to catch
> > all different kinds of exceptions/interrupts on the
> > MPC82xx without requiring any special register
> > programming? I am unable to find anything that that
> > resembles the DER register on the MPC8280.
>
> The BDI2000 works very nicely on 82xx processors.
> The 82xx debug unit is the standard COP interface,
> completely different from the 8xx debug interface.
> Stop looking for a DER on the 82xx, plug in the
> BDI2000 and use it. Make sure you understand all
> of the features of the BDI2000, as even on the 8xx
> you should not be worrying about the DER. Let the
> BDI2000 configure all of that accordingly based upon
> what you are asking it to do.
>
>
Well, the DER lets you look for multiple conditions at
once. Your program is blowing up, the memory is
getting trashed and you don't even know if the hardware
is valid - that's where BDM really shines. I don't see
where COP let's you do the equivalent of setting a
bunch of bits in the DER, so please enlighten us if
we're missing it!
Mark Chambers
P.S. I've read the BDI manual - I don't see it. My manual
says the BDI can only set one hardware breakpoint, and
stuff like VECTOR CATCH assumes valid memory.
next prev parent reply other threads:[~2005-01-26 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 22:54 Is there a DER for the MPC82xx? annamaya
2005-01-26 18:53 ` annamaya
2005-01-26 19:01 ` Dan Malek
2005-01-26 19:15 ` annamaya
2005-01-26 20:33 ` Mark Chambers [this message]
2005-01-26 21:19 ` Dan Malek
2005-01-26 21:37 ` Mark Chambers
2005-01-26 22:22 ` annamaya
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='00c001c503e6$64369fb0$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=annamaya@yahoo.com \
--cc=dan@embeddededge.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).