gdb and jtag

William A. Gatliff
Tue Nov 5 07:56:00 GMT 2002


Take a look at rproxy.  I think it's what you really want to embrace
and extend, sort of a gdbserver for remote debugging--- with the
server running on the host instead of the target.

You'd futz with rproxy sources to get it talking to your jtag unit,
then gdb would use its native RSP protocol (also documented on the
aforementioned page) to talk to rproxy.  In short, you wouldn't touch
gdb sources at all.



On Tue, Nov 05, 2002 at 07:43:57AM -0800, Doug Evans wrote:
> Simon Berry writes:
>  > Hi all
>  > 
>  > Does anyone know how one would go about creating an interface/back-end to
>  > gdb that use JTAG/ICE to debug a target board ? I know that there are
>  > commercial offerings (e.g raven,wiggler etc from Macraigor) but I want to
>  > use my own "JTAG hardware" (similar to altera byteblaster).
>  > 
>  > At the moment I am using a small program by Simon Wood to control the target
>  > processor via JTAG. This implements a simple debugger (with the JTAG
>  > "protocol" in software, unlike the commercial offerings) and connects to the
>  > target via the abovementioned "byteblaster" type cable (on parallel port).
>  > However I wish to use the superior (no offence Mr Wood) capabilities of gdb
>  > (breakpoints, stepping etc.).
>  > 
>  > My feeling is that I could use the base code that I have and somehow adapt
>  > it to present an interface that GDB needs (the fundamental question: what is
>  > this interface ????).
> Study the remote*.c files in the gdb sources and pick one to use as
> boilerplate.  The canonical one is remote.c.
> ------
> Want more information?  See the CrossGCC FAQ,
> Want to unsubscribe? Send a note to
Bill Gatliff
I'm an embedded GNU developer first, GNU instructor second.
See for details.

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list