[ECOS]Console-input & GDB

Bart Veer bartv@redhat.com
Tue Dec 5 06:40:00 GMT 2000

>>>>> "Andrew" == Andrew Lunn <andrew.lunn@ascom.ch> writes:

    >> in the eCos Reference Manual, pg. 117, I found that GDB remote
    >> protocol not allows console-input functionality for the
    >> applications. This means that is never possible to debug an
    >> application which requires such functionality, or is there any
    >> workaround?

Theoretically, if the embedded application needs keyboard input then
you need some sort of keyboard device on the target hardware, plus an
appropriate device driver. Granted, during initial development it
might sometimes be useful to use the host's keyboard instead, but that
functionality is not supported at present.

If you need something more general such as full serial I/O then, as
Andrew says, that really requires a separate serial port. Sharing a
communications channel for both debugging and real I/O is usually a
bad idea.

Theoretically the GDB remote protocol can be extended to provide some
sort of general purpose I/O service, allowing the target to access the
host's filing system and other devices until such time as the
corresponding target-side device drivers are up and running, but that
is for long term wish lists.


More information about the Ecos-discuss mailing list