Re: using Parallel Port as remote debugging.

[jtc at redback dot com (J.T. Conklin)]

>>>>> "amdnship" == ±è±âÇö  <amdnship@hanmail.net> writes:
amdnship> I wanna use Parallel Port instead of serial port when remote
amdnship> debugging.  it is possible?

Yes, but not out of the box.

amdnship> if possible. let me know howto using~!

It depends on your host and target systems.  I'll answer as best as I
can in generalities.

The remote serial protocol can run over any wire-like transport.
While it is defined in terms of packets, the lack of error handling
makes it risky to run over datagram transports where packets can be
lost, duplicated, or delivered out of order.  Fortunately for you, a
bi-directional parallel connection is should work fine.

GDB comes with support for serial, tcp, and UNIX pipe transports (see
ser-*.c).  You will need to a ser-parallel.c to add support for your
parallel transports.  The debug agents (stubs), at least the example
ones that are distributed with GDB, are transport independent.  Even 
with a serial transport, the user needs to supply the getDebugChar() 
and putDebugChar() functions.  You just need to write a version that
works with your target's parallel port hardware.

There is support in serial.c that handles parallel ports, so for your
if you name your parallel transport "parallel" (see ser-*.c files), it
looks like you can do:

        target remote lpt

And your code will be used.

        --jtc

-- 
J.T. Conklin
RedBack Networks