Busy Box and related: Difference between revisions

From ift
No edit summary
No edit summary
Line 29: Line 29:
=== Download Section ===
=== Download Section ===
Specification document:<br>
Specification document:<br>
[http://www.ift.uib.no/~alme/wiki/RCU_comm_specification_v2.6x.pdf RCU_comm_specification_v2.6x.pdf]<br>
[[Media:User_guide_busybox.pdf‎]]
[http://www.ift.uib.no/~alme/wiki/RCU_comm_specification_v2.8x.pdf RCU_comm_specification_v2.8x.pdf]
<br>
<br>


Source files:
Source files:
[http://web.ift.uib.no/kjekscgi-bin/viewcvs.cgi/vhdlcvs/messagebuffer/ CVS database]
[http://svn.ift.uib.no/svn/busybox_firmware SVN database]
<br><br>
<br><br>
<ul>
<ul>

Revision as of 11:32, 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:

  1. Buffers in Fec are full
  2. Upon receiving a trigger sequence from TTC
  3. 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


Download Section

Specification document:
Media:User_guide_busybox.pdf‎

Source files: SVN database