1. Alice EMCAL Meeting, July 2nd 20071 EMCAL global trigger status: STU design progress Olivier BOURRION LPSC, Grenoble

2. Alice EMCAL Meeting, July 2nd 20072 Overview Global trigger scheme reminder Technology issue Validation methodology Status Future steps Summary

3. Alice EMCAL Meeting, July 2nd 20073 Trigger specification : L0 trigger : OR of the 34 L0 calculated by the TRU. L1-gamma trigger: Energy summed over sliding window of 4x4 towers (2x2 fast OR) and compared to a multiplicity corrected threshold. L1-jet trigger : Energy summed over a sliding window of n*n subregions and compared to a multiplicity corrected threshold (a subregion is defined as 8x8 towers) Position of the Summary Trigger Unit in the global trigger scheme STU TRU L0 L1-gamma L1-jet 34 TRU Multiplicity from V0 4 diff pair Ethernet CAT7 cable TRU is clocked by the BC clock forwarded by STU (40.08MHz) TTC link To CTP DDL DCS Put trigger data in the data stream on L2a (via DDL) LVDS links

4. Alice EMCAL Meeting, July 2nd 20074 The technology issue The feasibility of a LVDS link (TRU  STU) working at 2*400.8 Mbs over 15m has to be checked. (see Frascati presentation) The STU design and fabrication on hold  waiting for this validation.

5. Alice EMCAL Meeting, July 2nd 20075 Validation methodology 1.An emitting buffer is loaded via the testing tools 2.A frame transfer is initiated 3.The receiving buffer is read by the testing tools Above steps have to be repeated many times with different packet contents. This scheme is exercising the link as in the final design. It also debugs the serial protocol (local and global trigger side). Trigger OR USB  LVDS USB Slow control LVDS CAT7 LVDS cable 15m Testing tools developed for PHOS by the university of Bergen

6. Alice EMCAL Meeting, July 2nd 20076 Status on this issue 1.Develop the serializer/deserializer VHDL code (with automated frame and character alignment)  Done! 2.Develop and validate the testing tools (hardware and software)  Done! 3.Validate the link speed feasibility with a loopback test  The test scheduling will depend on the availability of the TOR board Reminder: the original calendar was to do this testing before summer 2007

7. Alice EMCAL Meeting, July 2nd 20077 Future steps 1.Design and built the first STU prototype (on hold) 2.Implement a global L1-  (could be validated with 2 TRU). This step could also be done with a TOR. 3.Implement a first version of a L1-jet 4.Implement and test the DDL interface (LPSC is about to be equipped with a Acquisition computer running DATE) 5.Implement and test the DCS interface

8. Alice EMCAL Meeting, July 2nd 20078 Summary LVDS Link prototyping issue (test to be scheduled) Agreement on link protocol (no counter proposal since Frascati)  High speed serializer provided to local trigger (TRU) by LPSC Open questions: –ADC channel numbering versus physical location (to be confirmed or a new map ???) - Region orientation (mirroring between A and C side ???)

9. Alice EMCAL Meeting, July 2nd 20079 SPARES

10. Alice EMCAL Meeting, July 2nd 200710 TRU-STU Serial link specification Reference clock is issued by STU Returning serialized data phase unknown, calibration required at startup 1) Phase alignment: adjust the data input delay, when correctly tuned the words sequence that is read is always the same over several thousand samples. (IDELAY functionality) 2) Character alignment: Once the input delay is properly tuned, the proper frame alignment has to be found out of 6 possibilities (BitSLIP module). data clk data clk BAD GOOD thtsu 2.5ns MSB 100001 000011 000110 001100 011000 110000 LSB 001000 000100 000010 000001 100000 010000 GOOD

11. Alice EMCAL Meeting, July 2nd 200711 EMCAL layout (2/2) The ADC channel number has to be known by STU, in order to compute the triggers For instance, one 4X4 window is channel 5,6,9 and 10 Confirmation of the ADC channel affectation vs geometrical position

12. Alice EMCAL Meeting, July 2nd 200712 36 FEE 3 TRU 2 RCU 32 towers /FEE GTL bus crate 1 FEE (Front End Electronics): - 32 analog inputs - 8 2X2 towers analog sum output to TRU - Readout by RCU 1 RCU (Readout Control Unit): - Readout 18 FEE (1/2 SM=1.5 TRU region) - Readout 1 (or 2) TRU 1 TRU (Trigger Region Unit): - receive Fast OR from 12 FEE (8*48 towers) - digitize 96 FastOR inputs at the machine clock frequency - compute local L0 trigger - provide 5 samples integrated data to STU upon global L0 reception One SuperModule Electronics 1152 towers