This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |