From: "George Sosnowski" <george@stratalight.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Serial getc problem
Date: Mon, 08 Jul 2002 09:35:00 -0000 [thread overview]
Message-ID: <F626113795D3EB4482E5ACFBD9346512138308@mailhost.stratalight.com> (raw)
I have come across a similar situation using the 860T. My platform has
one serial port (SMC1 used as diag and console port) and currently I
inherit the serial channel from redboot. Is it still possible to have a
'proper' /dev/tty0 that uses the inherited serial channel (diag/console)
from redboot? Or does the ecos ram image have to install its own
/dev/ser0 for console and diag channels since these are the same device?
Thanks,
George
-----Original Message-----
From: Robert Cragie [mailto:rcc@jennic.com]
Sent: Thursday, July 04, 2002 10:26 AM
To: Daniel Lidsten; ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Serial getc problem
You need to use a 'proper' serial driver (/dev/tty0 or /dev/tty1), not
/dev/ttydiag. These allow blocking reads which will allow other threads
to
run; as you have seen, /dev/ttydiag does a busy wait on a character
which
will stop other threads from running. You can configure eCos so that
stdio
uses /dev/tty0 or /dev/tty1.
Regards,
Robert Cragie, Design Engineer
Direct: +44 (0) 114 281 4512
________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
www.jennic.com Tel: +44 (0) 114 281 2655
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Daniel
> Lidsten
> Sent: 04 July 2002 17:19
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Serial getc problem
>
>
> Hi,
>
> I am running a MPC850 with a few different threads in the application.
> The network stack is also enabled and up and running. However, when a
> thread calls the HAL_DIAG_READ_CHAR to wait for input from the user
then
> my net stack stops working. I cant reach it with a ping from my local
> host.
>
> My first thought was that the application was running with a higher
> priority (lower value) then the net stack but that was not the case.
The
> application runs at prio 8 and net at 6 and 7 (background).
>
> I have seen in the serial driver that when reading a char from the
port
> then the following is done:
>
> while ( !getc_non_block(..) )
>
> Can the problem be that this code is running in some form of "kernel
> state" i.e. in a very high prio state since the driver lies within
eCos?
>
> Regards, Daniel
>
> --
> Before posting, please read the FAQ:
http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2002-07-08 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 9:35 George Sosnowski [this message]
2002-07-08 9:43 ` Gary Thomas
2002-07-09 3:49 ` Robert Cragie
-- strict thread matches above, loose matches on Subject: below --
2002-07-05 1:14 Daniel Lidsten
2002-07-04 12:58 Daniel Lidsten
2002-07-04 9:20 Daniel Lidsten
2002-07-04 10:25 ` Robert Cragie
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=F626113795D3EB4482E5ACFBD9346512138308@mailhost.stratalight.com \
--to=george@stratalight.com \
--cc=ecos-discuss@sources.redhat.com \
/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).