From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29109 invoked by alias); 4 Jul 2002 19:58:58 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 29102 invoked from network); 4 Jul 2002 19:58:55 -0000 Received: from unknown (HELO venus.combitech.se) (146.75.247.84) by sources.redhat.com with SMTP; 4 Jul 2002 19:58:55 -0000 Received: from ratatosk.combitechsystems.com (localhost [127.0.0.1]) by venus.combitech.se (8.11.6/8.11.6) with ESMTP id g64Ju8x22833; Thu, 4 Jul 2002 21:56:08 +0200 (MEST) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Thu, 04 Jul 2002 12:58:00 -0000 Message-ID: <004B1D7A5257174C9044A1B7BD0E60ED232BD6@ratatosk.combitechsystems.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Daniel Lidsten" To: "Robert Cragie" , Subject: RE: [ECOS] Serial getc problem X-SW-Source: 2002-07/txt/msg00043.txt.bz2 Hi again, I have tried to install such a serial driver but can=B4t access it later on= in the application. How should i configure eCos? When i do a cyg_io_lookup= then i can find the following drivers: dev/ttydiag dev/tty0 dev/hal_diag ...but during the lookup procedure there is a check on "dep_name" and that = is set to "dev/ser0", which is not found among the above. What values/strings shall be entered under the section "TTY-mode serial dri= vers" in eCos config tool to make this work. Regards, Daniel -----Original Message----- From: Robert Cragie [mailto:rcc@jennic.com]=20 Sent: den 4 juli 2002 19:26 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: +4= 4 (0) 114 281 2655 > -----Original Message----- > From: ecos-discuss-owner@sources.redhat.com > [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Daniel=20 > 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.=20 > The network stack is also enabled and up and running. However, when a=20 > thread calls the HAL_DIAG_READ_CHAR to wait for input from the user=20 > then my net stack stops working. I cant reach it with a ping from my=20 > local host. > > My first thought was that the application was running with a higher=20 > priority (lower value) then the net stack but that was not the case.=20 > 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=20 > port then the following is done: > > while ( !getc_non_block(..) ) > > Can the problem be that this code is running in some form of "kernel=20 > state" i.e. in a very high prio state since the driver lies within=20 > eCos? > > Regards, Daniel > > -- > Before posting, please read the FAQ:=20 > 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