1. VME Pixel ROD in UW Pixel Lab Final Report
Jimin Kim
University of Washington
Department of Physics

2. Index Motivation of VME Pixel ROD Hardware and Software setup
Established Goals/Approaches and Results
Conclusion
Outlook
Summary

3. Motivation of VME Pixel ROD
Deploy a VME ROD based test system for Pixel DAQ using ATLAS Pixel ROD and IBLROD
Software/Firmware Development and Implementation
ROD/BOC System:
Pixel ROD REV E (from Iowa) + eBOC (from John Joseph) + FEI3 Pixel Module (Maurice)
IBLROD Rev C (LBNL) + BOC (Tobias Flick) + FEI4 module

4. Hardware and Software Setup in UW Pixel Lab
Pixlab 05
CPU : Intel Core 2 Duo E6550/2.33Ghz
Memory : Mb
Linux Version – Scientific Linux CERN 5
Kernel : el5PAE
Installed Software :
TDAQ
IBLDAQ
Single Board Computer
Model : VP-CP1 (Concurrent Technologies)
CPU : Pentium III/ Mhz
Memory : Mb
Linux Version – Scientific Linux CERN 5
Kernel : el5.sbc
VME Slot 1
Second Local Network (Sharing storage)
VME Crate
Pixel ROD
Model : ATLAS ROD for SCT/Pixel Rev E
Manufacturer : University of Wisconsin
VME Slot 10
Control via terminal remote control

5. Hardware Pictures eBOC Pixel ROD Rev E + FEI3 IBLROD Rev C + FEI4A
SBC Interface
Pixel ROD Rev E + FEI3
IBLROD Rev C + FEI4A
VME Crate
VP-CP1 Single Board Computer
eBOC

6. UW VME Pixel ROD Setup
SBC Interface
Pixlab05
VME Crate

7. Established Goals during Winter Quarter
Operation of the USBPix using TDAQ/IBLDAQ Software
This would confirm that we have a working software for various DAQ operations
Establishment of interface between the Single Board Computer and Pixel ROD
Required in order to check the status of the Pixel ROD
Check the current firmware for the ‘Formatter’ , ‘Event Fragment Builder’, ‘Router’ and ‘Controller’
Flash the new firmware into ROD prior to DAQ operation with realistic FEI3 Module

8. Operation of USBPix with TDAQ/IBLDAQ: Approach and result (Summarized)
BASE SETUP
Linux Version – Scientific Linux CERN 5
Kernel: el5PAE
TDAQ
LIBUSB Software
Resolve the inconsistency between source file (zzzz_daq.sh) and TDAQ software
Set USE USBPIX = yes
Modify the paths correctly
Modify the GCC compiler version
Set ./labsite = UWLOCAL
Install IBLDAQ
Set make JOBS = 1 for stable compilation
Confirm the communication
Use
~/daq/USBPix/USBTest/USBTest
To check the communication
Setup the USBPix environment
Follow the instruction in daq/USBPIX
Add 53-usbpix.rules file to /etc/udev/rules.d
Configure the software with local UW Pixel Lab setting
Configure the hostname
Configure database files
(alias, conn, pl and mkdb)
Source mkdb.sh
Start TDAQ Software and Console
Start up TDAQ software with start_infr
Boot – initialize – configure –start
Start Console
Allocate Selection
Blue LED lights from adapter regulators are turned on
communication is successful
Device USBpix ID 14, class 200, FW ver. 15    with adapter card ID 29

9. Establishment of a interface between the Single Board Computer and Pixel ROD: Approach and Result (Summarized)
BASE SETUP for SBC
Model : VP-CP1 (Concurrent Technologies)
CPU : Pentium III/ Mhz
Memory : Mb
Linux Version – Scientific Linux CERN 5
Kernel : el5.sbc
VME Slot 1
BASE SETUP for PIXLAB 05
OS: SLC5
Kernel: el5PAE
TDAQ
IBLDAQ
Share the necessary directories
/home
/tftpboot
/opt
/daq
/usr
Modify the drivers_tdaq script
This script takes care of all the driver files necessary for TDAQ Software
Use Hidden Memory Method for installing CMEM_RCC
export CMEM_PARAMS="debug=1 ram_top=256 ram_size=32“
Also modify the driver, binary and library paths
Compile the Driver Files
Navigate to /cmt under ROSRCDdrivers
Compile the driver files using
cmt make VERBOSE = 1
Make sure to comment out GCC compiler path in zzzz_daq.sh to use default compiler
Modify the Makefile for Driver Files
Modify /daq/slc5/tdaq/tdaq /ROSRCDdrivers/Makefile_32
Disable AFS
Put Static TAG
Specify PCI – VME Mapping
Use
vmeconfig –a vmetab
To load the parameters
And
vmeconfig –i vmetab
to configure the mapping
Apply Hidden Memory configuration for SBC
Add
mem=224M (256M – 32M)
In pxelinux.conf
Install the Driver Files
Reboot the SBC
Check the memory by
cat /proc/iomem
Run drivers_tdaq script by typing
drivers_tdaq start

10. Conclusion
With the procedure described at slide 8, one can successfully establish the communication between the USBPix Readout System and TDAQ /IBLDAQ
Also, by setting up a Second Local Network with Single Board Computer, and following the procedure at slide 9, one can successfully set up an interface between the Pixel ROD and SBC connected via VME crate.
In both procedures, it is very important to acknowledge the base hardware and software environments and establish the consistency with existing instructions by modifying the script and files on each step.

11. Outlook
After successful setup of interface between SBC and ROD, few hardware problems still remain
Measuring the current from the back plate of crate indicates that VME power supply is fine
The possibility leans to the fact that there might be a 3.3V short on the board
Once the problem is fixed, we can flash the firmware for the ROD and establish complete DAQ chain for FEI3 Module
LEDs from the ROD also indicates that ROD isn’t getting any current for 3.3V power (possibly digital circuit)
Crate is not giving any current for its 3.3V power pins

12. Summary
Motivation for the VME Pixel ROD and its hardware/software setup have been described in detail.
The goals and motivation during the Winter quarter have been given.
Systematic approaches that correspond to each of the goals have been summarized with results.
The conclusions from the approaches and results have been given.
Outlook and current facing problems have been described.

13. Thank You, any question? Additional Thanks to Professor Shih-Chieh Hsu
Matthias
Marius
Karolos
Milen
Jarek and Fred