[ECOS] shell application
Sun Sep 18 06:32:00 GMT 2005
Usually I use the ethernet channel for gdb (but the same problem I saw
some times ago using gdb on the serial /dev/ttyS3).
When I run an application like one of the tests application, all of the
output messages are reported by default on the gdb console. the problem is
when an input is required; probably this makes a conflict with gdb
In my application the command is this:
fgets(in, nINBUF, stdin);
and it use the stdin. Probably it is assigned by default with the gdb
How can I have to do to differentiate the input/output channel to have all
on the serial interface for example?
----- Original Message -----
From: "Andrew Lunn" <email@example.com>
To: "Jaws" <firstname.lastname@example.org>
Sent: Saturday, September 17, 2005 6:46 PM
Subject: Re: [ECOS] shell application
> On Sat, Sep 17, 2005 at 06:36:12PM +0200, Jaws wrote:
> > Thanks David, Andrew
> > I successfully ported the ZOG version in the actual ecos version and
> > compiled an application for arm.
> > I'll update the ficl used in ZOG with the last version from sourceforge.
> > A problem is still present. I created a test application ( starting form
> > testmain.c).
> > The problem is that executing the application from gdb the program run
> > it mets the first fgets.
> > At this point it remains blocked. I think is a general problem that I
> > not related to this specific application.
> What file descriptor is it trying to read from? Does it want it in raw
> mode? cooked? etc? Which serial device are you using? /dev/ser0
> /dev/tty0? You have to use a different serial device to the one gdb
> is using.
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss