SLAC Teststand Setup

Basic info: 

• ATCA shelf and COB connected to:  rdusr219
• Shelf name, IP: lbne1_0102,192.168.1.254
• RCE SDK path:  /afs/slac.stanford.edu/g/cci/volumes/vol1/sdimages/sdk/current (To get env: source /afs/slac.stanford.edu/g/cci/volumes/vol1/sdimages/sdk/V3.3.0/i86-linux-64/tools/envs-sdk.sh)
• RCE Soft/Firmware path:  /u1/hps/heavy-photon-daq
  • https://github.com/slaclab/heavy-photon-daq/releases/tag/release-4.1-run2016
• The HPS COB is in ATCA slot #2; slot #1 is used by other groups.
• DHPC server config: /u1/dhcp/dnsmasq.local.conf      (restart server with:  sudo service restart dnsmasq)

Start working/developing:

• Connect to the rdusr219 machine

• Setup the general environment: 

  source /u1/hps/setup_env.sh

• Start the conda environment:

  conda activate rogue-hps-dev-ben

• Run the software from this folder.

  cd /u1/hps/server/heavy-photon-daq/software/scripts
  python SvtDaqGui.py --env SLACSM

  The env command line is to tell which network configuration to load. The network configuration that gets loaded is stored in python/hps/constants.py
  Check the FebLinkStatus. In the RCE test, you should see FebFpga[0] and check the Link[0] state. If False, Read the variables again (click Read). If now True, means we are talking to the Feb. After the link is established one can load the configuration. 

• Load the configuration for the system configuration (back end: ATCA (advanced telecommunication computing architecture) and front end (FEB+Hybrid+APVs)) . Click on the HpsSvtDaqRoot tab and load settings

  /u1/hps/daq/heavy-photon-daq/software/config/rce-test.yml

  There is a copy of this configuration file in /u1/hps/server/heavy-photon-daq/software/config/

Configuration files used to configure rogue.
The 2019 CODA (central DAQ software at jLab) configuration files for HPS DAQ are stored on jLab machines at

/usr/clas12/release/1.4.0/parms/trigger/HPS/Run2019/

The general configuration for the DAQ usually ends in .trg, the relevant block for SVT is under the #SVT Config block in one of those files.
This should point to something like ..../svt/svt_config.cnf, where the configuration should be pointed. 

To access this information, one needs to ssh to the clonfarm machines. In particular, clonfarm2 and clonfarm3 are the SVT DAQ machines.

Setup of RCE bootloader for diskless booting: (based on this page)

    ssh (or minicom via usb) to DTM (192.168.2.221)

    minicom bay<bay>.<RCE>              (bay is 0-3 <4 is the DTM> and RCE is 0 or 2 <NOT 1>)

    From rdusr219 (with SDK env): cob_rce_reset 192.168.1.254/2/<bay>/<RCE>

    Interrupt boot sequence by pressing any key in minicom

    Apply the default u-boot environment:

        zynq-uboot> env default -a

        zynq-uboot> setenv modeboot nfsboot

        zynq-uboot> setenv bootdelay 3

        zynq-uboot> saveenv

        zynq-uboot> reset

In order to down/upload to github, set up a tunnel between rhel6-64 and rdusr219.  See Proto-DUNE: How to setup a temporary tunnel for github for a recipe.  

The HPS RCEs boot in "diskless mode" via NFS.  For info about this, see RCE Diskless Node (NFS).

RCE network names:

data DPMs: eth1_test_dpm<1-6>

control DPM: eth1_test_dpm7

DTM: eth1_test_dtm1

TO DO:

Upgrade sw to rogue, requires minor tweaks to fw (Ben)

Update to new config format used by rogue (Cameron and Omar)

Switch to JLab supported TI interface to use event builder supported at JLab and respin RTM (Ryan)

Build sw to take event blocks from data DPM fw and build EVIO blocks for CODA (JJ)

Install CODA at SLAC (Cameron and Omar)

Write EPICS sw (Cameron and Omar)