linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.muc.de>
To: Claude Robitaille <crobitaille@videotron.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: BDM for MPC860
Date: Sun, 02 May 1999 11:31:51 +0200	[thread overview]
Message-ID: <199905020931.LAA23358@denx.muc.de> (raw)
In-Reply-To: Your message of "Sat, 01 May 1999 18:28:05 EDT." <Pine.LNX.3.95.990501181912.11708A-100000@localhost>


In message <Pine.LNX.3.95.990501181912.11708A-100000@localhost> you write:
> 
> I've search the net but I couldn't find anything supporting
> the BDM on an MPC8xx. I found a driver for Coldfire and for
> CPU32.

Well, of course there are lots of tools - commercial  ones.  See  for
instance  PowerTAP  by Applied Microsystems (www.amc.com), Trace32 by
Lauterbach (www.lauterbach.de), visionPROBE by EST (www.estc.com)  or
BlackBird  by  SDS  (www.sdsi.com)  [there  are some other vendors as
well, and usually there is more than one solution from each of  those
vendors]. Be prepared to hear prices in the 5...10 k$ range.

But I guess you  are  looking  for  a  (cheap)  hardware  probe  that
cooperates  nicely  with  some of the common freeware debugging tools
like GDB? This is something I'm looking for, too...

> First, I'd like to use the BDM to download the kernel; is
> there any tools? Eventually, I would also like to debug 
> applications and eventually the kernel.

With one of the above tools those things can be  done.  But  I  don't
know of a solution for the 860 or 8260 that does not take a few k$.

Wolfgang

-- 
Phone:  (+49)-8142-4596-86   Fax: (+49)-8142-4596-88   wd@denx.muc.de
Office: (+49)-89-722-27328               Wolfgang.Denk@ICN.Siemens.DE
It is impractical for  the  standard  to  attempt  to  constrain  the
behavior  of code that does not obey the constraints of the standard.
                                                          - Doug Gwyn

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-05-02  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-01 22:28 BDM for MPC860 Claude Robitaille
1999-05-02  9:31 ` Wolfgang Denk [this message]

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=199905020931.LAA23358@denx.muc.de \
    --to=wd@denx.muc.de \
    --cc=crobitaille@videotron.ca \
    --cc=linuxppc-dev@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).