From: Daniel Jacobowitz <drow@false.org>
To: Larry Osborn <LOsborn@asset-intertech.com>
Cc: gdb@sourceware.org
Subject: Re: FW: GDB server configuration
Date: Fri, 17 Aug 2007 19:20:00 -0000 [thread overview]
Message-ID: <20070817192037.GA3223@caradoc.them.org> (raw)
In-Reply-To: <63C0A08D6E871C4599B3619112CF0DF96204BC@exchange.corp.asset-intertech.com>
On Fri, Aug 17, 2007 at 02:11:58PM -0500, Larry Osborn wrote:
>
> Hello All,
>
> I'm new to gdb so I apologize in advance if these questions are
> lame. I'm trying to connect a JTAG device to GDB. This device does
> not support either serial or tcp/ip so the remote connection won't
> work. The interface is actually PCI. I was wondering if the
> gdbserver would work. It is not clear to me from the documentation
> if the server has to run on the embedded target or on the host. My
gdbserver is specifically for remote debugging of userspace programs
on Unix-like (or, now, Windows-like) systems.
> desire is to have the debugger run on a window host, connected to
> JTAG hardware, and then connected to a PowerPC target. If you can
> point me to what I should read or any tips on this subject would be
> very helpful.
You need a "stub" which translates from the JTAG device's interface to
GDB's remote protocol. You'll have to check with your tools vendor or
JTAG vendor to see whether one exists; usually these are proprietary
applications, since vendors are not willing to publish specs for their
JTAG devices. I know CodeSourcery's tools support a bunch of JTAG
units, but none which are PCI cards.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-08-17 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 19:12 Larry Osborn
2007-08-17 19:20 ` Daniel Jacobowitz [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=20070817192037.GA3223@caradoc.them.org \
--to=drow@false.org \
--cc=LOsborn@asset-intertech.com \
--cc=gdb@sourceware.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