This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: shell application


On Sat, Sep 17, 2005 at 07:50:21PM +0200, Jaws wrote:
> Hi Andrew,
>     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
> console.
> How can I have to do to differentiate the input/output channel to have all
> on the serial interface for example?

You need to change the default console.

CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE 

It will be using /dev/ttydiag which is being directed to gdb. You need
to change this to one of your serial ports.

        Andrew


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]