1 |
David Relson wrote: |
2 |
|
3 |
> I'm porting a DOS application to Linux and have encountered problems |
4 |
> with the high speed serial devices from which the app receives data. |
5 |
|
6 |
|
7 |
|
8 |
Well here is link to a home brewed Serial Chip buffering |
9 |
circuit, that may better allow you to look at the signals |
10 |
and protocol interactions on your serial ports. I have found |
11 |
the hardware ckt to help (stabalize) bit sniffing on serial |
12 |
communications. The keyword is 'eavesdropping' as used |
13 |
by embedded designers. What good about this project, is it |
14 |
is an easy, practical work that allows you to learn the art |
15 |
of eavesdropping on a com link, rs232C being the vintage |
16 |
form. RS485 will come much easier into enlightenment for you.... |
17 |
|
18 |
|
19 |
You can download the tar file from here: |
20 |
|
21 |
http://sourceforge.net/projects/serialsniffer/ |
22 |
|
23 |
|
24 |
|
25 |
If you look at the file: LinuxSPA.png (after unpacking the |
26 |
tar file), you'll see the circuits; I used gimp, then you |
27 |
can see the chips used to buffer the signals are the old |
28 |
reliable 1488 and 1489. |
29 |
|
30 |
I'm not sure about the max speed, I believe its around |
31 |
500kbps, so you might have to find newer, faster |
32 |
replacements chips for the 1488 and the 1489..... |
33 |
|
34 |
|
35 |
When you go to test your hardware/software between the new |
36 |
embedded linux system and a tried and proven dos based |
37 |
system, this sort of buffering circuit is very valuable to |
38 |
keep from "loading/distorting" the signals between the 2 |
39 |
different devices, particularly as the speed of |
40 |
communications increases. |
41 |
|
42 |
|
43 |
You can look at both ends of the serial communications |
44 |
with 2 different windows on each side of the comm link, to |
45 |
discerning transmission issues, such as timing sync, skew |
46 |
etc etc. |
47 |
|
48 |
|
49 |
hth, |
50 |
James |