public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS]Console-input & GDB
@ 2000-12-05  2:23 Andrea Acquaviva
  2000-12-05  2:33 ` Andrew Lunn
  0 siblings, 1 reply; 3+ messages in thread
From: Andrea Acquaviva @ 2000-12-05  2:23 UTC (permalink / raw)
  To: ecos-discuss

Hi all,

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?

Thanks,
Andrea.


--
Ing. Andrea Acquaviva
D.E.I.S. - Universita' di Bologna
V.le Risorgimento, 2    40136 BOLOGNA (ITALY)
Tel: (+39) 051 20 93787 Fax: (+39) 051 2093786



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS]Console-input & GDB
  2000-12-05  2:23 [ECOS]Console-input & GDB Andrea Acquaviva
@ 2000-12-05  2:33 ` Andrew Lunn
  2000-12-05  6:40   ` Bart Veer
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Lunn @ 2000-12-05  2:33 UTC (permalink / raw)
  To: Andrea Acquaviva; +Cc: ecos-discuss

> 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?

This is one of those issues that comes up every so often. No its not
possible to use a serial port for both gdb and I/O. You either need
two serial ports, or you connect gdb to the target via some other
means like ethernet or maybe JTAG. 

        Andrew

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS]Console-input & GDB
  2000-12-05  2:33 ` Andrew Lunn
@ 2000-12-05  6:40   ` Bart Veer
  0 siblings, 0 replies; 3+ messages in thread
From: Bart Veer @ 2000-12-05  6:40 UTC (permalink / raw)
  To: acquaviva; +Cc: ecos-discuss

>>>>> "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.

Bart

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-12-05  6:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-12-05  2:23 [ECOS]Console-input & GDB Andrea Acquaviva
2000-12-05  2:33 ` Andrew Lunn
2000-12-05  6:40   ` Bart Veer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).