An Introduction to the CMS EMU DDU

or

Where the data from the Motherboard Goes


Device Dependent Unit (DDU) is the interface point between the on detector components and the Event Builder (EB) acquisition system.

  • As such, our goal is that the DDU will contain a minimal amount of "intelligence" (preferably none), providing a transparent link between the EMU Motherboard (MB) and the DDU Driver software.
  • The DDU interfaces the MB via a high speed optical link (1.2 Gbaud = 1.5 GHz).  That is 150MB/s or 75 MWORD/s
  • The DDU interfaces the EB via a local PCI bus on each front end (DDU carrier) unit (FEU). As such, we have confined ourselves to a 32-bit (DWORD) data width and a 33 MHz DWORD rate, shared among multiple DDUs. That is 132 MB/s or 66 MWORD/s.
  • Although 66-MHz and/or 64-bit PCI are options, we are not considering them at this time due to a lack of available PCI interface drivers compatible with the DDU goals.
  • Limitations from the DDU:

    1. Given the 32-bit width of the PCI bus, it is proposed that data should be organized in 16-bit WORDs, which are grouped into 32-bit words before transfer via PCI.
    2. Because of the unpredictable nature of the data stream, no sufficiently unique marker word(s) can be found to clearly delimit "beginning," "end," "error," or other control type words. We propose that one of the 16 bits be reserved distinguishing control words from 15-bit data words.
    3. Our current cascaded FIFO scheme on the DDU actually allows slightly more than half the PCI bandwidth per DDU, after bursting full speed for about 10 DWORDS.

    From the Anode Point of view:

    At 16-bits, the 96-bit anode "word" requires 6 WORDs.

    Conclusion:

    This slight inconvenience and additional overhead should be considered acceptable given the goals of the EMU system, and indeed the CMS detector, as a whole.

    P. Nylander,nylander@mps.no_.-more-._spam.ohio-state.edu
    23 January 1999