Page History

...

1. Assemble the test stand according to figures from the "B84 FELIX Test Setup" section:
   1. Plug any of MTP12_CH1_STX cable cables where X = 1, 2, 3 or 4 (labeled as "1", "2", "3" or "4") into the VLDB's RX. We Setup at SLAC use uses X = 1.
   2. Plug mini-HDMI in G0-LinkX on VLDB, where X = 0, 2, 4 or 6. The X value will further be used as "TX" parameter in YARR configs.
   3. Use J77 for mini-HDMI and J93 for mini-DP on the interface board (look into more details in the board's schematics for the reason of the choicewhy). In general, miniMini-HDMI and mini-DP ports standing one against each other another are coupled.
      
      
2. Configure VLDB (this part to be updated).GUI is needed for java):
   1. Supply 5VCC with 1A limit in current to VLDB. With 5V input voltage a VLDB may consume as low as 300mA. Once the VLDB and FELIX configuration processes are done, the board consumes about 450mA.
   2. Use the .jar programmer file and the txt config file.
   3. In the command line run:

      $ java -jar programmerv2.20180725.jar

      (Java GUI will appear) 
   4. Click "import i..." in the top left corner and select the txt config file.
   5. Click "Write GBTX". After the process is done, GUI should look like the attached screenshot
      
      Image Added
      
      
      
3. Update/install the most recent Felix firmware (assuming Vivado Lab is installed, and one has access to GUI):

   1. Plug in a JTAG-USB cable in a correct port on the FLX-712 board.

      SLAC FLX-712 Board	ANL FLX-712 Diagram	Xilinx Dongle: No LED light: PC doesn't see the dongle. Check drivers. Yellow LED: No target. Check JTAG connections. Green LED: Good! Can Proceed.

   2. Get the .bit (directly upload v4.9).
   3. In Vivado Lab detect the target, use the .bit file to configure.
   4. Reboot the PC.
   5. Unplug the MTP12-CH1-TXA cable fiber from the VLDB , and make sure you observe red light coming from the wire, plug it the fiber. Plug in the fiber back to the VLDB's RX. You can use TXA ch1 through ch4 cables.
   6. If there is no GUI and/or Vivado on the Felix server, one may use an external PC to configure the FLX-712 board: keep the board in the server, plug the Xilinx USB dongle into the external PC and run Vivado from there.
   7. Now you should see the RXDATA LED lighting with dim red color.
      
      
      
      

   8. Configure

   VLDB (GUI is needed for java):

   1. VIOs (Virtual Input Output) in the Hardware Manager (Vivado)
      On the left side VIOs appears in the breakdown menu below FPGA.
      Open them one by one, a new tab/window corresponding to each will appear in the central area.
      Click "+" on the top of the window with VIOs.
      A new window will appear. Navigate to your folder with FELIX FW from where a user need to upload "probes" files. Add both (input and output).
      Once the probes appear in a window for a VIO, set "Value" F instead of the default value 0.

      Image Added List of Virtual Inputs and Outputs: hw_vio_N	Image Added List of input and output probes

      
      
      

4. Set up FELIX.
   Depends on the number of FLX cards and their actual locations (PCIe ports) in your PC, option -c / -d in the following commands may vary. In the simplest case of one FLX card follow use same values as below.
   
   1. Run from /home/USER/FELIX/felix-*
5. Supply 5V with 1A limit in current to VLDB. With 5V input voltage a VLDB may consume as low as 300mA. Once the VLDB and Felix configuration process is done, the board consumes about 450mA.
6. Use the .jar programmer file and the txt config file.
7. Run:
   $ java -jar programmerv2.20180725.jar
   Java GUI will appear.
   
8. Click "import i..." in the top left corner and select the txt config file.
Click "Write GBTX". After the process is done, GUI should look like the attached screenshot
Image Removed
Set up FELIX:
1. Run (from /home/itpix/FELIX/felix-04-01-00-stand-alone/x86_64-centos7-gcc8-opt/bin/ in the particular SLAC server):
   $ source "path_to_felix"/source.sh
   
2. Run from
   $
   $ ./ flx-init -c0 
   Run the init commentcommand only oneonce. If you run it twice or more in one session, you need to reboot the computer.
   Get information about your FELIX:
   $ ./ flx-info -c0
   May omit the info command, but it is useful to crocs-check that everything is ok.
3. Check polarity of the channels, and invert if needed:
   $ ./ flx-config -d0 list | grep POLARITY
   $ ./ flx-config -d1 list | grep POLARITY
   TX polarity must be inverted, otherwise readout is not possible.
   If you observe something like "GBT-TXPOLARITY 0x000000000000", run:
   $ ./ flx-config -d1 set GBT-TXPOLARITY=0xffffffffffffffff 
   $ flx-d1 option selects the 1st FLX card. config -d1 set GBT-TXPOLARITY=0xffffffffffffffff 
   
4. If everything was done properly, the other two LEDs - TXRDY and RXRDY - should light up:
   
   
   
   
   
   
9. Configure E-links in elinkconfig:. 
   elinckconfig tool is described in the Felix manual - Section 6.1. 
   The procedure must be done after each system reboot.
   TL;DR:
   1. $ source "path_to_felix"/source.sh (if not done yet)
   2. $ elinkconfig

   3. elinkconfig GUI appears:
      

      Image Modified Initial state of the elinkconfig	Image Modified Target state of the elinkconfig

   4. Click "FULLmode" in the top panel. The left panel will collapse into just one box named "Enable FULLMODE": check the small box, and the entire big box block will turn orange.
   5. Check "TTC-to_Host (63b)" box in the top panel.
   6. Uncheck all the Epaths in the right panel: select "Egroup 0" on the bottom right, click "Disable" 0n on the bottom right, click "Relp 2 All" on the bottom right; uncheck "EC (3f)" by hand.
   7. Click "2-bit" drop down button under the Egroup 0 and select "4-bit".
   8. Check Egroup0-EpathX according to your setup (G0-LinkX mini-HMDI ports on the VLDB).

   9. Click "TH_FanOut..." on the top menu. New window will appear, click "None" and "OK". Repeat same for "FH_FanOut".

      Image Modified "ToHost FanOut" Initial state (same for "FromHost")
      Image Modified "ToHost FanOut" Target state (same for "FromHost")

   10. Click "Repl 2 All" on the top panel.
   11. Save the configuration: click "Generate/Update" on the top panels. new window will appear, click the top "Upload" button and "Close".
       Image Modified
   12. Click "FLX-device" breakdown menu on the top panel, select 1 instead of 0. Repeat same procedure for the device 1. (NOTE: number of devices and their actual address depend on the number of FLX-712 cards used in a server. In case of one card use only 0 and 1.)
       
       
       
10. Check some FELIX registers:
    
    1. ./flx-config -d0 list | grep GBT_GENERAL_CTRL
       If returns other than 0x0000000000000004, run:
       ./flx-config -d0 set GBT_GENERAL_CTRL=0x4
       
    2. ./flx-config -d0 list | grep GBT_ALIGNMENT_DONE
       returns 0x0..1f..0 when an RD53a SCC is connected (one 1 "f" for each SCC).
    3. ./flx-config -d0 list | grep GBT_RXCDR_LOCK
       returns 0x0..1f..0 when an RD53a SCC is connected (one 1 "f" for each SCC). 

Running YARR Scans with FELIX

Create a config file for the SCC itself.

First, copy the default to have your own config file:
$ cp configs/defaults/default_rd53a.json configs/rd53a_0.json

Set 1280 Mbps speed in the config file:
"CdrSelSerClk": 0,

Prepare a connectivity config file. 

First, copy the default example to modify your own config file (from YARR/):
$ cp configs/connectivity/example_rd53a_setup.json configs/connectivity/my_config.json

Set path to your config file for RD53a under "config".

Then, one need to know RX and TX for YARR config file: YARR/configs/connectivity/example_rd53a_setup.json 

A regular config file is shown in left figure below. TX is known from the test stand assembly.

Open two terminal windows. Source the Felix setup.src in both windows. To get the RX file one need to run a simple injection from one terminal window and monitor the process in parallel.

To run the simple injection from in the first terminal follow next steps:

1. Get "CalInjections.sh" and "commands.tgz" from cernbox.
2. Untar the commands.tgz
3. In the CalInjections.sh set correct parameters:
   
   1. -d : logical device, in the simples setup with one FLX card is 0.
   2. -G : physical link, is the X value form GX-LinkY name of the mini-HDMI port used on the VLDB (usually 0).
   3. -g : egroup, refer to the elinkconfig settings, usually 0.
   4. -p : path, same as TX. Can be taken from the TX map on the photo above or from elinkconfig - values are the same. 
4. In total, for a test stand same as described in the manual the parameters should be "-d 0  -G 0  -g 0  -p 6".
5. Run in the terminal:
   $ ./CalInjections.sh
   
   

In the second terminal:

1. Run from /home/USER/FELIX/felix-*/x86_64-centos7-gcc8-opt/ :
   $ fdaq -d0 -t30 -X test1.dat
   where -t sets time to run the scan in seconds, -X sets an output file.
   
2. While the scanning is up, repeat CalInjection in the first window.
3. Once the scanning is done, analyze the data file:
   $ fcheck test1-*.dat (note the test1 is the same as what comes in-X of ./fdaq command).
   Check the first value (G) below G-g-p. RX = G*64. In the example below RX = 8*64 = 512.
   
   Image Added

Run scans with RD53a SCC.

First, reboot the PC. Reboot is required after each time a user run CalInjection.sh . Repeat the routine Felix setup procedure described in sections "FELX Configuration Process - 4. Set up FELIX" and "FELX Configuration Process - 5. Configure E-links in elinkconfig".

Run FELIX core in the terminal window:
$ felixcore -t 1 --data-interface lo
where -t 1 specifies time (1h), and lo (LO) is the default name of the loopback address socket for CentOS7 machines.
Wait until the FELIX core command will return "FelixCore Up and Running..." in the terminal window (last line).

Open the second terminal window, navigate to the YARR SW directory, and run a (digital) scan from there:
$