http://www.pa.msu.edu/hep/d0/ftp/tcc/trics_ii/Hub_End_Initialization_Steps.txt -------------------------------------------------------------------------------- List of TCC actions to Initialize the SCL Hub End Crate Rev: Trics V9.3 Rev A (12-Sept-2001) There are two separate contexts =============================== - Explicit request from COOR (or dialog boxes) for SCL Initialize or as an implicit part of a Start_Run message from COOR - By using the "Initialize the SCL Hub End Crate" Button in the "SCL Hub End Crate" Sub-Menu of Trics. The steps below are not supposed to affect data taking and this initialization can thus be used as a way to collect current status information. SCL Hub End Crate Initialization Steps ====================================== As of Trics II V9.3 Rev A 1) Initialize the Trigger Hub Controller (THC) Card 1.a) write to all Set and Reset register to: clear all bits of the board status register except for the "7MHz Enable" bit that needs to be set this includes selecting an IRQ of 0 1.b) read the board status register and verify that step (1.a) was successful. Also show the current controller status as a Hex number. 2) Initialize all channels of the Trigger Status Concentrator (TSC) Cards 2.a) Write zero to the board status register of all 16 TSCs to prevent all VME interrupts. This includes checking that the write was successfull 2.b) Initialize all 128 Channel Interrupt Mask Registers to allow the following status signals to generate interrupts (while interrupts are not enabled at the board level): L1 Error L2 Error Init Ack GS Sync Err Cable Disc Note: this is not necessary the way we want to run when we start listening to interrupts Note: Here we enable all GeoSect while we will eventually want to disable all channels at this time and wait for coor to allocate a geo sect before we enable it to generate interrupts. 2.c) Clear all 128 Channel Interrupt Request Registers This includes checking that the write was successfull and can thus generate error messages if the bits do not reset properly. 2.d) This is where we would (re-)enable interrupts at the TSC board level, but it is NOT done. 3) Dump the status of all 128 Geo Sect channels: Display a set of lists of all GeoSect. This starts with the list of GeoSect Examined (i.e. all) and continues with sub-lists of GeoSects without and with errors flagged for all possible error types. e.g. : I$ GeoSect Examined List: 0:127 I$ GeoSect with No Error: 0:1 3:7 9:31 33:74 76:99 101:127 W$ GeoSect with L1 Error: 2 W$ GeoSect with L2 Error: 8 W$ GeoSect with Init Ack: 32 W$ GeoSect with Sync Err: 75 W$ GeoSect Not Connected: 100 Note: The "Errors" are only displayed as warnings (bright white) and not as errors (red). Not Done: ========= - get ready to Listen to and react to L1/L2 Errors - only listen to interrupts from the GeoSect actually allocated by COOR