Online on TCC (but between stores)

• System Complex, Pipelined, too fast to watch all events
• Very important to test and diagnose in situ
• Break down into several aspects/levels/stages
• cf. www.pa.msu.edu/hep/d0/ftp/tcc/testing/testing_strategy.html

1. IO Test
• configure FPGA
• read/write/verify
• ingest set of registers

 
2. Connectivity Test
• special firmware
• traces and cables
• write to driving end/read receiving end
• ingest an ascii description of all connections
• cf. www.pa.msu.edu/hep/d0/ftp/tcc/testing/connectivity_test.txt

 
3. Full Speed Single Chance Test and Exercizer
• whole system clocked at speed
• change inputs for only one time slice
• capture (via monitoring mechanism) that one event
• change only a few things between loops
• arrange to still have a lot of changes everywhere
• check all results, scalers, readout at every loop

 
4. Calibration
• much higher bandwidth from TCC than L2 or L3 could ever do
• e.g. find or tune Trigger Tower pedestals
  
  

• Simulator
• Programmable with the same syntax as hardware
• Packing and unpacking of raw data
• Input from MC or real Cal Data or real L1Cal Data
• Shared with system test: Simulate any lookup, correction, etc.

 
• Verifier
• Verify that Hardware and Simulator Match