From: Tim Hatton <tim@coherent-tech.co.uk>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] How to temporarily hijack console serial port
Date: Wed, 21 Feb 2007 09:19:00 -0000 [thread overview]
Message-ID: <9077603.post@talk.nabble.com> (raw)
Hi,
I am currently in the process of building an application with eCos (2.0.43)
running on our own hardware which uses an ATMEL AT91RM9200 CPU.
I have a strange requirement which I'm not sure how to fulfil at the moment.
Our application uses many serial ports talking to other devices (via termios
drivers) and one device has been configured eCos to use one of the serial
ports as the C console (stdin/stdout) which is used as a user interface for
configuration etc.
So far, so good. We now have a requirement to also be able to plug a device
into the user interface port sometimes. So now I would like to allow the
application to temporarily "hijack" the console serial port and open it as a
termios port for a while to talk to the device and then "return" it to it's
user interface use.
So, is there anyway to tell eCos (or I guess the C library) to stop using a
particular port as the console at run time and then re-instate it? (There's
no problem within the context of the application to know when to change from
one "mode" to the other, I just don't know how to do it).
If anyone has any ideas I'd be very grateful,
Best regards,
Tim Hatton
--
View this message in context: http://www.nabble.com/How-to-temporarily-hijack-console-serial-port-tf3265595.html#a9077603
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2007-02-21 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9077603.post@talk.nabble.com \
--to=tim@coherent-tech.co.uk \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).