1 / 20

SRP: Integration

SRP: Integration. Irakli MANDJAVIDZE DAPNIA, CEA Saclay, 91191 Gif-sur-Yvette, France. Overview. Part I TCC-DCC components Part II Tests Part III Exceptions Part IV Formats. Part I: TCC-DCC Components. SFP cages and connectors 240 sets ordered in March SFP transceivers

muncel
Download Presentation

SRP: Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SRP: Integration Irakli MANDJAVIDZE DAPNIA, CEA Saclay,91191 Gif-sur-Yvette, France Irakli.MANDJAVIDZE@cea.fr

  2. Overview • Part I • TCC-DCC components • Part II • Tests • Part III • Exceptions • Part IV • Formats Irakli.MANDJAVIDZE@cea.fr

  3. Part I: TCC-DCC Components • SFP cages and connectors • 240 sets ordered in March • SFP transceivers • Offer received • Do we buy all 200 pieces now? • Or 100 in 2005 and 100 in 2006? • Simplex LC-LC Cables • Run between SFP and TCC-DCC racks • Probably must be put in place during 2005 • Must satisfy CERN safety rules • Offer received, will be ordered on Monday • Length? Irakli.MANDJAVIDZE@cea.fr

  4. Part II: Tests • Principles • TCC – AB tests • AB – DCC tests • TCC – AB – DCC tests Irakli.MANDJAVIDZE@cea.fr

  5. Principles • Running with pre-calculated data sets • Coherent sets of TT flags, SR flags • Raw data, SR flags and selected data • Initially the data need not be issued from physics simulations • Preloading TCCs, DCCs and ABs with the data • In dedicated or existing FIFOs • TCS system • To distribute LHC clock and TCS commands • To generate L1 Accepts • To receive sTTS • CCS will be needed for tests with > 1 TCCs and/or DCCs Irakli.MANDJAVIDZE@cea.fr

  6. TCC – AB Standalone Tests • TCC is preloaded with TT flags • AB Tester is preloaded with expected SR flags • AB Tester substitutes DCC • TCS system generates L1 Triggers • TCC sends TT flags to AB at L1 • AB produces SR flags and sends to AB Tester • AB Tester verifies received SR flags • Tests can be done at LLR • A TCS system is needed TCC TCS AB AB Tester Irakli.MANDJAVIDZE@cea.fr

  7. AB - DCC Standalone Tests • AB Tester is preloaded with TT flags • DCC front-end FIFO is preloaded with raw data • AB Tester substitutes TCC • TCS system generates L1 Triggers • AB Tester sends TT flags to AB at L1 • AB produces SR flags and sends to DCC • DCC filters front-end data • Selected data checked against expected data • Tests to be done at CERN • Possibility to work w/o AB Tester • With TT flags directly loaded in AB AB Tester TCS AB DCC Irakli.MANDJAVIDZE@cea.fr

  8. TCC - AB - DCC Standalone Tests • TCC is preloaded with TT flags • DCC front-end FIFO is preloaded with corresponding data • Operation as expected in final system • TCS system generates L1 Triggers • AB Tester sends TT flags to AB at L1 • AB produces SR flags and sends to DCC • DCC filters front-end data • Selected data checked against expected data • Larger scale tests • With several TCCs and DCCs and single AB • Up to a compete ODE crate with 3 CCS-TCC-DCC unit TCC TCS AB DCC Irakli.MANDJAVIDZE@cea.fr

  9. Part III: Exceptions • Exception types • Reminder on Data to be collected and its format • Forcing SR flags • Exception handling Irakli.MANDJAVIDZE@cea.fr

  10. Exception Types • Spontaneously missing data • Hardware failures • Out of order TCCs or ABs • Transmission errors • CRC errors • Low level protocol errors, e.g. missed SoF, EoF... • High level protocol errors • Parity errors • Mismatch of locally calculated and received BxId and EvId • Permanently missing data • Inactive TCCs or ABs • Nonexistent partitions, e.g. endcaps • Partially equipped partitions Irakli.MANDJAVIDZE@cea.fr

  11. Example of a barrel AB When data is missing SR flags must be forced Data to be Collected in an AB Legend TCC data (SM) Neib. AB data Missing data Area withforced SRF Irakli.MANDJAVIDZE@cea.fr

  12. Super module data Data Format 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Hop 1 1 1 0 0 0 0 TCC / AB Id Hop 1 0 1 BxId Header Hop 1 1 0 EvId Hop 0 TTF/SRF 3 TTF/SRF 2 TTF/SRF 1 TTF/SRF 0 Data Hop 0 - - - - Hop 0 TTF/SRF 67 TTF/SRF 66 TTF/SRF 65 TTF/SRF 64 Trailer Hop 1 Vertical even parity Irakli.MANDJAVIDZE@cea.fr

  13. In the reserved bit of flags? fixes format and excludes addition of information in future Or in a reserved bit of data words? e.g. “00” – all good, “01” – at least 1 forced, “11” – all forced Leaves possibility to extend SR flags in future How to notify forced SR flags SR Flag 2 1 - 0 N/F Action 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Hop 0 N/F N/F TTF/SRF 3 TTF/SRF 2 TTF/SRF 1 TTF/SRF 0 Irakli.MANDJAVIDZE@cea.fr

  14. Exception handling • Hardware failures • detected by time-out • (also signaled to Run Control and TCS) • Transmission errors • detected by receiver, e.g. CRC error • or detected by time-out • Permanently missing data • Mask inactive TCCs or ABs at configuration • SR flags calculated in ABs and delivered to DCCs • Forced flags marked Irakli.MANDJAVIDZE@cea.fr

  15. How to Force SR Flags • Load substitution TT flags in ABs • Flags for masked TCCs and ABs may differ from all others • Use substitution flags for exceptions • Same strategy to exchange TT flags among ABs Local Bus Substitution TT flags DCC output Algorithm Logic Sender TCC input Receiver Error ≥1 Time-out Local Bus Config Mask Irakli.MANDJAVIDZE@cea.fr

  16. Exception handling (cont.) • What to do with mismatch of local and received EvId & BxId? • When has sTTS = Out_Of_Sync to be raised? • As soon as? • After Nth consecutive occurrence? • Does SRP nevertheless calculate and deliver SR flags? • What EvId & BxId to be used in SRF data packet? • Does SRP only notify DCCs of such an exception? • What is the format? Irakli.MANDJAVIDZE@cea.fr

  17. Part IV: Data Format • TT Flags • SR Flags: Actions or RU Classification Irakli.MANDJAVIDZE@cea.fr

  18. Format of TT Flags TT Flag Meaning • May exceptions prevent TCC from producing TT flags? • Will TCC send TT flags to AB in any case? • If a TT flag cannot be produced • Will TCC use the “Forbidden” value as error indication? • Will TCC force a valid value and mark it as forced (e.g. in bit 2)? 2 1 0 RSVD0 0 0 Bellow low threshold 0 1 Above low threshold 1 0 Forbidden 1 1 Above high threshold Irakli.MANDJAVIDZE@cea.fr

  19. Format of SR Flags: Actions SR Flag Meaning • ABs produce SR actions • Do not know what thresholds are set up in DCCs • DCCs either follow SRP instructions or ignore them • Programmable • SR algorithm changes: SRP and DCCs must be reconfigured • Coherence of SRP and DCC parameters 2 1 0 N/F 0 0 Suppress 0 1 Read with ZS 1 1 0 Read with ZS 2 1 1 Read all Irakli.MANDJAVIDZE@cea.fr

  20. Format of SR Flags: RU classifications SR Flag Meaning • ABs classify Read-out Units • Does not have to know what actions will be taken in DCCs • DCCs are programmed with actions and thresholds • Coherence between actions and thresholds • SR algorithm changes: only DCCs must be reconfigured • ABs remain unchainged 2 1 0 N/F 0 0 Suppressed RU 0 1 Single RU 1 0 Neighbor RU 1 1 Central RU Irakli.MANDJAVIDZE@cea.fr

More Related