Missing events in SDSP histogramming

• Minumum setup to trigger lost event
  • Only enable 3 moudles in ROD_C0_S20. These three modules are distributed to 3 PixelModuleGroup

    L2_B99_S1_A6- M2A, M4A
    L2_B99_S2_C6- M3C
          

  • Only trigger 6 events. Only choose 2 steps out of total 32 mask stages.
  • The L1Latency is set to 244 and CAL to L1 delay = 240. TRIGGER STREAM ORIGINAL is:

    LENGTH = 392 bits => 13 words effectively
      00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000001011001000000000000000000 0x01640000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000000000 0x00000000
    00000000000000000000000000011101 0x0000001d
    00000000000000000000000000000000 0x00000000
          

  • More details of the scan can be found in the DSPBuffer log files
• SLink dump - filar_S9850_digital.dump
  • There are no event header 0xb0f and tailer 0xe0f words in the SLink dump.
  • There are no missing events in the raw data.

    [ros01] ~ > filar_slink_dst -o 1 -f /home/schsu/Data/ToothPix/filar_S9850_digital.dump
    Wrong data: received L1id (0) is not previous (11) + 1
    Closing S-link ...
    
    
    ----------Test Statistics-----------
     Total # packets transferred = 24
     Total # corrupted packets   = 1
                wrong size       = 0
                wrong L1id       = 1
    ------------------------------------
       

• StdDump
  • StdDump.cxx

      long unsigned int dspStart[4]    = {0x400000  , 0x402000, 0x402400, 0x404400 };
      string filename[4]                      = {"Formatter", "Efb"       , "Router"   , "Rcf"};
          

  • Before scan
  • After scan
• FGPA version

  [pixrcc04] ~/daq/RodDaq/RodUtils > ./GetRodStatus -s20
  New BOC
  
  First doing initialize()
  RodModule::initialize
  reading MEMORYMAP_REG: 80000004 start 29f0278
   nTextBuffers: 2
   nTextBufferSlots: 5
  RodModule TextBuffer 0 size: 2000
  RodModule TextBuffer 1 size: 800
  RodModule TextBuffer 2 size: 2000
  RodModule TextBuffer 3 size: 800
  RodModule TextBuffer 4 size: 2000
  RodModule TextBuffer 5 size: 800
  RodModule TextBuffer 6 size: 2000
  RodModule TextBuffer 7 size: 800
  RodModule TextBuffer 8 size: 2000
  RodModule TextBuffer 9 size: 800
  RodModule::initialized finished
  Secondly, make the snapshot of the status
  Done.
  We've got a live one!
  Print the status:
  
  ================== R O D  S T A T U S ====================
   Slot                  : 14
   Base adress           : 0x14000000
   Byte order OK         : Yes
   Serial Number         : 820
   ROD rev.              : f
   MDSP program rev.     : c0ffee
   FMT program rev.      : 8f21
   EFB program rev.      : 8f29
   RTR program rev.      : 8f21
   RCF program rev.      : f33
   Number of slave DSPs  : 4
  
   Primitive state       : Idle
  ==========================================================
  
  Deleting VmeInterface...
    Releasing DMA buffer
     

• Scan Results
  • DSPBuffer log files
  • histogramming from SDSP shows we lost one event in the second mask stage step

Work preparation

• Our works are highly dependent on TDAQ releases, DAQ versions, DSP image versions, Configuration DB tag. Write down the combination of each scan is critical for debug activities
• Enviroment

 - login atlpix01 as pixeldaqdev.
   You will be direct to the gateway control5. It's where we do the work
 - Check which daq release you are using
   ls -l daq -> DAQ-VERSIONS/PixelDAQNdsp-1-0-T1
   We normally use soft-link to select different DAQ release

• Load master image to flash memory on ROD

   The images are collected in directory. 
 - Check which SBC the RODS are located. For example, ROD12 is on crate1 (pixrcc04)
 - login to pixrcc04 
 - source /daq/slc4/zzzz_daq_190.csh
 - cd ~/daq/RodDaq/RodUtils/
 - ./MdspFlashLoad -f
    Enter valid ROD slot number [5-12:14-21]  (decimal):12
    Enter binary file name, including extension (q to quit):/home/schsu/DSP/jdopke_master_20080708.bin   
 - ./RodReset -s12
 - Check the version of master image. If the FPGA Version are all fff. Something is wrong.  
   /home/schsu/scripts/RodCheckVerDsp.sh 12
+++++++++++++ ROD(12)   S/N 213
**** PRM Version (12) = f17
**** RCF Version (12) = f2e  PIXEL
**** FMT Version (12) = f21p

**** EFB Version (12) = f29  PIXEL
+++++++++ WRONG EFB Firmware (f22) +++++++++
**** RTR Version (12) = f1f  PIXEL
**** new DSP Version

• start-up partition

 - in Control5, setup environment variable
   source /daq/slc4/zzzz_daq_190.csh
 - Make sure Configuration Tag is selected correctly. 
   cd ~/daq/Applications/Pixel/PixRCD/PixRCD-00-01-00/PixRCDConfiguration/SR1/partitions
   ls -l PixelEnv.data.xml -> PixelEnv.data.xml.BOC
   "CoralDB id tag" "CT"
For run control: 
"CONNECTIVITY_RUN_TAG_C" "TOOTHPIX-2008-C2"
"CONNECTIVITY_RUN_TAG_CF" "TOOTHPIX-BOC"</attr>
"CONNECTIVITY_RUN_TAG_MOD_CF" "TOOTHPIX-BOC"</attr>
Pix configuration:
"CONNECTIVITY_TAG_C""TOOTHPIX-2008-C2"</attr>
"CONNECTIVITY_TAG_CF""TOOTHPIX-BOC"</attr>
"CONNECTIVITY_TAG_MOD_CF""TOOTHPIX-BOC"</attr>
 - sartup partiton
   ~/startup_infr
 - click boot

• Scan with Calibration Console

- Start Console
   cd daq/Applications/Pixel/CalibrationConsole/Console
   Console
   
   During the startup, you can see one of the message contains the configuration:
   create new Connectivity for "CT:TOOTHPIX-2008-C2;TOOTHPIX-BOC.
   
- Command Tool
   wait for 001 Initalise RODs Done.
   If it's not, check if there's error message in the TDAQ panel. Follow the hints to clear problems.
   Normally, it could means the Configuration tag or master image is wrong.
  - Right Click 
    Choose preset name "DIGITAL_TEST"
    Save file to /daq/results/NewDspDebug/DIGITAL_TEST/
    Base tag with revision time "Tue Jul 29 13:10:50 2008"
    Configure path name
    Click OK to start the scan
- Module List
  - choos scan number, e.g. S008-137
  - Choose PP0, e.g. L0_B12_S1_C7
    right click->Show Histogram ->OCCUPANCY
  - Save the figures as png files

• Backup log file

There are two types of log files we want to preserve:
- DSPBuffer
   cd /daq/logs/PixelInfr_pixeldaqdev/DSPBuffers
   cp -rp ROD_C1_S12  /daq/results/NewDspDebug/DIGITAL_TEST/ROD_C1_S12_Digital_S8137
   You can check the master and slave DSP versions from infor.out:
File link time 2008/07/08 @ 14:40   router version = 0x00008f1f slave loading complete
 File link time 2008/07/08 @ 17:02   a slave is born

- ActionsServer 
   cd /daq/logs/PixelInfr_pixeldaqdev/
   ls -ltr |grep ActionsServer |tail -10
   cp -p   Appl_PixelActionsServer-Crate1_pixrcc03.pixel.cern.ch_1218260731.out /daq/results/NewDspDebug/DIGITAL_TEST/ROD_C1_S12_Digital_S8137/

• A: CT, TOOTHPIX-2008-C2, TOOTHPIX-BOC, master 0708, slave 0708
• B: SR1, TOOTHPIX-V3, NEWDSP-SCHSU, TOOTHPIX-DEFAULT, master 0708, slave 0708
• C: SR1, TOOTHPIX-V3, NEWDSP-SCHSU, TOOTHPIX-DEFAULT, master 0731, slave 0731

ROD12 L0_B12_S1_C7