Installation guide

DC 900-1325I 43
Chapter
3
Interfacing to DLI/TSI and
Protocol Software
Most SRAs built to run on the Freeway server will need to access protocol software run-
ning on an ICP board. The Freeway server code includes an ICP device driver that coor-
dinates moving data from the server platform to the ICP. The only server code that
interacts with the ICP device driver is the message multiplexor (
msgmux) process. The
TSI code communicates with the
msgmux process which makes calls to the ICP driver.
Your SRA must use the DLI or TSI functions to access the ICPs through the
msgmux
process. Your application cannot make calls directly to the ICP device driver functions.
As outlined in Section 2.3, the simpliest way to build an SRA from scratch is to start
with a protocol loopback program, which already contains working code written to
interface with the DLI and TSI. This chapter contains additional information and tips
on interfacing with the DLI API and protocol software. More detailed information on
DLI and TSI can be found in the Freeway Data Link Interface Reference Guide (DC-
900-1385) and the Freeway Transport Subsystem Interface Reference Guide (DC-
900-1386), respectively.
3.1 Files Associated with DLI and TSI
When building an SRA to interface with protocol software, there are always at least three
source files involved in the build process: the SRA source code, the DLI configuration
text file, and the TSI configuration text file. These three files are inputs to the make file
which in turn generates binary versions of each of these files. The binary versions of
these files are then used in the execution of the SRA. To demonstrate the file generation