public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] BDIxxxx and others...
Date: Tue, 16 Jun 2009 16:24:08 -0700	[thread overview]
Message-ID: <4A382998.4010300@ovro.caltech.edu> (raw)
In-Reply-To: <Pine.LNX.4.64ksi.0906161532580.9552@home-gw.koi8.net>


> I see you guys talking about BDI3000 and I decided to ask a related
> question.
> 
> Those who happen to own MPC8548CDS or something like this know it comes with
> a small box called CodeWarrior USB TAP.
> 
> It is supposed to work with their software one has to pay for. I never used
> anything but GCC suite for anything GCC supports and always tried to avoid
> commercial tools like a plague. So I want to ask if somebody knows if there
> are any free tools for that thing...
> 
> Not that I really need it for something but it is sitting in the box
> gathering dust and it would be nice ot somehow put it to do something...

I've wondered the same thing. But didn't manage to find
anything out there. I've got three ... in the boxes
the Freescale MDS boards came in.

The USB-TAP has a PowerPC processor in it ... so even if you
had to blow away the original firmware, I'm sure it wouldn't
be too hard to figure out what code would be required to
make the device look like a USB debugger, and then create
a set of USB commands to generate JTAG transactions.

I think the main problem is getting the JTAG TAP codes
for manipulating JTAG. I've never seen a document relating
to that, so they are obviously NDA.

That being said, a weekend with a logic analyzer on a
BDI2000 JTAG connection would probably give you all the
info you need to figure out the appropriate JTAG
commands.

I've wired up the COP connection on my board via an FPGA,
so that I could conceivably use the PowerPC JTAG via
PCI. However, its the lack of open documentation on the
JTAG commands that has limited my interest in pursuing
this. However, it would be simple to use that interface
to log all JTAG transactions, to figure out all the
JTAG TAP instructions.

Cheers,
Dave

  reply	other threads:[~2009-06-16 23:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 23:00 [U-Boot] BDIxxxx and others ksi at koi8.net
2009-06-16 23:24 ` David Hawkins [this message]
2009-06-16 23:34   ` Leon Woestenberg
2009-06-16 23:43     ` David Hawkins
2009-06-17  5:39   ` Wolfgang Denk
2009-06-17 15:41     ` ksi at koi8.net
2009-06-17 13:53   ` Jerry Van Baren
2009-06-17 15:55     ` David Hawkins
2009-06-17  5:37 ` Wolfgang Denk

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=4A382998.4010300@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=u-boot@lists.denx.de \
    /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