1 |
Hi, |
2 |
|
3 |
> The Linux app has a separate thread for each of the 2 serial ports. |
4 |
> Data is received using select() and read(). Read is called with a 32 |
5 |
> byte buffer. As neither BRKINT nor IGNBRK is set, the input thread |
6 |
> recognizes 0xFF, 0x00, 0x00 sequences as breaks. When the encoded |
7 |
> break is recognized, any pending message is sent. |
8 |
|
9 |
There should be no problem handling 115K2 data at full speed on a 300MHz |
10 |
processor although some SOC UARTs are realy gnarly. Using line break as |
11 |
a protocol signalling element is so 1970s but again shouldn't be a problem. |
12 |
|
13 |
What are your VMIN, VTIME settings ? They can have a big impact on read |
14 |
performance/timing. VMIN=VTIME=0 makes a mockery of using select for |
15 |
example. |
16 |
|
17 |
What size of return are you actually seeing from the read ? |
18 |
|
19 |
If you are seeing reasonably full blocks, does you code handle the three char |
20 |
break sequence spanning the read boundy ? Sorry if this is teaching grandma |
21 |
to suck eggs. |
22 |
|
23 |
-- |
24 |
Bob Dunlop |