From mp@hep.ucl.ac.uk Mon Jan 19 19:58:04 1998 Date: Mon, 19 Jan 1998 15:19:46 GMT From: "MARTIN POSTRANECKY,UCL-PHYSICS DEP,HEPP GROUP,GOWER ST,LONDON WC1E 6BT,TEL:(00-44)-[0]171-419 3453,FAX:[0]171-380 7145" To: meh@ax8.hep.ucl.ac.uk, mp@ax8.hep.ucl.ac.uk Subject: more JBL's ROCKY_TRANSPUTERs_TESTs ZUKVS2::userdisk:[UCL.Rocky]Rocky.TXT PigLink and ROCBear : or how to soak test the ROCs 25-Jun-1993 J.B.Lane ================================================== Also known as Links and Rocky, these programs soak test all the transputer links and memories in the network respectively... Links sends large blocks on all links in the network in both directions at the same time and checks the data. Rocky runs Stig's full memory test from ROCTEST on all the transputers in the network. How to run the programs ----------------------- The programs are run from ZUKVS3 using the ISERVER from the occam Toolset. They are independent of the DAQ software which uses the HARNESS. First login to ZUKVS3 and run the command file to set up some symbols etc. : $ @userdisk:[UCL.Rocky]setup ============================ Then just type the name of the program, i.e. : $ Links ======= or $ Rocky ======= Pressing the space bar generates a summary and the program continues running. Any other key causes the message handler to exit after giving the summary. The link switch above the RBOX should be in the normal position. You should use QTA0: (link0) (you can type SHOWLINK). The source is in ZUKVS2::userdisk:[UCL.Rocky] Notes on configuration ---------------------- The crates are numbered : 0 : ZFLT RBOX1 1 - 16 : ZFLT sectors 17 - 32 : FADC sectors 33 : FADC RBOX2 34 : EVB and RBOX1 (FAN in/out, ZEBRA builder, GSLT decision) /cont./ - 2 - Notes on running Links ---------------------- There is a flood of startup messages and then some TIMEOUTs... after a minute press the space bar : there should be a total of 495 Starts and 73 TIMEOUTs corresponding to the 73 unused link connections. Any additional TIMEOUTs indicates a problem. Holding the screen may cause TIMEOUT followed by RECOVER messages because a backlog of messages will cause a link handler to hang. A TIMEOUT on a link which is also used for messages will cause other TIMEOUTs as a backlog of messages causes deadlock to spread. The cure for this has not been implemented yet. Notes on running Rocky ---------------------- There should be a total of 123 Starts corresponding to all the transputers except the Event Builder interface (this one is not operational yet and it is not on a ROC). It takes about 20 minutes to complete a memory test cycle. There should be no CHECK or WRITE errors! Links messages -------------- Start : A message showing that a link handler has started up. Count : A message showing that a link handler is still active. TIMEOUT : An error showing that a link handler has timed out. RECOVER : A message showing that a link handler has recovered from timeout. CHECK : An error showing that a link handler has received bad data. Rocky messages -------------- Start : A message showing that a memory test has started up. Count : A message showing that a memory test is still active. CHECK : An error showing that a memory test has found bad data. WRITE : An error showing that a memory test has found bad data. DUNNO : A message showing that Stig has sent a message I don't understand!