From: Kumar Gala <kumar.gala@freescale.com>
To: Matevz Langus <matevz.langus@fortunal.net>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: JTAG debuggers for Motorola 8xx/82xx/85xx
Date: Wed, 9 Jun 2004 16:17:07 -0500 [thread overview]
Message-ID: <5CB4164A-BA5A-11D8-92CC-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1086815570.3985.13.camel@n1020>
I'm guessing most people would recommend the BDI2000. If I remember
correctly they end up doing support based on 'Family'. So support for
85xx is one family, 82xx is another, 8xx a third.
- kumar
On Jun 9, 2004, at 4:12 PM, Matevz Langus wrote:
>
> Hi folks,
>
> I see you are discussing about BDI2000 here. Our company used EST Tools
> for many years and they were really good but since Windriver bought EST
> they suck.
>
> Which JTAG debugger do you suggest for Mot 8xx/82xx/85xx processors?
> If possible without stupid licensing model, where every time Motorola
> changes partnumber for the same chip new license and a couple k$ are
> needed.
>
> I hope to get honest answers as all producers promise amazing things
> which aren't really to believe.
>
> thanks,
> Matevz
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-09 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040609154634.29212C109F@atlas.denx.de>
2004-06-09 21:12 ` JTAG debuggers for Motorola 8xx/82xx/85xx Matevz Langus
2004-06-09 21:17 ` Kumar Gala [this message]
2004-06-10 0:08 ` Tom Curran
2004-06-09 21:35 ` Mark Chambers
2004-06-09 22:38 ` Wolfgang Denk
2004-06-18 5:21 ` Andrew Dennison
2004-06-18 9:39 ` Wolfgang Denk
2004-06-18 13:09 ` Mark Chambers
2004-06-18 15:04 ` Wolfgang Denk
2004-06-18 13:02 ` Mark Chambers
2004-06-21 0:21 ` Andrew Dennison
2004-06-10 3:25 ` Fahd Abidi
2004-06-09 21:22 VanBaren, Gerald (AGRE)
[not found] <81C69D96BDD30640952C7A404004AA25092CE9@h0007e95d9fa7.ne.client2.attbi.com>
2004-06-18 14:19 ` Fahd Abidi
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=5CB4164A-BA5A-11D8-92CC-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=matevz.langus@fortunal.net \
/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.