From: "Andy Gospodarek" <andy@greyhouse.net>
To: "Steven Hein" <ssh@sgi.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: JTAG debugger for MPC82xx/MPC83xx
Date: Tue, 19 Sep 2006 18:30:04 -0400 [thread overview]
Message-ID: <bdfc5d6e0609191530y34d37905jdd97888085214bf0@mail.gmail.com> (raw)
In-Reply-To: <4510664B.2020304@sgi.com>
On 9/19/06, Steven Hein <ssh@sgi.com> wrote:
> Hi,
>
> My group is starting a new project includes a custom board
> with an MPC8258E processor on it. I'm in the process
> of evaluating the state of the Linux kernel, toolchains,
> etc. for the MPC8258E/MPC8360E, as well as selecting a
> JTAG debugger for our project.
>
> I've been researching the available JTAG debuggers that
> support the MPC82xx/MPC83xx family, and I've found these
> choices so far:
>
> * Abatron BDI-2000
> * Green Hills Probe
> * Freescale's PowerTAP PRO for PowerPC
> * Lauterbach TRACE32-ICD
> * WindRiver ICE
> * Embedded Toolsmiths Guardian-SE (BUT...this is no longer
> being sold, according to an email response I received
> from Embedded Toolsmiths)
>
> We will definitely want one with a network connection,
> and will will run the debugger software from a Linux host.
> Ideally, we would also like one that provides a library
> to allow us to write apps to function the debugger.
>
> Can anyone comment on what JTAG debugger they are using,
> and how have your experiences been? Are there any other
> good options besides the ones mentioned above.
> I'd appreciate any input.
>
> Thanks!
> Steve
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Steve Hein (ssh@sgi.com) Engineering Diagnostics/Software
> Silicon Graphics, Inc.
> 1168 Industrial Blvd. Phone: (715) 726-8410
> Chippewa Falls, WI 54729 Fax: (715) 726-6715
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
I've used the BDI on 82xx, 85xx, 83xx, and othersfor custom board
bringup and I liked it. Some may not like the command line interface,
but I found it quite easy to use. I was able to use remote gdb to
debug u-boot, the Linux kernel, and with some trickery userspace apps.
I can't comment specifically on the others (though I have seen some WR
and Lauterbach debuggers and didn't like the user interface), but I
would still recommend the BDI.
next prev parent reply other threads:[~2006-09-19 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 21:51 JTAG debugger for MPC82xx/MPC83xx Steven Hein
2006-09-19 22:30 ` Andy Gospodarek [this message]
2006-09-19 23:26 ` Mark A. Greer
2006-09-20 0:22 ` Greg Weeks
2006-09-20 6:20 ` Kelsey Dawes
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=bdfc5d6e0609191530y34d37905jdd97888085214bf0@mail.gmail.com \
--to=andy@greyhouse.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ssh@sgi.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).