From: Wolfgang Denk <wd@denx.de>
To: "Mark Chambers" <markc@mail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: JTAG debuggers for Motorola 8xx/82xx/85xx
Date: Fri, 18 Jun 2004 17:04:55 +0200 [thread overview]
Message-ID: <20040618150500.73631C13D3@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 18 Jun 2004 09:09:49 EDT." <001501c45535$8aecd120$0301a8c0@chuck2>
In message <001501c45535$8aecd120$0301a8c0@chuck2> you wrote:
> Thanks for this information Wolfgang. We've been trying to decide between
> 5200 and an 8xxx for a project and have gotten the distinct feeling that
> 5200 is somehow not from the same part of the company as 8xxx, and not
> supported in the same way. Do you know, do the 82xx or 85xx processors have
> similar restrictions?
The same restrictions are in place for all processors with a JTAG/COP
port, i. e. all what's ther eis in the 52xx, 82xx, 85xx, 7xx, 74xx,
... families. Just the 5xx/8xx which use BDM are an exception.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
No user-servicable parts inside. Refer to qualified service personnel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-18 15:04 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
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 [this message]
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=20040618150500.73631C13D3@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=markc@mail.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).