* Re: [Xenomai-help] error after timeout on serial port
@ 2007-02-23 15:23 Nicolas BLANCHARD
0 siblings, 0 replies; 3+ messages in thread
From: Nicolas BLANCHARD @ 2007-02-23 15:23 UTC (permalink / raw)
To: Nathan.Lauener; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
>>>> Jan Kiszka <jan.kiszka@domain.hid> 23.02 15:51 >>>
>Lauener Nathan wrote:
>> Hi,
>>
>> I am polling on a serial port during an init sequence of a
positioning
>> device. Every once in a while I get a return code indicating that a
>> timeout occured, code -110 (ETIMEDOUT).
In the struct rtser_config you have the event_timeout parameter that
cause
ETIMEDOUT (if it's different than RTSER_DEF_TIMEOUT).
Have a look on rt_dev_ioctl(uiFd, RTSER_RTIOC_WAIT_EVENT, &rx_event ).
>After a timeout occured I can't
>> read the port anymore. Whenever I call rt_dev_read() again the
function
>> returns the error code -14 (EFAULT). Is there a flag I must clear to
get
>> the port operatioanl again?
Is your device correctly open (file descriptor>=0) ?
>
>I /tend/ to say it's an application bug, because we are using the
driver
>heavily, and our sluggish devices often cause timeouts during setup.
>Some colleague should have already slapped me otherwise. :)
>
>Are you sure that a valid buffer and a valid size is passed to
>rt_dev_read after the timeout (because those should be the reason for
>EFAULT)? If yes, maybe you can post a simple demo for the effect.
>
>Jan
Blanchard nicolas
[-- Attachment #2: HTML --]
[-- Type: text/html, Size: 1851 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xenomai-help] error after timeout on serial port
2007-02-23 14:29 Lauener Nathan
@ 2007-02-23 14:51 ` Jan Kiszka
0 siblings, 0 replies; 3+ messages in thread
From: Jan Kiszka @ 2007-02-23 14:51 UTC (permalink / raw)
To: Lauener Nathan; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Lauener Nathan wrote:
> Hi,
>
> I am polling on a serial port during an init sequence of a positioning
> device. Every once in a while I get a return code indicating that a
> timeout occured, code -110 (ETIMEDOUT). After a timeout occured I can't
> read the port anymore. Whenever I call rt_dev_read() again the function
> returns the error code -14 (EFAULT). Is there a flag I must clear to get
> the port operatioanl again?
I /tend/ to say it's an application bug, because we are using the driver
heavily, and our sluggish devices often cause timeouts during setup.
Some colleague should have already slapped me otherwise. :)
Are you sure that a valid buffer and a valid size is passed to
rt_dev_read after the timeout (because those should be the reason for
EFAULT)? If yes, maybe you can post a simple demo for the effect.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Xenomai-help] error after timeout on serial port
@ 2007-02-23 14:29 Lauener Nathan
2007-02-23 14:51 ` Jan Kiszka
0 siblings, 1 reply; 3+ messages in thread
From: Lauener Nathan @ 2007-02-23 14:29 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Hi,
I am polling on a serial port during an init sequence of a positioning
device. Every once in a while I get a return code indicating that a
timeout occured, code -110 (ETIMEDOUT). After a timeout occured I can't
read the port anymore. Whenever I call rt_dev_read() again the function
returns the error code -14 (EFAULT). Is there a flag I must clear to get
the port operatioanl again?
Regards
Nathan
[-- Attachment #2: Type: text/html, Size: 935 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-02-23 15:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-23 15:23 [Xenomai-help] error after timeout on serial port Nicolas BLANCHARD
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 14:29 Lauener Nathan
2007-02-23 14:51 ` Jan Kiszka
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.