Busy Box and related: Difference between revisions

From ift
No edit summary
No edit summary
Line 35: Line 35:
[http://svn.ift.uib.no/svn/busybox_firmware SVN database]
[http://svn.ift.uib.no/svn/busybox_firmware SVN database]
<br>
<br>


BusyBox firmware:<br>
BusyBox firmware:<br>
Line 45: Line 44:
</li>
</li>
<br>
<br>
DCS board firmware for BusyBox:<br>
[[Electronics_for_the_Time_Projection_Chamber_(TPC)#Download_Section | DCS BusyBox firmware]]
[[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 12:11, 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:
user_guide_busybox.pdf

Source files:
SVN database

BusyBox firmware: