Busy Box and related: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
The BusyBoxes are located in the DAQ counting rom. | The BusyBoxes are located in the DAQ counting rom. | ||
=== Version history === | |||
'''1.0 (~april 2004)''' <br> | |||
<ul> | |||
<li> Made based upon TRD DCS FW version 011. </li> | |||
<li> Messagebuffer v1.0 (Torsten Alts orginal version)</li> | |||
<li> Virtex driver for programming RCU FPGA included </li> | |||
</ul> | |||
<br> | |||
=== Download Section === | === Download Section === | ||
[[Electronics_for_the_Time_Projection_Chamber_%28TPC%29#RCU_Trigger_Receiver_Module|RCU Trigger Receiver Module]] | [[Electronics_for_the_Time_Projection_Chamber_%28TPC%29#RCU_Trigger_Receiver_Module|RCU Trigger Receiver Module]] | ||
Revision as of 10:54, 20 May 2009
Overview
Traditionally the Fee in ALICE sub-detectors indicates when its buffers are full and cannot handle further triggers from the CTP. This is either done directly or through the FANIN module to the LTU with a busy signal.
Due to dense cabling, four of the ALICE sub-detectors (TPC, PHOS, FMD and EMCal), utilize a BusyBox to keep track of free buffers in their Fec. The BusyBox asserts the busy signal to the LTU when one or more of these conditions are true:
- Buffers in Fec are full
- Upon receiving a trigger sequence from TTC
- When the TTC sends a global reset to the Fee
The busy signal is de-asserted when one or more FEC buffers are freed
The BusyBoxes are located in the DAQ counting rom.
Version history
1.0 (~april 2004)
- Made based upon TRD DCS FW version 011.
- Messagebuffer v1.0 (Torsten Alts orginal version)
- Virtex driver for programming RCU FPGA included