[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom ["Stephen D. Cohen" <scohen@xybion.com>] (fwd)



>From owner-rtl Fri Jun  1 08:44:20 2001
Received: from xsiis.xybioncorp.com (mail.xybioncorp.com [12.20.208.3])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f51EiKs17878
	for <rtl@fsmlabs.com>; Fri, 1 Jun 2001 08:44:20 -0600
Received: from exchange.xybion.com (exchange_server [192.168.20.21]) by xsiis.xybioncorp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id MAY9Q6F7; Fri, 1 Jun 2001 10:39:03 -0400
Received: by EXCHANGE with Internet Mail Service (5.5.2653.19)
	id <L1JRXYJB>; Fri, 1 Jun 2001 10:39:02 -0400
Message-ID: <235B3E173BB3D311B88C00508B8B6C62500984@EXCHANGE>
From: "Stephen D. Cohen" <scohen@xybion.com>
To: "'rtl@fsmlabs.com'" <rtl@fsmlabs.com>,
   "'Evgeni_Dobrev@excite.com'"
	 <Evgeni_Dobrev@excite.com>
Subject: RE: [rtl] rt_com 
Date: Fri, 1 Jun 2001 10:38:55 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"

Evgeni,

> i am writing a device driver for an eib (European Instalation 
> Bus) device. 
> It communicates with a serial port.  I wrote my own module 
> which I load with
> rt_com and communicate with the device (19200 8n1)- it sends 
> the computer a
> byte and the computer sends it back.  The problem is that I 
> want to make the
> response time of the serial device smaller.
> 
> see i connected an osciloscope to the serial port and 
> measured delay of 2.2
> miliSecs between the time the driver gets the byte and send 
> the answer.  I
> need to bring the time down to a bit less than 150 microSecs.

	I will not profess to fully understanding your complaint, but it
sounds like you are saying that you are receiving a single byte and that it
appears to take an inordinately long time.  If that is the case, you have
probably hit a fairly common problem with rt_com.

	The problem is that there are FIFOs on most modern UARTS.  rt_com,
by default, enables these FIFOs.  If the FIFOs are enabled, a receive
interrupt is not generated until either the FIFO fills, or a time-out has
occurred.  You probably want to disable the FIFO for your application, or
else reduce the time-out.  A quick browse of the rt_com code will show how
this is done (I do not remember off the top of my head).

Regards,

Steve