linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matevz Langus <matevz.langus@fortunal.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: JTAG debuggers for Motorola 8xx/82xx/85xx
Date: Wed, 09 Jun 2004 23:12:50 +0200	[thread overview]
Message-ID: <1086815570.3985.13.camel@n1020> (raw)
In-Reply-To: <20040609154634.29212C109F@atlas.denx.de>


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/

       reply	other threads:[~2004-06-09 21:12 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 ` Matevz Langus [this message]
2004-06-09 21:17   ` JTAG debuggers for Motorola 8xx/82xx/85xx Kumar Gala
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=1086815570.3985.13.camel@n1020 \
    --to=matevz.langus@fortunal.net \
    --cc=linuxppc-embedded@lists.linuxppc.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).