1. esccp_2009_02_26.zip Driver
2. HOWTO.txt File Contents

HOWTO.txt Driver File Contents (esccp_2009_02_26.zip)

This describes how to use extended transparent mode on an ESCC card.
Read the README.txt file for a brief description of why all this is necessary.

Included are a handful of utilities that I used to test this mode.  It is 
assumed that you will use the accompanying source code as a starting point to 
write your own program to handle extended transparent mode.

I had port 1 connected to port 2 via a crossover cable (SD->RD, TT->RT).

Open two console windows and execute:

write_random 0 128 wout

in one window and:

read 1 rout

in the other.

Let it run for a bit, then stop the read window (hit a key). Then stop the
transmitter (hit a key).

I was able to do this a couple of times, I verified a file that was about 5megs
and one that was about 27megs.

The load on my machine was noticable, it was running at 80/20 privilaged/user time
with an interrupt rate around 500-700.

Please note that the machine that I was doing this on is a 233MHz MMX pentium
with 64M of ram.  A more well endowed machine will probably not even notice that
this is going on...

To verify the files a couple of utilities were generated (ts_comp,shifter,disp_bin)
The out file may or may not be the same as wout, since more than likely the
two programs aren't started at the same time, the beginning points in the file
will be different, but more importantly the receiver will not do any kind of byte
alignment in the mode we are using, so the entire stream could very well be shifted 
by 0-7 bit positions from the output stream.

If you run the shifter program on the read output file as:

shifter 1 rout rout1
shifter 2 rout rout2
shifter 3 rout rout3
shifter 4 rout rout4
shifter 5 rout rout5
shifter 6 rout rout6
shifter 7 rout rout7

Then one of the files rout,rout1,rout2,rout3,rout4,rout5,rout6,rout7 will compare with
the wout file successfully.

The ts_comp program can be used to verify the data, it scans the input file for
the framecounter, and then scans the wout file for the same counter value, then
compares the rest of the bytes in the file.

You should expect that the last couple of bytes will fail, as they are artifacts
of the shifter program.
one of:

ts_comp rout wout
ts_comp rout1 wout
ts_comp rout2 wout
ts_comp rout3 wout
ts_comp rout4 wout
ts_comp rout5 wout
ts_comp rout6 wout
ts_comp rout7 wout

should successfully compare the bulk of the saved files, and indicate only
the handfull of errors at the end of the file.

The read program will dump data read from a port and save the data to the specified file.

The write_random program will generate a random bitstream with a 12 byte
framecounter placed every (blocksize) bytes in the file. (the 12 byte sequence
is 0xff,0x00,8 digit ascii counter,0x00,0xff).  It outputs this stream to the
given ESCC port, and optionally also to a specified file.
(if you make the blocksize small and the bitrate fast, and the system is
loaded too much you will not end up with a continuous output, which you
will see as long strings of 0xff's in the received file) increasing the blocksize
should take care of this.

The disp_bin program dumps a binary file to the screen as hex digits,
25 bytes to a row.

The lsb2msb program can be used to change the bit order of a file from lsb to
msb first.  This code might be necessary if you expect your data to be msb first 
on the line (as the 82532/20534 receives and transmits data lsb first).

The shifter implements an algorithm to shift a lsb received data stream by the
given number of bits.

The ts_comp program searches the input file for the 12 byte framecounter sequence
(as per write_random) and when it finds a likely suspect, it then looks for that
framecount in the compare file, and then compares the rest of the input file
to the data in the compare file.