Difference between revisions of "Busy Box and related"

From ift
Jump to: navigation, search
m (How to run the RCU - DRORC - Busybox setup)
Line 16: Line 16:
 
The BusyBoxes are located in the DAQ counting rom.
 
The BusyBoxes are located in the DAQ counting rom.
  
=== [[How to run the RCU - DRORC - Busybox setup]] ===
+
== BusyBox Hardware tests at UiB ==
 +
In one of our labs at UiB we have a setup for testing new BusyBox firmware in hardware before releasing it. The setup features a full readout chain for one channel of the ALICE TPC.
 +
Components in LAB setup :
 +
* Local Trigger Crate (LTU)
 +
* Readout Control Unit (RCU) with Front End Cards (FEC)
 +
* Local Data Concentrator (LDC) with 3 DAQ ReadOut Receiver Cards (DRORC) and date software.
 +
* BusyBox with 2 FPGAs but only 1U rack.
  
 +
[[How to run the RCU - DRORC - Busybox setup]]
  
 
=== Version history ===
 
=== Version history ===

Revision as of 09:45, 14 October 2009

Overview

Block diagram BusyBox



ALICE is one of four large detectors situated at the collision points in the Large Hadron Collider (LHC) at CERN. The BusyBox is used by four of ALICE’s sub-detectors: Time Projection Chamber (TPC), Photon Spectrometer (PHOS), Forward Multiplicity Detector (FMD) and Electromagnetic Calorimeter (EMCal)

Triggers initiate data readout from ALICE’s sub-detectors and are received by the DCS board via an optical cable interface. The triggers and associated data are routed from the TTCrx ASIC on the DCS board to the BusyBox FPGA(s). Here, the L1a and Serial B line raw data is decoded by the Trigger Receiver firmware module.

Every time a trigger sequence starts the Fee starts buffering data, i.e. a buffer in the Fee is used. A valid trigger sequence ends with an L2a trigger and the event data along with the event ID is sent to the D-RORCs.

The purpose of BusyBox is to let the Central Trigger Processor (CTP) know when the Fee’s buffers are full by asserting a busy signal which prevents further issuing of triggers. The BusyBox and D-RORCs receives a unique event ID from the Fee after an event. After a valid trigger sequence ends the BusyBox will ask the D-RORCs if they have received the same event ID as the BusyBox did. If they do not reply with the same ID it means data has not been shipped from the Fee to the D-RORC, hence, the buffer in the Fee still holds event data.

The Fee buffers can hold 4 or 8 events and the BusyBox keeps track of free buffers. The busy is asserted if the buffers are full.

Interaction with the BusyBox is done through the DCS board, either via Ethernet or UART.

The BusyBoxes are located in the DAQ counting rom.

BusyBox Hardware tests at UiB

In one of our labs at UiB we have a setup for testing new BusyBox firmware in hardware before releasing it. The setup features a full readout chain for one channel of the ALICE TPC. Components in LAB setup :

  • Local Trigger Crate (LTU)
  • Readout Control Unit (RCU) with Front End Cards (FEC)
  • Local Data Concentrator (LDC) with 3 DAQ ReadOut Receiver Cards (DRORC) and date software.
  • BusyBox with 2 FPGAs but only 1U rack.

How to run the RCU - DRORC - Busybox setup

Version history

1.0

  • Magne Munkejord



Download Section

Specification document:
user_guide_busybox.pdf

Source files:
SVN database | CVS database Trigger Receiver


BusyBox firmware:


VHDL source code for Trigger Receiver module:


DCS board firmware for BusyBox:


Related documents for BusyBox:
Busybox User Guide, Rikard Bølgen
Master Thesis, Rikard Bølgen
RCU Trigger Receiver Module
Master Thesis, Magne Munkejord
PhD Thesis, Johan Alme