Preliminary setup after power cycle

Firmware is persistent in the FLX-711 and FLX709, so you don't need to reload it after a power cut. You will need to configure and initialise the links, launch the FELIX server application,chek that all is working correctly.

Loading FW

FLX711

ssh np04-srv-017
cd /nfs/sw/felix/firmware
./programFLX.sh 711

FLX712

ssh np04-srv-020
cd /nfs/sw/felix/firmware
./programFLX.sh 712

The script can also be used to load a different version of the FW with respect to the latest.

Initialisation (after WIBs are configured)

FLX711

ssh root@np04-srv-019
./affinity_setup.sh
. jump-to-flx-gcc62.sh
./linkconfig-new.sh 5 0
./init-new.sh

FLX709

ssh root@np04-srv-020
./affinity_setup.sh
. jump-to-flx-gcc62.sh
./linkconfig-new.sh 5 0
./init-new.sh

Launching Felix server applications

From any host:
cd /nfs/sw/Felix/FLXRPC
python start712.py
python start711.sh

After having done this, open a browser and check on http://np04-srv-019.cern.ch:9001 and http://np04-srv-020.cern.ch:9001 that felixcore/protocore are running. Tail the output to check that all 10 links are seeing data (5 on srv-019 and 5 on srv-020).

Troubleshooting

cmem errors when launching applications

The driver did not manage to allocate the block of contiguous memory -> REBOOT

Some links not publishing data

You can try to restart the felixcore/protocore application. If this doesn't work and always the same links are missing data, you may try to initialise the links again, but most probably you will have to reload the fw (with reboot implied).

Other Info

Open a terminal, it's time to configure the FLX links:

ssh -Y root@np04-srv-019
. jump-to-flx-gcc62.sh
./elinkconfig/elinkconfig
You now have a graphical interface open. Click on the ReadCfg button for card 0. Make sure that link 0 is enabled in FULL MODE (and nothing else). Also disable any timeouts and ensure, that the clock is set to local. Click on Repl2All in the Link selection line. (Not in the EGroup selection column.) Upload the configuration. Click on the ReadCfg button for card 1. Do the same procedure, that you did with card 0. Upload the configuration and quit the interface.
  • How to use elinkconfig.:
    elinkhowto.png

Configure the WIB end of the connection now (the present configuration script resets the link, thus the FELIX side needs to be setup after it). The WIB should send idles, so don't issue a startStreamToDAQ command through BUTool yet.

Open another terminal, where you will control the FELIX application.

ssh root@np04-srv-018 #or any other DAQ host.
cd /nfs/sw/felix/FLXRPC/
python init711.py
For additional information what the script does, have a look in it.

Open another terminal, where you will run the FELIX daq application.

ssh root@np04-srv-019
. jump-to-flx.sh
./felixcore -t 1 --num_sources 2 --num_links 6 -o 0 --poll_time 10000 -B fi_verbs
This tool shows data from the 12 available links from the FELIX card with data rates and error checking.

Now you can issue a startStreamToDAQ command to the WIBs. After that, you should see data flowing on the connected links.

Getting ready for running

(OBSOLATE! Correct version TBA.)

Open three terminals on:

  • np04-srv-012 (wib),
  • np04-srv-019 (felix),
  • np04-srv-018 (data receiver).

Warning, important np04-srv-018 and 019 are not yet setup correctly, but you can connect once you are authenticated with your credentials doing ssh -Y root@np04-srv-019 .

The VST WIB shall have firmware version 18-03-01. Instructions to load the firmware can be found in WIBBasicOp.

Setup the VST WIB (from np04-srv-012):

cd /nfs/sw/wib/WIBSoftwareTrunk
source env.sh
cd scripts
BUTool.exe -w 192.168.200.2 -X WIB/config_WIB_preFEMB.script

Now setup FELIX (from np04-srv-019):

cd /nfs/sw/felix/software
source SOURCEME.sh
flx-init
flx-init -d1 // only for FLX-711
flx-info
#taskset -c 0,2,4,6,8,10,12,14 ./felixcore/felixcore -t 4 --num_sources 2  --data_interface p6p2
felixcore -t1 --num_sources 1 -B fi_verbs

Open a browser on http://np04-srv-019:8080 and start monitoring FELIX.

Running

Now activate the WIB dataflow (in the terminal of np04-srv-012):

BUTool.exe -w 192.168.200.2 -X WIB/config_WIB_FELIX_postFEMB.script

Ready to start the DAQ!

QAT

In case the boardreader hosts (017,018) are rebooted, one needs to reload the QAT driver for compression support:
/nfs/sw/sysadmin/QAT/QAT2.0/qatcomp/startdriver.sh

Configuration to be used for the QAT devices can be found under:

/nfs/sw/felix/QAT/Configs.backup
Ensure that the driver configs under /etc , are identical to the ones in the config backup directory.

Debugging

Now check that we are getting good data (e.g. on np04-srv-018):
cd /nfs/sw/felix/software
source SOURCEME.sh
testBW -H 192.168.2.2 -P 12345 -t 64 -s 1 -m 472 -z -q -c 0

The data are published on links 64 and 1088 (-t option) on ports 12345 or similar (the web browser provides the info).

Alternatively, if you wish to stream out data for debugging, you can subscribe to (one or more) links and start receiving data:

source /nfs/sw/felix/software/SOURCEME.sh
netio-cat subscribe --host  192.168.2.2 -t 0 -t 64 -e raw
This command, as an example, connects to the felixcore application running on np04-srv-019, subscribes to links 1 and 2 and dumps the data in raw (i.e. hexdump) format. netio-cat -h provides a full list of options.

Working document .

-- GiovannaLehmannMiotto - 2018-02-13 -- RolandSipos - 2018-07-13

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng elinkhowto.png r2 r1 manage 93.5 K 2018-07-14 - 12:08 RolandSipos Elinkconfig howto.
Edit | Attach | Watch | Print version | History: r24 | r22 < r21 < r20 < r19 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r20 - 2018-10-09 - GiovannaLehmannMiotto
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CENF All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback