search

DUNE-DAQ / timinglibs

0 stars 1 forks source link

Feature/inter session comm conn service #84

Closed strilov closed 1 year ago

eflumerf commented 1 year ago

I was able to run this on np04, at least to the point of seeing the HSI app from the DAQ session connecting to the thi app in the timing session. I wasn't able to run the daq session, as the HSI app crashed at start, apparently due to not being able to connect to hardware. 

2023-Feb-28 18:31:14,033 ERROR [virtual void dunedaq::hsilibs::HSIReadout::do_hsievent_work(std::atomic<bool>&) at /nfs/home/eflumerf/dune-daq-base/v3.3.0/sourcecode/hsilibs/plugins/HSIReadout.cpp:177] HSI endpoint not ready. Current state: 0x5
ESC[0;31m28-02-23 18:31:14.034834 [140461438252800] ERROR - Bad response code (0x6 = 'bus timeout on read') received for Incrementing read at base address 0x102c (nodes "stat", "stat.buf_err", "stat.buf_warn" under "TOP.endpoint0.hsi.csr").  URI: "chtcp-2.0://np04-srv-012.cern.ch:10203?target=10.73.137.84:50001". Sent/received headers: 0x2003010f / 0x20030006 (transaction 1/1 bytes into IPbus payload)ESC[0m
bieryAtFnal commented 1 year ago

I wonder if daq-systemtest/integtest/iceberg_real_hsi_test.py is a possible way to test this. I recall that Stoyan updated the TLU/HSI firmware at ICEBERG recently, so the hardware might be in a reasonable state. If you run this integtest without starting the timing DAQ session, it will print out suggested commands for running that.