LAV firmware status
Francesco Gonnella
Mauro Raggi
10th October 2012
TDAQ Working Group Meeting
LAV trigger generator
 High and Low threshold crossing association
and slewing correction






Constant offset
Event reconstruction
High and Low threshold crossing association and slewing correction
Recognition of the end of the 6.4 μs time frame (EoF)
Output data (corrected times and EoF) written on a 32-bit fifo
Error on FIFO L/H full
End-of-Frame signal
to TRIG FIFO
From OBTRIG FIFO
64 blocks
(128 FIFOs)
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
2
LAV trigger generator inside PP
 Input data is read from the OBTRIG fifo;
 Data is elaborated from TRIGGEN module
 Output data is written to TRIG fifo
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
3
LAV-PP output data format
 Data sent from each PP (TRIG fifo) to SL is formatted as following:

Data is composed of 2x 32-bit words, the first starting with “10”
31 ”10” 30
29 Block 24
23 Error
22 block error 20
19 Risetime 12
11 – 8
7 Time(39:32) 0
31 Time(31:0) 0
 The End of Frame is 1 word starting with “11”
31 ”11” 30
29 don’t care 0
 For example:
0X81000A00
0X0008FFB7
0X80000500
0X0008FFFA
0XFFFFFFFF
0X81000A00
0X0009FFB8
0X80000500
0X0009FFFB
0X81000A00
0X000AFFBA
0X80000500
0X000AFFFD
0XFFFFFFFF
0X81000A00
0X000BFFBB
0XFFFFFFFF
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
4
Test with fake data on TDSPY
 We programmed the
four PP-FPGAs with LAV
specific firmware
 Fake data was
written into the
OB via TDSPY
 The output data
was read out
from the TRIG fifo
 Data matched
the Modelsim
simulations
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
5
Test with data from LAV FEE
Problem with
TDC noise
under study
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
6
Failure in 1/4 DDR-test
The LAV trigger generator module takes a large amount of
resources, so we want to be sure that its integration does not
compromise the proper functioning of the whole firmware.
 We tried a DDR test on the LAV PP-firmware. It resulted in error in
PP0 but was successful in PP1, PP2, and PP3
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
7
LAV SL firmware
 Event time merging and primitive generation

Merge event times from the 4 PPs

Group together events within a programmable time cluster (5 ns)

Evaluate the average of the clusters, obtaining primitive times

Sort primitive times

Produce trigger primitives according to MTP assembler format

Error on primitive lost
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
8
LAV primitive-merger integration on
SL
We are ready to integrate LAV SL-firmware
in order to test it on the TEL62.
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
9
Conclusions
 Status:

We have a working version of the PP firmware performing High and
Low threshold-crossing association and slewing correction

PP LAV-specific firmware has been successfully integrated into
common firmware

Tests have been performed successfully on TEL62

We have a working version of the SL firmware ready to be
integrated


Works at 160 MHz frequency with reasonable (10%) resource
utilization
Can handle up to 32 trigger primitives
with a fixed latency of about 1.3 μs
 Things to do:

Integrate LAV firmware into SL common firmware

Test the complete LAV-specific firmware (PP and SL)
Francesco Gonnella - I.N.F.N. - Laboratori Nazionali di Frascati - Italy
10 October 2012
10
Thank you for your attention
10 October 2012
11