This is the mail archive of the
mailing list for the GDB project.
Re: MultiICE, gdb and parallel port
- To: Dan Hovang <d at wespot dot com>
- Subject: Re: MultiICE, gdb and parallel port
- From: Fernando Nasser <fnasser at redhat dot com>
- Date: Thu, 08 Nov 2001 09:56:15 -0500
- CC: ARM Linux List <linux-arm at lists dot arm dot linux dot org dot uk>, dave at cdlusa dot com, gdb at sources dot redhat dot com, Keith Seitz <keiths at cygnus dot com>
- Organization: Red Hat Canada
- References: <3BEA7490.95290FEF@wespot.com>
Dan Hovang wrote:
> I'm trying to get arm-elf-gdb 5.0 (to be more precise, insight)
> to run using a MultiICE over the parallel port. After some failed
> attempts using "target rdi p=/dev/lp0" and similar I began
> tracing the gdb code and found that there are three protocols to
> use; serial, ethernet and serpar. It seems like the serpar
> would be my best bet, but from what I can read from the source it
> uses BOTH serial and parallel connections at the same time; serial
> for reads and parallel for writes. My MultiICE has parallel interface
Good point. I don't have any device like that here so I was thinking
of P as parallel port only but, of course, you are right: it is actually
a combination of serial and parallel.
Are you sure your MultiICE device will work fine if you can communicate
with it (by writing a parallel driver)? If it speaks the Angel protocol
it probably will. But I guess the only way to know is to try and write
Anyway, if you decide to do that, please talk to me first so we can get
to sign an assignment to FSF. This way we can incorporate your driver
the GDB code and other people can benefit from it as well.
> I want to use gdb. What to do? Should I implement a parallel only
> driver for gdb? It does not seem like that much work; the driver
> infrastructure is real nifty. But any help would be most appreciated.
> "Gathright, Dave" wrote:
> > first you have to compile a version of gdb for arm. i am currently
> > using gdb-5.0, and it works well. then connect to your ICE or Angel
> > debugger using the "target rdi X=Y" command, where X is the
> > interface type and Y is the specific interface ('E' is ethernet,
> > e.g. e=192.168.0.10; 'S' is serial, e.g., s=/dev/tty0; and P is
> > parallel port, e.g. p=/dev/lp0). now you can load your executable
> > (compiled with -g option, of course). there are some features that
> > may need to be disabled if your are using a JTAG ICE. my target
> > has ROM at address zero, so in gdb i have to 'set rdiromatzero 1'
> > to disable vector catching and semi-hosting.
> Dan Hovang email@example.com +46 733 451 427
> WeSpot AB Sölvegatan 41 223 70 Lund, Sweden
Red Hat Canada Ltd. E-Mail: firstname.lastname@example.org
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9