From: Wolfgang Denk <wd@denx.de>
To: Karl P lsson <KPA@infocom.dk>
Cc: linuxppc-embedded@lists.linuxppc.org,
Frank Przybylski <Frank.Przybylski@vas-gmbh.de>
Subject: Re: Recommend a debugger
Date: Thu, 17 Feb 2000 21:15:51 +0100 [thread overview]
Message-ID: <200002172015.VAA13366@denx.local.net> (raw)
In-Reply-To: Your message of "Thu, 17 Feb 2000 10:45:09 +0100." <819E3E914E0AD11194DE00805F0D100B01088335@fbi.infocom.dk>
Hi Karl,
in message <819E3E914E0AD11194DE00805F0D100B01088335@fbi.infocom.dk> you write:
>
> What are people using for debugging code on the target, using the MPC823
> debug port?. What are the options and which debugger can you recommend?
What do you want to debug?
Application code? Then you should do fine with gdbserver on the
target and GDB / DDD on the host.
Kernel code? Are you looking for a BDM based debugger? There is no
perfect solution available right now. There are some pretty good, but
expensive professional solutions that run on the Linux host (for
instance, by Lauterbach and ETS), but they do not include any special
support for the Linux target - especially, they do not support the
MMU (so you will not be able to do kernel source code debugging once
the MMU is on, which is pretty early).
There are some cheaper solutions (MacCraigor) with similar problems.
Several people built their own debugger interfaces. The latest I've
seen is by Frank Przybylski <Frank.Przybylski@vas-gmbh.de>, see
http://www.vas-gmbh.de/software/mpcbdm/
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"A little knowledge is a dangerous thing." - Doug Gwyn
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-02-17 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-17 9:45 Recommend a debugger Karl Pálsson
2000-02-17 20:15 ` 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=200002172015.VAA13366@denx.local.net \
--to=wd@denx.de \
--cc=Frank.Przybylski@vas-gmbh.de \
--cc=KPA@infocom.dk \
--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).