linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: gdb load address and KERNELLOAD
Date: Wed, 04 Apr 2001 08:42:19 +0200	[thread overview]
Message-ID: <20010404064224.72482281DB@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 03 Apr 2001 22:05:34 EDT." <3ACA816E.71E4FA67@mvista.com>


In message <3ACA816E.71E4FA67@mvista.com> Dan Malek wrote:
>
> The only BDM debugger that works successfully with Linux is the
> Abatron gdb/BDI2000, hosted on a Linux platform.

This is absolutely correct except for the word "only".

The BDM4GDB  project  at  sourceforge  (see  bdm4gdb.sourceforge.net)
provides all necessary information to build a home-made parallel port
adapter  (schematics, source extension to GDB) which allows to do the
same. If you cannot build a simple PCB  yourself,  we  offer  BDM4GDB
adapters  at  production  cost ($ 50, including a CD-ROM with sources
and binary for the modified GDB) as a service to the Linux community.

The main differences between the BDI2000 and BDM4GDB:

* BDI2000 connects to the Ethernet, BDM4GDB needs a parallel port  on
  a PC.
* BDI2000 has support for  many  CPU  types,  BDM4GDB  restricted  to
  MPC8xx (so far)
* BDI2000 has support for all comon flash types, BDM4GDB  needs  some
  more  work  in that area (but you can adapt it yourself when needed -
  it's Open Source)
* BDI2000 is much faster for code download / flash programming
* The BDI2000 costs around $ 2,500, BDM4GDB $ 50.

Shameless plug:

I will give a presentation "Debugging  of  Linux  Kernel  and  Device
Drivers  Using Low-Cost BDM Interface" featuring the BDM4GDB on May 4
at the 3rd Brunswick Linux Days, see
http://braunschweiger.linuxtage.de/programm/index.html

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Remember that Beethoven wrote his first symphony in C ...

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

  reply	other threads:[~2001-04-04  6:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04  0:57 gdb load address and KERNELLOAD Wang Yong
2001-04-04  2:05 ` Dan Malek
2001-04-04  6:42   ` Wolfgang Denk [this message]
2001-04-04 15:30     ` Dan Malek
2001-04-04 15:54       ` Wolfgang Denk
2001-04-05  4:13         ` how to get the physival address jerry
2001-04-05  5:58           ` Dan Malek
2001-04-05  6:28             ` jerry
2001-04-05  6:30               ` Dan Malek
2001-04-05  9:16             ` Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2001-04-04  3:04 gdb load address and KERNELLOAD Hua Ji

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=20010404064224.72482281DB@denx.denx.de \
    --to=wd@denx.de \
    --cc=dan@mvista.com \
    --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).