Control Chip Functionality Overview in Particle Detection Systems
GTP
FIFO
SPYBI+VME
SPYBI+VME
GTP
FIFO
SPYBI+VME
SPYBI+VME
GTP
FIFO
SPYBI+VME
SPYBI+VME
SPYBI+VME
Single input detector Layers
DOUBLE input detector Layers
To 4
LAMBs
From P3
SCTHit0
SCTHit1
SCTHit2
SCTHit3
PixHit0
PixHit1
PixHit2
PixHit3
PixHit4
PixHit5
PixHit6
PixHit7
.
.
.
12 S-links
4 Slinks
4 Slinks
4 Slinks
4 Slinks
16
Slinks
INPut Artix
OUTput Artix
HITA
HITB
AMBSLP
EE signals
Signals
to
communicate
Errors… etc.
VME
signals
Control
Signals
To VME chip
Common to
Input/output
FPGAs
Control chip inputs/outputs
(This is for AMBFTK to be updated)
Control chip Logic:
•
Generate INIT_event
when: (a) EE is received by HIT, and ROAD
chips (2 signals)
•
Receive error
(code & stream info) and
generate an action
(freeze
or stopless-removal) comparing with Severity error
•
For Freeze
: check that the event involved in the error is totally
processed and than generate the freeze to all AMBFTK FPGAs.
Send Freeze upstream.
•
Generate
Operation Code
to the LAMBs
•
FSM?? Molto semplice: INIT_EVENT e quando riceve I 2 EE da HIT
e ROAD, INIT_EVENT di nouvo.
2
1
Init_event
2 EE words received
•
P
a
r
i
t
y
o
r
C
R
C
e
r
r
o
r
–
f
o
r
e
a
c
h
l
i
n
k
(
8
p
i
x
e
l
&
4
S
C
T
)
P
a
r
i
t
y
(
P
A
)
o
r
‘
s
u
m
c
h
e
c
k
’
s
h
o
u
l
d
b
e
m
o
n
i
t
o
r
e
d
.
E
r
r
o
r
d
e
t
e
c
t
i
o
n
s
h
o
u
l
d
b
e
r
e
g
i
s
t
e
r
e
d
i
n
a
8
b
i
t
(
o
r
4
b
i
t
w
o
r
d
)
•
F
I
F
O
O
v
e
r
f
l
o
w
–
e
a
c
h
F
I
F
O
f
u
l
l
f
l
a
g
s
h
o
u
l
d
p
r
o
d
u
c
e
e
r
r
o
r
i
f
s
e
t
.
A
g
a
i
n
8
(
o
r
4
)
b
i
t
w
o
r
d
.
•
I
n
v
a
l
i
d
I
n
p
u
t
d
a
t
a
(
f
o
r
e
x
a
m
p
l
e
i
n
v
a
l
i
d
H
I
T
f
r
o
m
R
O
D
)
?
?
•
L
o
s
t
S
y
n
c
h
r
o
n
i
s
m
(
e
v
e
n
t
t
a
g
s
i
n
d
i
f
f
e
r
e
n
t
s
t
r
e
a
m
s
d
o
n
o
t
m
a
t
c
h
)
–
A
g
a
i
n
8
(
o
r
4
)
b
i
t
w
o
r
d
•
T
r
u
n
c
a
t
e
d
o
u
t
p
u
t
(
f
o
r
e
x
a
m
p
l
e
t
o
o
m
a
n
y
h
i
t
s
i
n
i
n
p
u
t
)
-
A
g
a
i
n
8
(
o
r
4
)
b
i
t
w
o
r
d
.
W
e
c
a
n
c
o
m
m
u
n
i
c
a
t
e
t
o
C
o
n
t
r
o
l
C
h
i
p
t
h
e
e
r
r
o
r
u
s
i
n
g
:
4
b
i
t
s
t
o
i
d
e
n
t
i
f
y
t
h
e
k
i
n
d
o
f
e
r
r
o
r
+
8
(
o
r
4
)
b
i
t
s
t
o
s
a
y
w
h
i
c
h
i
s
t
h
e
f
a
u
l
t
y
s
t
r
e
a
m
.
Errors to be monitored into the INPUT Chips
1.
Error register
– WR = clear; 8 (or 4) x 5 bits
2.
For
each FIFO: flag register
(empty, HFull, Full)–RO (3x 8 or 4)
3.
For each
FSM
: state machine - RO
4.
Output Status (
Hold flags
) – RO (necessario? Esiste HFull)
5.
For each Spy Buffer:
Spy Buffer register
: Pointer, OVFL flag,
status(freeze/spy. WR=clear of Pointer & flag. Status is RO
6.
chip firmware ID? (see Alberto slides)
Firmware and date reg.
7.
Input FiFos: R/W
8.
Input Spy Buffers memories
9.
Timing measurements: each chip has a counter. When
Init_event is received it is started. When all the input EE event
words are received it is stopped. All incoming words are written
in the spy buffer with the counter content.
INPUT VME registers
This detailed content discusses the functionality of the control chip in particle detection systems. It covers topics such as error monitoring, logic generation, input/output communication, and more. The control chip plays a crucial role in handling errors, generating actions based on severity, and ensuring smooth operation of the detection system. It also describes the monitoring of errors, handling of various signals, and the overall logic behind the control chip's operation in these systems.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
DOUBLE input detector Layers HitA0 HitB0 FIFO PixHit0 GTP GTP SPYBI+VME GTP PixHit1 FIFO GTP SPYBI+VME HitA1 HitB1 FIFO PixHit2 GTP GTP SPYBI+VME GTP PixHit3 FIFO GTP SPYBI+VME HitA2 HitB2 PixHit4 FIFO GTP GTP SPYBI+VME GTP PixHit5 FIFO GTP SPYBI+VME FIFO HitA3 HitB3 PixHit6 GTP GTP SPYBI+VME GTP FIFO PixHit7 GTP To 4 LAMBs SPYBI+VME From P3 Single input detector Layers HitA4 HitB4 GTP SCTHit0 FIFO GTP SPYBI+VME GTP GTP SCTHit1 FIFO GTP SPYBI+VME . . . GTP GTP SCTHit2 FIFO GTP SPYBI+VME GTP GTP SCTHit3 FIFO GTP SPYBI+VME GTP
AMBSLP HITA 4 Slinks 4 Slinks INPut Artix 12 S-links HITB 4 Slinks 16 Slinks 4 Slinks OUTput Artix
Control chip inputs/outputs (This is for AMBFTK to be updated) EE signals Signals to communicate Errors etc. Common to Input/output FPGAs VME signals Control Signals To VME chip
Control chip Logic: Generate INIT_event when: (a) EE is received by HIT, and ROAD chips (2 signals) Receive error (code & stream info) and generate an action (freeze or stopless-removal) comparing with Severity error For Freeze: check that the event involved in the error is totally processed and than generate the freeze to all AMBFTK FPGAs. Send Freeze upstream. Generate Operation Code to the LAMBs FSM?? Molto semplice: INIT_EVENT e quando riceve I 2 EE da HIT e ROAD, INIT_EVENT di nouvo. Init_event 1 2 2 EE words received
Errors to be monitored into the INPUT Chips Parity or CRC error for each link (8 pixel & 4 SCT) Parity (PA) or sum check should be monitored. Error detection should be registered in a 8 bit (or 4 bit word) FIFO Overflow each FIFO full flag should produce error if set. Again 8 (or 4) bit word. Invalid Input data (for example invalid HIT from ROD) ?? Lost Synchronism (event tags in different streams do not match) Again 8 (or 4) bit word Truncated output (for example too many hits in input) - Again 8 (or 4) bit word. We can communicate to Control Chip the error using: 4 bits to identify the kind of error + 8 (or 4) bits to say which is the faulty stream.
INPUT VME registers 1. Error register WR = clear; 8 (or 4) x 5 bits 2. For each FIFO: flag register (empty, HFull, Full) RO (3x 8 or 4) 3. For each FSM: state machine - RO 4. Output Status (Hold flags) RO (necessario? Esiste HFull) 5. For each Spy Buffer: Spy Buffer register: Pointer, OVFL flag, status(freeze/spy. WR=clear of Pointer & flag. Status is RO 6. chip firmware ID? (see Alberto slides) Firmware and date reg. 7. Input FiFos: R/W 8. Input Spy Buffers memories 9. Timing measurements: each chip has a counter. When Init_event is received it is started. When all the input EE event words are received it is stopped. All incoming words are written in the spy buffer with the counter content.
