This is the mail archive of the
mailing list for the eCos project.
RE: i386 RedBoot serial
- From: "Ecer, Jiri" <jecer at Rational dot Com>
- To: "'Jonathan Larmour'" <jlarmour at redhat dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Thu, 7 Feb 2002 14:21:03 -0500
- Subject: RE: [ECOS] i386 RedBoot serial
I am interested in separating the ecos application's standard I/O from the
communication with gdb. The gdb link should use one serial port and the IO
the other. When I tried to change CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE from
/dev/ttydiag to /dev/tty0 or /dev/tty1, the application receives SIGSEGV in
Cyg_StdioStream::flush_output_unlocked as soon as anything is outputted to
standard output. I made sure that CYGPKG_IO_SERIAL_TTY_TTY0 and
CYGPKG_IO_SERIAL_TTY_TTY1 are enabled.
So, I am looking for information on how to do that.
From: Jonathan Larmour [mailto:firstname.lastname@example.org]
Sent: February 7, 2002 1:24 PM
To: Ecer, Jiri
Subject: Re: [ECOS] i386 RedBoot serial
"Ecer, Jiri" wrote:
> Is there documentation that expalins the relationship between the two
> ports and the diag serial device?
Sounds like a vague question. What do you need to know?
> I am using a PC with two serial ports and trying to use the first serial
> port for redboot and for the gdb <-> eCos link and the second port for
> ecos application's standard input and output. I have tried configurations
> that made sense to me without success. In particular:
> Redboot posts boot message on all available serial port and claims the one
> that receives the first character as the one (as described in the original
> message). This port can then be used by the ecos application to
> with gdb. Can the other port be used as well (in my case for standard
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine