RE: [gentoo-embedded] High Speed Serial Problem

Hello Bob,

VMIN and VTIME are the default values of 1 and 0, respectively.  If I
understand correctly, these settings will provide data as rapidly as
possible.

At present, I am using a 256 byte buffer for reading data.  I've added
some statistics gathering.  Every 1000 reads, the program logs the total
bytes read and the maximum read.  The program was run for 30 seconds to
provide 6 statistics records

With _no_ processing of data, 1000 reads got from 27,545 to 28,520
chars.  The max read was 128 chars.  3 of the 1000 read samples had max
reads of 56 or 57 and 3 had max reads of 110, 126, and 128.

With copying of data to a buffer (which involves several function calls,
incrementing counters, etc), 1000 reads got from 27,187 to 28,241 chars
and each of the 6 sample sets had a max read of 110 to 128 bytes.

One would expect processing to increase the total bytes received, but
this was not the case.

The code _is_ handling the 3 char break sequence and the (undocumented)
doubling (escaping) of 0xFF chars (to distinguish them from break
sequences).

Regards,
 
David
-----Original Message-----
From: Bob Dunlop [mailto:bob.dunlop@×××××××××.uk] 
Sent: Monday, March 15, 2010 9:35 AM
To: gentoo-embedded@l.g.o
Subject: Re: [gentoo-embedded] High Speed Serial Problem

Hi,

> The Linux app has a separate thread for each of the 2 serial ports.
> Data is received using select() and read().  Read is called with a 32
> byte buffer.  As neither BRKINT nor IGNBRK is set, the input thread
> recognizes 0xFF, 0x00, 0x00 sequences as breaks.  When the encoded
> break is recognized, any pending message is sent.

There should be no problem handling 115K2 data at full speed on a 300MHz
processor although some SOC UARTs are realy gnarly.  Using line break as
a protocol signalling element is so 1970s but again shouldn't be a
problem.

What are your VMIN, VTIME settings ? They can have a big impact on read
performance/timing.  VMIN=VTIME=0 makes a mockery of using select for
example.

What size of return are you actually seeing from the read ?

If you are seeing reasonably full blocks, does you code handle the three
char break sequence spanning the read boundy ?  Sorry if this is
teaching grandma to suck eggs.

-- 
        Bob Dunlop