Busy Box and related: Difference between revisions
From ift
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
'''1.01 (~may 2009)''' <br> | '''1.01 (~may 2009)''' <br> | ||
<ul> | <ul> | ||
<li> Firmware register added to 0x2015 </li> | <li> Firmware version register added to 0x2015 </li> | ||
<li> Busy Controller module updated to handle orphan messages </li> | <li> Busy Controller module updated to handle orphan messages </li> | ||
</ul> | </ul> | ||
Revision as of 11:18, 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
- Magne Munkejord
1.01 (~may 2009)
- Firmware version register added to 0x2015
- Busy Controller module updated to handle orphan messages
