The transputerlink test tests one particular link in the network by booting the two transputers on both ends of the link. One transputer is connected to the iserver reporting the results of the test and initiating the link communication, the other transputer echos received datablocks, so that data transfer is bidirectional (and simultaneous). Data is checked by means of Cyclic Redundancy Check (CRC). The blocksize used is 64 kByte. The link connection under test between the two transputers might run through one or two linkswitch chips. The linkswitch is set automatically before the testprogram is booted on the transputers.
Here is how a link test is started (in directory /zeus/transputer/tools/caldaq_linktest): ltest -c tpid1 tpid2 [no_of_mbytes]
with
c = f or b or r,
signifying whether the link to test is part of the FCAL, BCAL or RCAL transputer network, respectively, and with
no_of_bytes > 0
an optional parameter that is the number of MBytes to transfer in the test (bidirectional, default is 5 MByte), and with
tpid1 = roi (i=1,2,316)
and
tpid2 = tr
= roci (i=0,1,2,3)
= mon
or
tpid1 = tri (i=1,2,3
16)
and
tpid2 = l2
or
tpid1 = l2j (j=0,1
j
)
and
tpid2 = l3
in which
roi is the READOUT transputer in crate i and tr is the TRIGGER (LAYER1) transputer in the same crate,
roci is READOUT COLLECT transputer link i and
mon is the corresponding (to roi) MONITOR transputer and link,
tri is the TRIGGER (LAYER1) transputer in crate i and l2 the connected LAYER2 transputer,
l3 is the LAYER3 or LAYER3MON transputer,
j =4 in case of FCAL or BCAL and RCAL TRIGGER
transputers don't have links to LAYER2 transputers.
When testing a link of a READOUT transputer, its 'monitor'-link is used when testing the link to mon and its 'readout'-link is used in other cases.
(The sources for configuring/preparing the transputer network for a link test are in /zeus/transputer/tools/caldaq_linktest/link_test_prep and the sources of the testprogram in /zeus/transputer/tools/caldaq_linktest/link_test.)