1. New DCC Status and Plans Jim Rohlf, Eric Hazen, Arno Heister,
Old DCC Update
New DCC Status and Plans
Jim Rohlf,
Eric Hazen, Arno Heister,
Jason St John, Shouxiang Wu
Boston University
E. Hazen

2. Old DCC HTR/DCC communications fixed – zero errors in MonLogger
A few outstanding issues
Anecdotal evidence for 50kHz L1A rate with ZS
Put on back burner until HTR ZS code settles down
Un-tested features... will we every use these?
Calibration triggers – Yes! Need to test
Hardware re-sync – Maybe
CRC calculation on flash firmware – ??
Anything else?
E. Hazen

3. New DCC Overview
Single VME slot; 15 HTR spigots, Ethernet, TTC, TTS on front
Optional P3 rear transition module for selective readout
Xilinx
XC3S200A
FPGA
32MByte
DDR SDRAM
XC3SD1800A
64MByte
TTCrx
UMD
board
LVDS Tx
TTS
TTC
Buffers
VME
VME64x
S-Link
LSC
DAQ Data
TP Out / Readout bits in
Out In
optional rear
transition module
Ethernet
(WizNet)
RJ-45
E. Hazen

4.
E. Hazen

5. Hardware Prototype Status 10 Bare PCBs here; assembled by 12/17
Initial firmware ~ ready
Test Plans
Test at BU test stand until ~ working (1 month?)
Tests at CERN starting ~ 1 February
E. Hazen

6. Software Goal: plug-compatible with old DCC
One crate may contain both old and new DCC!
How to manage this?
Current hcalDCC class becomes a wrapper
DCC1 and DCC2 classes represent old/new boards
All current methods will exist at least as stubs
Strategy
Add new classes to CVS very soon so new releases will have this structure to avoid divergent code
Add functionality to DCC2 class as it is developed
Who will do it?
Phil, Eric, Arno
E. Hazen

7. Software Trouble Spots
Firmware programming – different set of files
Firmware DB will need some updating
Old: Log1/2/3 plus Xilinx New: LRB, Xilinx, VME
Benefits: Everything is reprogrammable, much faster
Jeremy says this is easy to support
MonLogger
Many counters expand from 8 to 32 bits
Some totally new items
Some old items disappear
How to make this compatible?
Initially, just pretend it's an old DCC and accept some trouble
Expert View
Same issues as monlogger
E. Hazen

8. Strategic Decision Plan A
Deploy New DCC as fully and quickly as possible; make one-way changes to fix trouble spots
Plan B
Code full support for a mixed system
Most flexible, but requires extra software effort
We don't have to decide right now, as we need at least basic support for a mixed system.
This requires management input (discuss)
E. Hazen