From: Jesper Skov <jskov@cygnus.co.uk>
To: Rolf.Fiedler@Ferrari.DE
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: debugging a PPC405GP target
Date: 24 Jan 2000 10:33:48 +0100 [thread overview]
Message-ID: <otemb7u83n.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: Rolf Fiedler's message of "Mon, 24 Jan 2000 10:10:28 +0100"
>>>>> "Rolf" == Rolf Fiedler <Rolf.Fiedler@Ferrari.DE> writes:
Rolf> Hi there,
Rolf> currently we are looking for a solution to debug gcc generated
Rolf> code on the PPC405GP target. All debuggers I have found so far
Rolf> are hosted on Win9x/NT. This is sub-optimal, since our
Rolf> tool-chain is hosted on linux.
Rolf> I know that I can use gdb with a gdb-server running on the
Rolf> target, however I prefer access to the JTAG debug port of the
Rolf> PPC405GP. The Macraigor Wiggler devices support JTAG debugging
I don't think this would work (or at least not easily). When you
access the target through a wiggler it's at a very low level (on the
CPU, basically - you don't communicate with software in the
target).
For debugging an application you need to communicate with gdbserver -
ethernet is the optimal solution, if your board has
ethernet. Otherwise you have to use serial.
You may be able to make the wiggler work as a regular serial
connection, but I don't see what you gain by that over using a
standard ethernet/serial connection (except if the only interface on
the board is the wiggler one).
Jesper
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-24 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-24 9:10 debugging a PPC405GP target Rolf Fiedler
2000-01-24 9:33 ` Jesper Skov [this message]
2000-01-24 9:57 ` Rolf Fiedler
2000-01-24 10:42 ` Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
2000-01-24 17:33 Rolf Fiedler
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=otemb7u83n.fsf@thinktwice.zoftcorp.dk \
--to=jskov@cygnus.co.uk \
--cc=Rolf.Fiedler@Ferrari.DE \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.