All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "Matevz Langus" <matevz.langus@fortunal.net>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: JTAG debuggers for Motorola 8xx/82xx/85xx
Date: Wed, 9 Jun 2004 17:35:47 -0400	[thread overview]
Message-ID: <007a01c44e69$bb7de860$0301a8c0@chuck2> (raw)
In-Reply-To: 1086815570.3985.13.camel@n1020


For 8xx, the open source BDM4GDB (which you can get from www.denx.de) is
great.  I also partially ported the bdm driver to Windows for production
testing work.  Under Windows, I've used CrossView (from Tasking.com) with
Macraigor Wiggler (ocdemon.net) - all priced very reasonably.  However
CrossView does not support linux (but BDM4GDB does, of course)

Mark Chambers

>
> 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.
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-06-09 21:35 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
2004-06-10  0:08     ` Tom Curran
2004-06-09 21:35   ` Mark Chambers [this message]
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='007a01c44e69$bb7de860$0301a8c0@chuck2' \
    --to=markc@mail.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.