1. DAQ Link integration update A Navarro Tobar*, JM Cela Ruiz 10/2/2015

2. Introduction: data flow and FW modules 29/2/2015A. Navarro (Ciemat) TM7 AMC13 LHC clock TTC data TTS DAQ (FCLKA) (Port #3 ←) (Port #1 ↔) DAQ Link TTC Event Builder

3. FW overview Event builder: DT-specific, entirely up to us TTC: low rate link, sampled in general I/O pins. Simple decoder provided by BU. DAQ link (includes TTS): high speed (5 Gbps) bi- directional link (return link is used for link control and monitoring), uses MultiGigabit Transceivers (MGT). Boston University (BU) provides a FW module that takes care of the link layer, but physical layer, being device-dependent, needs tuning. TM7 communicates with MP7 and both are Virtex-7 devices. A portion of MP7’s code is suitable for use in TM7. 9/2/2015A. Navarro (Ciemat)3

4. TTC BU provides a simple TTC decoder (v1.1) with automatic clock-data alignment (v1.0 w/o alignment) Prior to release of v1.1, we programmed a TTC module with automatic phase alignment and somewhat more elaborated signal outputs and control/status registers. MP7 has its own TTC module (with externally- programmable phase alignment) and other features. – It (obviously) fits perfectly with the data flow architecture between different MP7 FW modules that we’re using in TM7. – Code seems to be clean and maintained, and keeping the register and addresses map and may allow us to also re-use part of MP7’s SW. – It probably makes sense to stick to this FW module 9/2/2015A. Navarro (Ciemat)4

5. DAQ link (I) BU provides a module for different platforms (Kintex7, Virtex6, Virtex7) that manages physical and link layer, offering a tidy, high- level interface for the AMC developer to use. But: they don’t own a V7 board, so the code for this HW is obsolete and the user is entitled to use the K7 link layer code and do the physical layer. Currently, making the link work involves creating an IP core for MGT management (no instructions provided although most part can be reproduced from the obsolete SVN V7 branch), removing the core, re-adding some of the generated vhd’s and manually modifying one of them. – Finding this recipe, actually, was the hardest part since it is not documented and involved a lot of trial and error with the integration of the IP core We are working remotely: we are in Madrid, the HW at CERN (mainly uTCA crate at P5). It has some drawbacks but overall it’s working satisfactorily. 9/2/2015A. Navarro (Ciemat)5

6. DAQ link (II) We have demonstrated transmission between TM7 and AMC13 in a “clean” project (i.e. only simple TTC module + DAQ link + dummy event builder). – ie we build an event with pre-fixed contents, send it through the backplane link and verify reception at AMC13 by reading it from the RAM through IPbus. We have demonstrated transmission co-existing with other MGT- using modules (IPbus, optical tx). – Since the clocks are shared between several MGTs, and, in particular IPbus and DAQ link share the 125 MHz, some adaptation was needed. MP7 developers are working their own solution; we might want to adapt parts of their code in the future to take advantage of their SW and their validation procedure (from AMC to AMC13 to FedKit). At present we are working in finalizing the event builder FW to complete the full Data Acquisition chain. 9/2/2015A. Navarro (Ciemat)6