[subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version
Weber, Guenter Dr.
g.weber at hi-jena.gsi.de
Wed Jan 10 10:30:35 CET 2024
Hi folks,
the old "./find_firmware.pl" was working. This is the output:
a1729cda ../ver/rimfaxe0_trlo/rfx0_defs.h
0866c243 ../ver/rimfaxe1_trlo/rfx1_defs.h
5e8f5ef4 ../ver/tridi1_trlo/tridi_defs.h
6e4ba1a9 ../ver/vulom4_trlo/trlo_defs.h
68f8955e ../ver/vulom4_trlo_all_in/trlo_all_in_defs.h
af33ed35 ../ver/vulom4_trlo_big/trlo_big_defs.h
1409285e ../ver/vulom4b_trlo/trlo_defs.h
d374466d ../fw/tridi1_trlo/tridi_defs.h
d96ffc88 ../fw/vulom4_trlo/trlo_defs.h
5b298165 ../fw/vulom4_trlo_all_in/trlo_all_in_defs.h
6f28c0f8 ../fw/vulom4_trlo_big/trlo_big_defs.h
fa5020ea ../fw/vulom4_trlo_led/trlo_defs.h
426cb99c ../fw/vulom4b_trlo/trlo_defs.h
MKDIR fw_a1729cda_rfx0 # ../ver/rimfaxe0_trlo/rfx0_defs.h
SYMLINK fw_a1729cda_rfx0/rfx0_defs.h -> ../../ver/rimfaxe0_trlo/rfx0_defs.h
MKDIR fw_0866c243_rfx1 # ../ver/rimfaxe1_trlo/rfx1_defs.h
SYMLINK fw_0866c243_rfx1/rfx1_defs.h -> ../../ver/rimfaxe1_trlo/rfx1_defs.h
MKDIR fw_5e8f5ef4_tridi # ../ver/tridi1_trlo/tridi_defs.h
SYMLINK fw_5e8f5ef4_tridi/tridi_defs.h -> ../../ver/tridi1_trlo/tridi_defs.h
MKDIR fw_6e4ba1a9_trlo # ../ver/vulom4_trlo/trlo_defs.h
SYMLINK fw_6e4ba1a9_trlo/trlo_defs.h -> ../../ver/vulom4_trlo/trlo_defs.h
SYMLINK fw_1409285e_trlo -> fw_6e4ba1a9_trlo
MKDIR fw_68f8955e_trlo_all_in # ../ver/vulom4_trlo_all_in/trlo_all_in_defs.h
SYMLINK fw_68f8955e_trlo_all_in/trlo_all_in_defs.h -> ../../ver/vulom4_trlo_all_in/trlo_all_in_defs.h
MKDIR fw_af33ed35_trlo_big # ../ver/vulom4_trlo_big/trlo_big_defs.h
SYMLINK fw_af33ed35_trlo_big/trlo_big_defs.h -> ../../ver/vulom4_trlo_big/trlo_big_defs.h
MKDIR fw_d374466d_tridi # ../fw/tridi1_trlo/tridi_defs.h
SYMLINK fw_d374466d_tridi/tridi_defs.h -> ../../fw/tridi1_trlo/tridi_defs.h
MKDIR fw_d96ffc88_trlo # ../fw/vulom4_trlo/trlo_defs.h
SYMLINK fw_d96ffc88_trlo/trlo_defs.h -> ../../fw/vulom4_trlo/trlo_defs.h
SYMLINK fw_426cb99c_trlo -> fw_d96ffc88_trlo
SYMLINK fw_fa5020ea_trlo -> fw_d96ffc88_trlo
MKDIR fw_5b298165_trlo_all_in # ../fw/vulom4_trlo_all_in/trlo_all_in_defs.h
SYMLINK fw_5b298165_trlo_all_in/trlo_all_in_defs.h -> ../../fw/vulom4_trlo_all_in/trlo_all_in_defs.h
MKDIR fw_6f28c0f8_trlo_big # ../fw/vulom4_trlo_big/trlo_big_defs.h
SYMLINK fw_6f28c0f8_trlo_big/trlo_big_defs.h -> ../../fw/vulom4_trlo_big/trlo_big_defs.h
However, the compilation did end with an error:
make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo'
CC bld_ppc-linux_4.2.2/src/trlo_check_version.o
CC bld_ppc-linux_4.2.2/src/trlo_functions.o
../trlolib/src/trlo_functions.c: In function 'trlo_clear_config':
../trlolib/src/trlo_functions.c:144: error: 'trlo_setup_map' has no member named 'sync_check_start_mux'
../trlolib/src/trlo_functions.c:146: error: 'trlo_setup_map' has no member named 'sync_check_stop_mux'
../trlolib/src/trlo_functions.c: In function 'trlo_print_config':
../trlolib/src/trlo_functions.c:825: error: 'trlo_setup_map' has no member named 'sync_check_start_mux'
../trlolib/src/trlo_functions.c:829: error: 'trlo_setup_map' has no member named 'sync_check_stop_mux'
../trlolib/src/trlo_functions.c: In function 'trlo_print_trig_status':
../trlolib/src/trlo_functions.c:1155: error: 'trlo_output_map' has no member named 'trig_sync_check'
make[1]: *** [bld_ppc-linux_4.2.2/src/trlo_functions.o] Error 1
make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo'
make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi'
CC bld_ppc-linux_4.2.2/src/tridi_check_version.o
CC bld_ppc-linux_4.2.2/src/tridi_functions.o
../trlolib/src/trlo_functions.c: In function 'tridi_clear_config':
../trlolib/src/trlo_functions.c:144: error: 'tridi_setup_map' has no member named 'sync_check_start_mux'
../trlolib/src/trlo_functions.c:146: error: 'tridi_setup_map' has no member named 'sync_check_stop_mux'
../trlolib/src/trlo_functions.c: In function 'tridi_print_config':
../trlolib/src/trlo_functions.c:825: error: 'tridi_setup_map' has no member named 'sync_check_start_mux'
../trlolib/src/trlo_functions.c:829: error: 'tridi_setup_map' has no member named 'sync_check_stop_mux'
../trlolib/src/trlo_functions.c: In function 'tridi_print_trig_status':
../trlolib/src/trlo_functions.c:1155: error: 'tridi_output_map' has no member named 'trig_sync_check'
make[1]: *** [bld_ppc-linux_4.2.2/src/tridi_functions.o] Error 1
make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi'
make: *** [fw_d374466d_tridi_build] Error 2
The fallback option is now to delete the new TRLOII folder and replace it with old one and then repeat the following steps?
cd trloii
make clean
make
cd trloctrl
make fw_d96ffc88_trlo_build
make fw_d374466d_tridi_build
Is this correct?
I also looked for the "--addr=" and this is the result:
nurdlib/tools/rwdump.c:52: fprintf(str, " -a, --addr=address VME hex address, e.g. "
Übereinstimmungen in Binärdatei nurdlib/build_cc_ppc-linux_4.2.2_debug/tools/rwdump.o
Übereinstimmungen in Binärdatei nurdlib/build_cc_ppc-linux_4.2.2_debug/tools/rwdump
Übereinstimmungen in Binärdatei nurdlib/build_cc_ppc-linux_4.2.2_debug/nurdctrl
Übereinstimmungen in Binärdatei nurdlib/build_cc_ppc-linux_4.2.2_debug/ctrl/nurdctrl.o
nurdlib/ctrl/nurdctrl.c:214:" -a, --addr=host Talk to given host, default=localhost:"
Übereinstimmungen in Binärdatei trloii/flash/bin_ppc-linux_4.2.2/vulomflash
trloii/flash/vulomflash.c:869: printf ("Usage %s --addr=A [command] [file.rbt[,comment.txt]]\n", argv0);
trloii/flash/vulomflash.c:871: printf (" --addr=A Module address (HEX).\n");
trloii/flash/vulomflash.c:964: else if (strncmp(argv[i],"--addr=",7) == 0)
Übereinstimmungen in Binärdatei trloii/flash/bld_ppc-linux_4.2.2/vulomflash.o
Übereinstimmungen in Binärdatei trloii/flash/bin_x86_64-linux-gnu_7/vulomflash
Übereinstimmungen in Binärdatei trloii/flash/bld_x86_64-linux-gnu_7/vulomflash.o
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_ctrl.c:41: printf (" --addr=HEX Module address (HEX=dummy for dummy).\n");
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_ctrl.c:201: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:1532: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2202:../flash/vulomflash --addr=2 --restart=4
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2203:trlolib/trlo_ctrl --addr=2 --clear-setup
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2204:trlolib/trlo_ctrl --addr=2 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2205:trlolib/trlo_ctrl --addr=2 fast_busy_len=100ns
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2206:trlolib/trlo_ctrl --addr=2 --print-config
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2208:../trimictrl/trimictrl_Linux_ppc --addr=2 encoded_in=TRLO_ENCODED_TRIG
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2209:../trimictrl/trimictrl_Linux_ppc --addr=2 --status
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2211:../trimictrl/trimictrl_RIO4 --addr=2 encoded_in=TRLO_ENCODED_TRIG
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2212:../trimictrl/trimictrl_RIO4 --addr=2 "serial_out=ECL_OUT(1)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2213:../trimictrl/trimictrl_RIO4 --addr=2 "dt_in=ECL_IN(1)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2214:../trimictrl/trimictrl_RIO4 --addr=2 "fast_dt=40"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2215:../trimictrl/trimictrl_RIO4 --addr=2 "dt_out=ECL_OUT(3)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2216:../trimictrl/trimictrl_RIO4 --addr=2 "serial_in=ECL_IN(3)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2217:../trimictrl/trimictrl_RIO4 --addr=2 "link_period=8"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2218:../trimictrl/trimictrl_RIO4 --addr=2 --status
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2223:../flash/vulomflash --addr=3 --restart=4
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2224:trlolib/trlo_ctrl --addr=3 --clear-setup
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2225:trlolib/trlo_ctrl --addr=3 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2226:trlolib/trlo_ctrl --addr=3 fast_busy_len=100ns
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2227:trlolib/trlo_ctrl --addr=3 --print-config
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2229:../trimictrl/trimictrl_Linux_ppc --addr=3 encoded_in=TRLO_ENCODED_TRIG
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2230:../trimictrl/trimictrl_Linux_ppc --addr=3 "dt_out=ECL_OUT(1)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2231:../trimictrl/trimictrl_Linux_ppc --addr=3 "serial_in=ECL_IN(1)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2232:../trimictrl/trimictrl_Linux_ppc --addr=3 "serial_out=ECL_OUT(3)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2233:../trimictrl/trimictrl_Linux_ppc --addr=3 "dt_in=ECL_IN(3)"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2234:../trimictrl/trimictrl_Linux_ppc --addr=3 "fast_dt=40"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2235:../trimictrl/trimictrl_Linux_ppc --addr=3 "link_period=8"
trloii/trloctrl/fw_d96ffc88_trlo/src/trlo_trimi_test.c:2236:../trimictrl/trimictrl_Linux_ppc --addr=3 --status
trloii/trloctrl/trlolib/src/trlo_ctrl.c:40: printf (" --addr=HEX Module address (HEX=dummy for dummy).\n");
trloii/trloctrl/trlolib/src/trlo_ctrl.c:200: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:1531: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2201:../flash/vulomflash --addr=2 --restart=4
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2202:trlolib/trlo_ctrl --addr=2 --clear-setup
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2203:trlolib/trlo_ctrl --addr=2 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2204:trlolib/trlo_ctrl --addr=2 fast_busy_len=100ns
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2205:trlolib/trlo_ctrl --addr=2 --print-config
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2207:../trimictrl/trimictrl_Linux_ppc --addr=2 encoded_in=TRLO_ENCODED_TRIG
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2208:../trimictrl/trimictrl_Linux_ppc --addr=2 --status
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2210:../trimictrl/trimictrl_RIO4 --addr=2 encoded_in=TRLO_ENCODED_TRIG
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2211:../trimictrl/trimictrl_RIO4 --addr=2 "serial_out=ECL_OUT(1)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2212:../trimictrl/trimictrl_RIO4 --addr=2 "dt_in=ECL_IN(1)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2213:../trimictrl/trimictrl_RIO4 --addr=2 "fast_dt=40"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2214:../trimictrl/trimictrl_RIO4 --addr=2 "dt_out=ECL_OUT(3)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2215:../trimictrl/trimictrl_RIO4 --addr=2 "serial_in=ECL_IN(3)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2216:../trimictrl/trimictrl_RIO4 --addr=2 "link_period=8"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2217:../trimictrl/trimictrl_RIO4 --addr=2 --status
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2222:../flash/vulomflash --addr=3 --restart=4
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2223:trlolib/trlo_ctrl --addr=3 --clear-setup
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2224:trlolib/trlo_ctrl --addr=3 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2225:trlolib/trlo_ctrl --addr=3 fast_busy_len=100ns
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2226:trlolib/trlo_ctrl --addr=3 --print-config
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2228:../trimictrl/trimictrl_Linux_ppc --addr=3 encoded_in=TRLO_ENCODED_TRIG
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2229:../trimictrl/trimictrl_Linux_ppc --addr=3 "dt_out=ECL_OUT(1)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2230:../trimictrl/trimictrl_Linux_ppc --addr=3 "serial_in=ECL_IN(1)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2231:../trimictrl/trimictrl_Linux_ppc --addr=3 "serial_out=ECL_OUT(3)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2232:../trimictrl/trimictrl_Linux_ppc --addr=3 "dt_in=ECL_IN(3)"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2233:../trimictrl/trimictrl_Linux_ppc --addr=3 "fast_dt=40"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2234:../trimictrl/trimictrl_Linux_ppc --addr=3 "link_period=8"
trloii/trloctrl/trlolib/src/trlo_trimi_test.c:2235:../trimictrl/trimictrl_Linux_ppc --addr=3 --status
trloii/trloctrl/examples/vulom_prienc.trlo:20: * trlo_ctrl --addr=X --clear-setup --config=vulom_prienc.trlo "basic"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:1532: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2202:../flash/vulomflash --addr=2 --restart=4
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2203:trlolib/tridi_ctrl --addr=2 --clear-setup
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2204:trlolib/tridi_ctrl --addr=2 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2205:trlolib/tridi_ctrl --addr=2 fast_busy_len=100ns
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2206:trlolib/tridi_ctrl --addr=2 --print-config
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2208:../trimictrl/trimictrl_Linux_ppc --addr=2 encoded_in=TRIDI_ENCODED_TRIG
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2209:../trimictrl/trimictrl_Linux_ppc --addr=2 --status
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2211:../trimictrl/trimictrl_RIO4 --addr=2 encoded_in=TRIDI_ENCODED_TRIG
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2212:../trimictrl/trimictrl_RIO4 --addr=2 "serial_out=ECL_OUT(1)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2213:../trimictrl/trimictrl_RIO4 --addr=2 "dt_in=ECL_IN(1)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2214:../trimictrl/trimictrl_RIO4 --addr=2 "fast_dt=40"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2215:../trimictrl/trimictrl_RIO4 --addr=2 "dt_out=ECL_OUT(3)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2216:../trimictrl/trimictrl_RIO4 --addr=2 "serial_in=ECL_IN(3)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2217:../trimictrl/trimictrl_RIO4 --addr=2 "link_period=8"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2218:../trimictrl/trimictrl_RIO4 --addr=2 --status
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2223:../flash/vulomflash --addr=3 --restart=4
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2224:trlolib/tridi_ctrl --addr=3 --clear-setup
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2225:trlolib/tridi_ctrl --addr=3 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2226:trlolib/tridi_ctrl --addr=3 fast_busy_len=100ns
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2227:trlolib/tridi_ctrl --addr=3 --print-config
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2208:../trimictrl/trimictrl_Linux_ppc --addr=2 encoded_in=TRIDI_ENCODED_TRIG
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2209:../trimictrl/trimictrl_Linux_ppc --addr=2 --status
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2211:../trimictrl/trimictrl_RIO4 --addr=2 encoded_in=TRIDI_ENCODED_TRIG
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2212:../trimictrl/trimictrl_RIO4 --addr=2 "serial_out=ECL_OUT(1)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2213:../trimictrl/trimictrl_RIO4 --addr=2 "dt_in=ECL_IN(1)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2214:../trimictrl/trimictrl_RIO4 --addr=2 "fast_dt=40"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2215:../trimictrl/trimictrl_RIO4 --addr=2 "dt_out=ECL_OUT(3)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2216:../trimictrl/trimictrl_RIO4 --addr=2 "serial_in=ECL_IN(3)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2217:../trimictrl/trimictrl_RIO4 --addr=2 "link_period=8"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2218:../trimictrl/trimictrl_RIO4 --addr=2 --status
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2223:../flash/vulomflash --addr=3 --restart=4
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2224:trlolib/tridi_ctrl --addr=3 --clear-setup
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2225:trlolib/tridi_ctrl --addr=3 "DEADTIME_IN(1)=TRIMI_TDT"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2226:trlolib/tridi_ctrl --addr=3 fast_busy_len=100ns
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2227:trlolib/tridi_ctrl --addr=3 --print-config
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2229:../trimictrl/trimictrl_Linux_ppc --addr=3 encoded_in=TRIDI_ENCODED_TRIG
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2230:../trimictrl/trimictrl_Linux_ppc --addr=3 "dt_out=ECL_OUT(1)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2231:../trimictrl/trimictrl_Linux_ppc --addr=3 "serial_in=ECL_IN(1)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2232:../trimictrl/trimictrl_Linux_ppc --addr=3 "serial_out=ECL_OUT(3)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2233:../trimictrl/trimictrl_Linux_ppc --addr=3 "dt_in=ECL_IN(3)"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2234:../trimictrl/trimictrl_Linux_ppc --addr=3 "fast_dt=40"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2235:../trimictrl/trimictrl_Linux_ppc --addr=3 "link_period=8"
trloii/trloctrl/fw_d374466d_tridi/src/tridi_trimi_test.c:2236:../trimictrl/trimictrl_Linux_ppc --addr=3 --status
trloii/trloctrl/fw_d374466d_tridi/src/tridi_ctrl.c:41: printf (" --addr=HEX Module address (HEX=dummy for dummy).\n");
trloii/trloctrl/fw_d374466d_tridi/src/tridi_ctrl.c:201: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
trloii/trloctrl/trloctrl.sh:35:$TRLOCTRL_BASE/$TRLOCTRL_PGM --addr=$TRLOCTRL_ADDRESS $@
Übereinstimmungen in Binärdatei trloii/trimictrl/bin_ppc-linux_4.2.2/trimictrl
Übereinstimmungen in Binärdatei trloii/trimictrl/bld_ppc-linux_4.2.2/trimictrl.o
Übereinstimmungen in Binärdatei trloii/trimictrl/bin_x86_64-linux-gnu_7/trimictrl
trloii/trimictrl/trimictrl.c:52: printf (" --addr=HEX Module address.\n");
trloii/trimictrl/trimictrl.c:852: if (argc > iarg && strncmp(argv[iarg],"--addr=",7) == 0)
Übereinstimmungen in Binärdatei trloii/trimictrl/bld_x86_64-linux-gnu_7/trimictrl.o
trloii/scripts/makealiases.sh:46: ADDRESS=" --addr=$1"
trloii/doc/man/man7/trloii-intro.7:107: alias trimictrl \fI/trloii-path\fB/trimictrl/bin_\fIARCH\fB/trimictrl --addr=\fIVA\fR
trloii/doc/man/man7/trloii-intro.7:117: alias trimictrl=\(dq\fI/trloii-path\fB/trimictrl/bin_\fIARCH\fB/trimictrl --addr=\fIVA\fB\(dq\fR
trloii/doc/man/man7/trloii-intro.7:144:\fBvulomflash --addr=7 --read\fR
trloii/doc/man/man7/trloii-intro.7:180:\fBvulomflash --addr=7 --readprogs\fR
trloii/doc/man/man7/trloii-intro.7:208:\fBvulomflash --addr=7 \fIX\fBlogic\fIY\fB.rbt --prog=\fI6\fR
trloii/doc/man/man7/trloii-intro.7:236:\fBvulomflash --addr=7 --readprogs\fR
trloii/doc/man/man7/trloii-intro.7:244:\fBvulomflash --addr=7 --restart=6\fR
trloii/doc/man/man7/trloii-intro.7:248:\fBvulomflash --addr=7 --read\fR
trloii/doc/man/man7/trloii-intro.7:276: --addr=\fIVA\fR
trloii/doc/man/man7/trloii-intro.7:285: --addr=\fIVA\(dq\fR
history_saves/rio4_mcal_1.history:6: 6 9:55 ./bin_ppc-linux_4.2.2/vulomflash --addr=4
history_saves/rio4_mcal_1.history:7: 7 9:55 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --readprogs
history_saves/rio4_mcal_1.history:8: 8 9:56 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --help
history_saves/rio4_mcal_1.history:9: 9 9:56 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --extract=0,vulom_fw_range0.readback
history_saves/rio4_mcal_1.history:11: 11 9:57 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --help
history_saves/rio4_mcal_1.history:12: 12 9:58 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --readprogs=full
history_saves/rio4_mcal_1.history:21: 21 10:01 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --help
history_saves/rio4_mcal_1.history:22: 22 10:01 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --prog=1 ../fw/vulom4b_trlo/vlogic_4b.rbt
history_saves/rio4_mcal_1.history:23: 23 10:02 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --restart=1
history_saves/rio4_mcal_1.history:24: 24 10:02 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --readprogs
history_saves/rio4_mcal_1.history:41: 41 10:12 $TRLOII_FLASH --addr=4
rio4-mcal-2/scaler.sh:2:$VULOM4_CTRL --addr=$addr --mux-src-scalers=ptn,$1
rio4-mcal-2/trloii_setup.sh:6:# $VULOM4_CTRL --addr=$addr --clear-setup --config=vulom.trlo standalone module_trigger pulser_to_channels
rio4-mcal-2/trloii_setup.sh:9:# $VULOM4_CTRL --addr=$addr --clear-setup --config=vulom.trlo standalone module_trigger
rio4-mcal-2/trloii_setup.sh:12:$VULOM4_CTRL --addr=$addr --clear-setup --config=vulom.trlo standalone module_trigger
rio4-mcal-2/trloii_setup.sh:19:# $TRIMI_CTRL --addr=$addr encoded_in=TRLO_ENCODED_TRIG fast_dt=1000
rio4-mcal-2/rio4_mcal_1.history:6: 6 9:55 ./bin_ppc-linux_4.2.2/vulomflash --addr=4
rio4-mcal-2/rio4_mcal_1.history:7: 7 9:55 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --readprogs
rio4-mcal-2/rio4_mcal_1.history:8: 8 9:56 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --help
rio4-mcal-2/rio4_mcal_1.history:9: 9 9:56 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --extract=0,vulom_fw_range0.readback
rio4-mcal-2/rio4_mcal_1.history:11: 11 9:57 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --help
rio4-mcal-2/rio4_mcal_1.history:12: 12 9:58 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --readprogs=full
rio4-mcal-2/rio4_mcal_1.history:21: 21 10:01 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --help
rio4-mcal-2/rio4_mcal_1.history:22: 22 10:01 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --prog=1 ../fw/vulom4b_trlo/vlogic_4b.rbt
rio4-mcal-2/rio4_mcal_1.history:23: 23 10:02 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --restart=1
rio4-mcal-2/rio4_mcal_1.history:24: 24 10:02 ./bin_ppc-linux_4.2.2/vulomflash --addr=4 --readprogs
rio4-mcal-2/rio4_mcal_1.history:41: 41 10:12 $TRLOII_FLASH --addr=4
drasi/f_user_example/f_user_sync.c:197:${TRLOLIB_DIR}/bin_`bin/drasi-config.sh --arch-prefix`/trlo_ctrl --addr=3 \
drasi/f_user_example/f_user_sync.c:203:${TRLOLIB_DIR}/../../bin/trimictrl --addr=3 "encoded_in=TRLO_ENCODED_TRIG"
drasi/f_user_example/f_user_sync.c:211:${TRLOLIB_DIR}/bin_`bin/drasi-config.sh --arch-prefix`/trlo_ctrl --addr=2 \
drasi/f_user_example/f_user_sync.c:217:${TRLOLIB_DIR}/../../bin/trimictrl --addr=2 "encoded_in=TRLO_ENCODED_TRIG"
drasi/perf/readout/perf2.txt:1:# bin_ppc-linux_4.2.2/tridi_ctrl --addr=2 "TRIG_PENDING[1]=PULSER(1)" "period(1)=100ns" "TRIG_PENDING[2]=WIRED_ZERO" "TRIG_PENDING[3]=WIRED_ZERO"
drasi/perf/readout/perf2.txt:2:# bin_ppc-linux_4.2.2/tridi_ctrl --addr=2 "TRIG_PENDING[1]=PULSER(1)" "period(1)=20000ns" "TRIG_PENDING[2]=PULSER(2)" "period(2)=19990ns" "TRIG_PENDING[3]=PULSER(3)" "period(3)=20030ns"
drasi/perf/readout/perfplot.py:437:bin_ppc-linux_4.2.2/tridi_ctrl --addr=2 \
drasi/perf/readout/perfplot.py:441:bin_ppc-linux_4.2.2/tridi_ctrl --addr=2 \
drasi/perf/readout/perfplot.py:449:bin_ppc-linux_4.2.2/tridi_ctrl --addr=2 --print-config
Best greetings
Günter
________________________________
Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan T Johansson <f96hajo at chalmers.se>
Gesendet: Dienstag, 9. Januar 2024 23:21:08
An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version
On Tue, 9 Jan 2024, Weber, Guenter Dr. wrote:
>
> Dear Håkan,
>
>
> in the old directory I found "trloii_firmwares_c44f109.tar.gz".
>
>
> I should now delete the new TRLOII folder and replace it with the extracted archive, correct?
No, extract the archive in the trloii/ folder.
> Then just typing in "find_firmwares.pl" (or should it be "./find_firmwares.pl"?) in TRLOCTRL
> will, hopefully, do the trick, right?
Yes, "./find_firmwares.pl" in trloii/trloctrl/
And then we cross fingers that the newer code compiles with the older
headers. (Likely, but no guarantee.)
If not, then get the older trloii/ directory which presumably has the
firmwares already unpacked in it.
> With VULOM address you mean the physical address that is set on the module? No, I do not know it.
> But tomorrow I can find out, of course.
Or likely it is in some script somewhere.
grep -r "--addr="
might reveal it :-)
Cheers,
Håkan
>
>
>
>
>
> Best greetings
>
> Günter
>
>
>
>
> _________________________________________________________________________________________________
> Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan T Johansson
> <f96hajo at chalmers.se>
> Gesendet: Dienstag, 9. Januar 2024 22:28:24
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to
> the most recent version
>
> My mistake:
>
> in a new trloii directory,
>
> after
>
> cd trloctrl
>
> you need to do
>
> find_firmwares.pl
>
> before the make <something>_build
>
> however, I suspect we'll then run into the next issue, namely that the
> TRLO II firmware that you have likely is old. I do not see d96ffc88 in
> the list of current ones
>
> http://fy.chalmers.se/~f96hajo/trloii/firmwares.html
>
> --
>
> This is not needed, but might help to figure that:
>
> If you can run (new or old) $TRLOII_FLASH or just from trloii/ dir:
>
> bin/vulomflash --addr=X --readprogs
>
> where X needs to be the address of the vulom module, that would give a
> list. Do you know what the vulom address is?
>
> --
>
> Hmmmm. To update that means to also update what runs on the VULOM4, which
> makes it more messy to go back-and-forth. Or to run another version of it
> but without changing its default. Doable, but I think we are getting a
> few too many loose variables here right now.
>
> I think it would be best if you for the moment copy over the old trloii/
> directory and try to recompile that one in the new location.
>
> --
>
> The other way is if you have a
>
> trloii_firmwares_XXX.tar.gz
>
> file, e.g. in the (old) trloii/ directory, and unpåack that in the new
> trloii/, then find_firmwares.pl should also find those (old) headers, and
> hopefully produce a line also with d374466d.
>
> --
>
> Sorry that this is becoming a bit too convoluted to be really pleasant.
>
> Cheers,
> Håkan
>
>
>
>
> On Tue, 9 Jan 2024, Weber, Guenter Dr. wrote:
>
> >
> > Ok, after this fix, the compilation in TRLOII finshes without problems.
> >
> >
> > But in TRLOCTRL we have the following problem (as already noticed when I tried to compile on
> the
> > PC).
> >
> >
> > RIO4-MCAL-2 mbsdaq > pwd
> > /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl
> > RIO4-MCAL-2 mbsdaq > make fw_d96ffc88_trlo_build
> > cat: firmwaredirs: No such file or directory
> > make -C fw_d96ffc88_trlo -f ../trlolib/Makefile \
> > TRLOBASENAME=`cat fw_d96ffc88_trlo/trlobasename` FILTERSRC=1
> > cat: fw_d96ffc88_trlo/trlobasename: No such file or directory
> > make: *** fw_d96ffc88_trlo: No such file or directory. Stop.
> > make: *** [fw_d96ffc88_trlo_build] Error 2
> > RIO4-MCAL-2 mbsdaq > make fw_d374466d_tridi_build
> > cat: firmwaredirs: No such file or directory
> > make -C fw_d374466d_tridi -f ../trlolib/Makefile \
> > TRLOBASENAME=`cat fw_d374466d_tridi/trlobasename` FILTERSRC=1
> > cat: fw_d374466d_tridi/trlobasename: No such file or directory
> > make: *** fw_d374466d_tridi: No such file or directory. Stop.
> > make: *** [fw_d374466d_tridi_build] Error 2
> >
> > After this I went ahead to DRASI and there the compilation finished without error.
> >
> > Thus, if the issue with TRLOCTRL could be solved, maybe our DAQ is good to go ??
> >
> >
> >
> > Best greetings
> > Günter
> >
> >
> >
> >________________________________________________________________________________________________
> _
> > Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan T Johansson
> > <f96hajo at chalmers.se>
> > Gesendet: Dienstag, 9. Januar 2024 16:59:07
> > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> > Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update
> to
> > the most recent version
> >
> > Quick-fix II: comment out trigalign_dir from the targets in trloii/Makefile:
> >
> > all: trimictrl_dir flash_dir \
> > proglinks # trigalign_dir
> >
> > Cheers,
> > Håkan
> >
> >
> >
> > On Tue, 9 Jan 2024, Weber, Guenter Dr. wrote:
> >
> > >
> > > Unfortunately, "make -k" ends with the same result:
> > >
> > >
> > > ...
> > >
> > > make[1]: Entering directory
> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trigalign'
> > > CC bld_ppc-linux_4.2.2/align_analyse.o
> > > CC bld_ppc-linux_4.2.2/gen_ppc-linux_4.2.2/align_parser.o
> > > gen_ppc-linux_4.2.2/align_parser.c:19: warning: 'align_growstack' declared 'static' but never
> > defined
> > > CC bld_ppc-linux_4.2.2/gen_ppc-linux_4.2.2/align_lexer.o
> > > align_lexer.l: In function 'align_lex':
> > > align_lexer.l:28: error: 'align_lval' undeclared (first use in this function)
> > > align_lexer.l:28: error: (Each undeclared identifier is reported only once
> > > align_lexer.l:28: error: for each function it appears in.)
> > > align_lexer.l:29: error: 'INTEGER' undeclared (first use in this function)
> > > align_lexer.l:32: error: 'START' undeclared (first use in this function)
> > > align_lexer.l:33: error: 'END' undeclared (first use in this function)
> > > align_lexer.l:34: error: 'CH' undeclared (first use in this function)
> > > align_lexer.l:35: error: 'DELAY' undeclared (first use in this function)
> > > make[1]: *** [bld_ppc-linux_4.2.2/gen_ppc-linux_4.2.2/align_lexer.o] Error 1
> > > make[1]: Target `all' not remade because of errors.
> > > make[1]: Leaving directory
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trigalign'
> > > make: *** [trigalign_dir] Error 2
> > > make: Target `all' not remade because of errors.
> > >
> > >
> >>_______________________________________________________________________________________________
> _
> > _____________________________________________________
> > > Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan T Johansson
> > <f96hajo at chalmers.se>
> > > Gesendet: Dienstag, 9. Januar 2024 16:36:28
> > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> > > Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to
> update
> > to the most recent version
> > >
> > > Quick-fix for the trigalign:
> > >
> > > try compile with 'make -k', which tries to continue with other things.
> > > the trigger aligment you likely do not use, so we can solve that more slowly.
> > >
> > > You are not creating problems, we want/need to know what does not work so
> > > it can get fixed :)
> > >
> > > Cheers,
> > > Håkan
> > >
> > >
> > >
> > > On Tue, 9 Jan 2024, Weber, Guenter Dr. wrote:
> > >
> > > >
> > > > Dear friends,
> > > >
> > > >
> > > > what I now did:
> > > >
> > > >
> > > > 1) Deleting the folders of DRASI, TRLOII, and R3BFUSER
> > > >
> > > > 2) Downloading the most recent versions from Gitlab
> > > >
> > > > 3) Executing MAKE CLEAN, followed by MAKE in the folders TRLOII and DRASI on the PC (make
> > fw_d96ffc88_trlo_build failed on the PC, make
> > > > fw_d374466d_tridi_build I did not try)
> > > >
> > > > 4) Executing MAKE CLEAN, followed by MAKE on the RIO in the folder TRLOII. And there a new
> > problem shows up:
> > > >
> > > >
> > > > make[1]: Entering directory
> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trigalign'
> > > > CC bld_ppc-linux_4.2.2/align_analyse.o
> > > > CC bld_ppc-linux_4.2.2/gen_ppc-linux_4.2.2/align_parser.o
> > > > gen_ppc-linux_4.2.2/align_parser.c:19: warning: 'align_growstack' declared 'static' but
> never
> > defined
> > > > CC bld_ppc-linux_4.2.2/gen_ppc-linux_4.2.2/align_lexer.o
> > > > align_lexer.l: In function 'align_lex':
> > > > align_lexer.l:28: error: 'align_lval' undeclared (first use in this function)
> > > > align_lexer.l:28: error: (Each undeclared identifier is reported only once
> > > > align_lexer.l:28: error: for each function it appears in.)
> > > > align_lexer.l:29: error: 'INTEGER' undeclared (first use in this function)
> > > > align_lexer.l:32: error: 'START' undeclared (first use in this function)
> > > > align_lexer.l:33: error: 'END' undeclared (first use in this function)
> > > > align_lexer.l:34: error: 'CH' undeclared (first use in this function)
> > > > align_lexer.l:35: error: 'DELAY' undeclared (first use in this function)
> > > > make[1]: *** [bld_ppc-linux_4.2.2/gen_ppc-linux_4.2.2/align_lexer.o] Error 1
> > > > make[1]: Leaving directory
> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trigalign'
> > > > make: *** [trigalign_dir] Error 2
> > > >
> > > > When I was compiling TRLOII with the old version, this error did not occur.
> > > >
> > > >
> > > >
> > > > I am really sorry for causing so much trouble ??
> > > >
> > > >
> > > >
> > > >
> > > > Best greetings
> > > >
> > > > Günter
> > > >
> > > >
> > > >
> >>>______________________________________________________________________________________________
> _
> > _____________________________________________________
> > > _
> > > > Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan T Johansson
> > <f96hajo at chalmers.se>
> > > > Gesendet: Dienstag, 9. Januar 2024 16:05:19
> > > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> > > > Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to
> > update to the most recent version
> > > >
> > > > Dear Günter,
> > > >
> > > > yes, please download the latest drasi. That should fix the broken link.
> > > >
> > > > ALso, compile it on the PC first. That will download the file, and then
> > > > the RIO compile will use that.
> > > >
> > > > I'd suggest to also update trloii before compiling! Same trick there
> > > > might be helpful, i.e. compile on PC first. Nothing to download, but some
> > > > generated files are quicker made on a PC.
> > > >
> > > > Cheers,
> > > > Håkan
> > > >
> > > >
> > > > On Tue, 9 Jan 2024, Weber, Guenter Dr. wrote:
> > > >
> > > > >
> > > > > Dear Håkan,
> > > > >
> > > > >
> > > > > in the last step (DRASI compilation) I now get this problem:
> > > > >
> > > > >
> > > > > make[1]: Entering directory
> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwrocmon'
> > > > > CC bld_ppc-linux_4.2.2/lwrocmon.o
> > > > > CC bld_ppc-linux_4.2.2/lwroc_mon_basic.o
> > > > > CC bld_ppc-linux_4.2.2/lwroc_mon_rate.o
> > > > > CC bld_ppc-linux_4.2.2/lwroc_mon_detail.o
> > > > > CC bld_ppc-linux_4.2.2/lwroc_mon_tree.o
> > > > > lwroc_mon_tree.c: In function 'lwroc_draw_mon_tree_item':
> > > > > lwroc_mon_tree.c:3116: warning: 'label._ambiguity' may be used uninitialized in this
> > function
> > > > > CC bld_ppc-linux_4.2.2/lwroc_mon_status.o
> > > > > LINK bin_ppc-linux_4.2.2/lwrocmon
> > > > > CC bld_ppc-linux_4.2.2/lwroclog.o
> > > > > LINK bin_ppc-linux_4.2.2/lwroclog
> > > > > CC bld_ppc-linux_4.2.2/lwrocctrl.o
> > > > > LINK bin_ppc-linux_4.2.2/lwrocctrl
> > > > > LINK bin_ppc-linux_4.2.2/lwrocmerge
> > > > > DOWNLOAD https://www.ietf.org/timezones/data/leap-seconds.list
> > > > > curl: (6) Couldn't resolve host 'www.ietf.org<http://www.ietf.org>'
> > > > > ../scripts/download-leap-seconds.sh: line 67: wget: command not found
> > > > > Failed to download download/leap-seconds.list from
> > https://www.ietf.org/timezones/data/leap-seconds.list
> > > > > Try on other platform, or manually, or use IGNORELEAPSECONDFILE=1
> > > > > make[1]: *** [download/leap-seconds.list] Error 1
> > > > > make[1]: Leaving directory
> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwrocmon'
> > > > > make: *** [lwrocmon_dir] Error 2
> > > > >
> > > > > Problem 1: the RIO has no connection to the web.
> > > > >
> > > > > Problem 2: the links is no longer valid, see here:
> > https://www.ietf.org/timezones/data/leap-seconds.list
> > > > >
> > > > >
> > > > > Possible solution for problem 2:
> > https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list
> > > > >
> > > > > (But I have no idea if this file has an identical structure or just the same name.)
> > > > >
> > > > >
> > > > > There is the possibility to set the variable "LEAPFILE" that is used in
> > > > > "~/mbsrun/rio4/2024_mcalstruck/drasi/scripts/download-leap-seconds.sh" to point to a
> local
> > file. However, LEAPFILE is set in the
> > > > > following way:
> > > > >
> > > > >
> > > > > LEAPFILE=$1
> > > > >
> > > > > So, I would need to know where "download-leap-seconds.sh" is called to give it the right
> > value. And then cross the fingers that
> > > > > leap-seconds.list that I found on the web is the right one.
> > > > >
> > > > >
> > > > > I am really curious how Bastian managed to compile DRASI on our system without running
> into
> > this problem.
> > > > >
> > > > >
> > > > > Alternatively, should I download the most recent DRASI version and give it a try?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Best greetings
> > > > >
> > > > > Günter
> > > > >
> > > > >
> > > > >
> > > >>_______________________________________________________________________________________________
> _
> > ________________________________
> > > > > Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan T Johansson
> > <f96hajo at chalmers.se>
> > > > > Gesendet: Dienstag, 9. Januar 2024 14:56:41
> > > > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> > > > > Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to
> > update to the most recent version
> > > > >
> > > > > Dear Günter,
> > > > >
> > > > > the 'make drasi' in the 'r3bfuser' directory actually does not compile
> > > > > drasi itself (I suspect) but a readout which uses files from drasi (and
> > > > > trloii). One suspicion is that due to the directory change, some paths
> > > > > have ended up being hard-coded in the actual 'drasi' and 'trloii'
> > > > > directories.
> > > > >
> > > > > Since you are working in a full copy anyhow, please try
> > > > >
> > > > > cd $EXP_PATH
> > > > > pwd # make sure it is the new path
> > > > > cd trloii
> > > > > make clean
> > > > > make
> > > > > cd trloctrl
> > > > > make fw_d96ffc88_trlo_build
> > > > > make fw_d374466d_tridi_build
> > > > >
> > > > > cd $EXP_PATH
> > > > > pwd # make sure it is the new path
> > > > > cd drasi
> > > > > make
> > > > >
> > > > > and then the compilation in the 'r3bfuser' directory.
> > > > >
> > > > > ---
> > > > >
> > > > > Let's see if that helps.
> > > > >
> > > > > Cheers,
> > > > > Håkan
> > > > >
> > > > >
> > > > >
> > > > > On Tue, 9 Jan 2024, Weber, Guenter Dr. wrote:
> > > > >
> > > > > >
> > > > > > P.S.
> > > > > >
> > > > > >
> > > > > > I also checked what is in the folder "build_cc_ppc-linux_4.2.2_debug" of the previous
> > version of NURDLIB:
> > > > > >
> > > > > >
> > > > > > RIO4-MCAL-2 mbsdaq > ls -l
> > > > > > total 2192
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jun 28 2023 _ccd/
> > > > > > drwx--S--- 3 mbsdaq daq 4096 Jun 28 2023 _hconf/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jun 28 2023 config/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jun 28 2023 crate/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jun 28 2023 ctrl/
> > > > > > drwxr-sr-x 5 mbsdaq daq 4096 Mar 1 2023 hconf/
> > > > > > -rw-r--r-- 1 mbsdaq daq 1749 Jun 28 2023 hconf.cache
> > > > > > -rw-r--r-- 1 mbsdaq daq 11 Jun 28 2023 hconf.cache.ccd
> > > > > > -rw-r--r-- 1 mbsdaq daq 2174826 Sep 11 12:19 libnurdlib.a
> > > > > > -rwxr-xr-x 1 mbsdaq daq 19974 Jun 28 2023 md5summer*
> > > > > > drwxr-sr-x 48 mbsdaq daq 4096 Sep 11 12:19 module/
> > > > > > drwxr-sr-x 5 mbsdaq daq 4096 Mar 1 2023 replacements/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jun 28 2023 tools/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jun 28 2023 util/
> > > > > >
> > > > > > Obviously, there are quite some differences. Maybe this helps to understand what the
> > problem with DRASI compilation is.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Best greetings
> > > > > >
> > > > > > Günter
> > > > > >
> > > > > >
> > > > > >
> > > >>>______________________________________________________________________________________________
> _
> > ________________________________
> > > > > _
> > > > > > Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Weber, Guenter
> Dr.
> > <g.weber at hi-jena.gsi.de>
> > > > > > Gesendet: Dienstag, 9. Januar 2024 13:28:24
> > > > > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> > > > > > Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to
> > update to the most recent version
> > > > > >
> > > > > > Dear Hans,
> > > > > >
> > > > > >
> > > > > > here is the result when I try to compile DRASI:
> > > > > >
> > > > > >
> > > > > > RIO4-MCAL-2 mbsdaq > make drasi
> > > > > > rm -f build_cc_ppc-linux_4.2.2_debug
> > > > > > [ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p
> > build_cc_ppc-linux_4.2.2_debug_drasi
> > > > > > ln -s build_cc_ppc-linux_4.2.2_debug_drasi build_cc_ppc-linux_4.2.2_debug
> > > > > > make -f Makefile.drasi
> > > > > > sed: can't read ../nurdlib/build_cc_ppc-linux_4.2.2_debug/hconf.cache: No such file or
> > directory
> > > > > > sed: can't read ../nurdlib/build_cc_ppc-linux_4.2.2_debug/hconf.cache: No such file or
> > directory
> > > > > > make[1]: Entering directory
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> > > > > > make -C ../nurdlib lib
> > > > > > Could not figure out RFX1 firmware (8-xdigit number), skipping.
> > > > > > TRIDI_FW=d374466d
> > > > > > VULOM4_FW=d96ffc88
> > > > > > RFX1_FW=
> > > > > > make[2]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib'
> > > > > > make[2]: Nothing to be done for `lib'.
> > > > > > make[2]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib'
> > > > > > make[1]: *** No rule to make target
> > `../nurdlib/build_cc_ppc-linux_4.2.2_debug/hconf.cache', needed by
> > > > > > `build_cc_ppc-linux_4.2.2_debug/hconf.cache'. Stop.
> > > > > > make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> > > > > > make: *** [drasi] Error 2
> > > > > >
> > > > > > As "hconf.cache" is not found, I had a look at the content of
> > "nurdlib/build_cc_ppc-linux_4.2.2_debug":
> > > > > >
> > > > > > RIO4-MCAL-2 mbsdaq > ls -l
> > > > > > total 8084
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jan 8 14:27 config/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jan 8 14:27 crate/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jan 9 10:54 ctrl/
> > > > > > -rw-r--r-- 1 mbsdaq daq 2165210 Jan 9 10:54 libnurdlib.a
> > > > > > -rwxr-xr-x 1 mbsdaq daq 19930 Jan 8 14:27 md5summer*
> > > > > > drwxr-sr-x 54 mbsdaq daq 4096 Jan 8 14:28 module/
> > > > > > drwx--S--- 5 mbsdaq daq 4096 Jan 8 14:27 nconf/
> > > > > > -rw-r--r-- 1 mbsdaq daq 400 Jan 8 14:27 nconf.args
> > > > > > -rw-r--r-- 1 mbsdaq daq 4 Jan 8 14:27 nconf.args.1st
> > > > > > -rwxr-xr-x 1 mbsdaq daq 27707 Jan 8 14:27 nconfer*
> > > > > > drwx--S--- 3 mbsdaq daq 4096 Jan 8 14:27 nconfing/
> > > > > > drwxr-sr-x 3 mbsdaq daq 4096 Jan 8 14:29 ntest/
> > > > > > -rwxr-xr-x 1 mbsdaq daq 1726034 Jan 9 10:54 nurdctrl*
> > > > > > drwxr-sr-x 5 mbsdaq daq 4096 Jan 8 14:27 replacements/
> > > > > > -rwxr-xr-x 1 mbsdaq daq 2381977 Jan 8 14:29 test*
> > > > > > -rw-r--r-- 1 mbsdaq daq 116999 Jan 9 10:54 test.log
> > > > > > -rwxr-xr-x 1 mbsdaq daq 1724366 Jan 9 10:54 test_ctrl*
> > > > > > -rw-r--r-- 1 mbsdaq daq 3612 Jan 9 10:54 test_ctrl.log
> > > > > > -rw-r--r-- 1 mbsdaq daq 0 Jan 9 10:54 test_ctrl_ok
> > > > > > -rwxr-xr-x 1 mbsdaq daq 42392 Jan 8 14:29 test_ntest*
> > > > > > -rw-r--r-- 1 mbsdaq daq 1217 Jan 8 14:29 test_ntest.log
> > > > > > -rw-r--r-- 1 mbsdaq daq 0 Jan 8 14:29 test_ntest_ok
> > > > > > -rw-r--r-- 1 mbsdaq daq 0 Jan 9 10:54 test_ok
> > > > > > drwxr-sr-x 3 mbsdaq daq 4096 Jan 9 10:54 tests/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jan 9 10:55 tools/
> > > > > > drwxr-sr-x 2 mbsdaq daq 4096 Jan 8 14:28 util/
> > > > > >
> > > > > >
> > > > > > Do you have any idea what went wrong? Maybe the DRASI version that is on our machine is
> > too old and compatible with the most
> > > > > > recent NURDLIB version?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Best greetings
> > > > > >
> > > > > > Günter
> > > > > >
> > > > > >
> > > > > >
> > > >>>______________________________________________________________________________________________
> _
> > ________________________________
> > > > > _
> > > > > > Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Hans Toshihide
> > Törnqvist <hans.tornqvist at chalmers.se>
> > > > > > Gesendet: Dienstag, 9. Januar 2024 11:31:34
> > > > > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, Guenter Dr.
> > > > > > Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to
> > update to the most recent version
> > > > > > Dear Günter,
> > > > > >
> > > > > > On 2024-01-09 11:18, Weber, Guenter Dr. wrote:
> > > > > > > Dear Hans, dear Håkan,
> > > > > > >
> > > > > > > now the compilation was successful.
> > > > > >
> > > > > > *Thumbs up*
> > > > > >
> > > > > > > Side note:
> > > > > > >
> > > > > > > 'export VARIABLE_NAME=VARIABLE_VALUE' did not work on our RIO4. Instead
> > > > > > > 'setenv VARIABLE_NAME VARIABLE_VALUE' needed to be used. Probably, this
> > > > > > > due to not using bash but tcsh (for whatever reason).
> > > > > >
> > > > > > If I remember correctly, the historical reason was to easily have the
> > > > > > .bashrc for normal systems and the .tcshrc for DAQ systems.
> > > > > >
> > > > > > > Now I updated the NURDLIB, right? To check if it actually works with the
> > > > > > > hardware present, I would now need to run the DAQ and have a look at the
> > > > > > > output data.
> > > > > >
> > > > > > You also need to rebuild the f-user. Nurdlib provides the library to
> > > > > > read out hardware, the f-user is the piece of code between nurdlib and
> > > > > > the DAQ backend, in this case drasi.
> > > > > > So, something like:
> > > > > >
> > > > > > cp -r r3bfuser r3bfuser.20240109 # Backup!
> > > > > > cd r3bfuser
> > > > > > rm -rf build_*
> > > > > > make drasi
> > > > > >
> > > > > > I'm pretty sure that r3bfuser looks for nurdlib in "../nurdlib/".
> > > > > >
> > > > > > > Will DRASI automatically work with the new NURDLIB or do I need to
> > > > > > > compile it again?
> > > > > >
> > > > > > This would solved with the r3bfuser rebuild :)
> > > > > > Eventually, once this nurdlib business is settled, you could consider
> > > > > > updating drasi too. It's good practice, updating and backing things up.
> > > > > >
> > > > > > > Will also UCESB automatically adapt to the new NURDLIB or do I need to
> > > > > > > compile it again?
> > > > > >
> > > > > > Should be fine as is.
> > > > > >
> > > > > > > (I am a bit puzzled by the fact that it is
> > > > > > > '~/mbsrun/rio4/mcalstruck/ucesb/...' and not
> > > > > > > '~/mbsrun/rio4/2023_mcalstruck/ucesb/...'. This seems to be inconsistent.)
> > > > > >
> > > > > > Feel free to play around, again once the nurdlib stuff is done!
> > > > > >
> > > > > > > Moreover, I found the following environment variables that (to my
> > > > > > > understanding) tell the various parts of the DAQ software where it can
> > > > > > > find some necessary stuff:
> > > > > > >
> > > > > > > TRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii
> > > > > > >
> > > >>TRIDI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/
> b
> > in_ppc-linux_4.2.2/tridi_ctrl
> > > > > >>TRIMI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trimictrl/bin_ppc-linux_4.2
> .
> > 2/trimictrl
> > > > > >>TRLOII_FLASH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/flash/bin_ppc-linux_4.2.2
> /
> > vulomflash
> > > > > >>VULOM4_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/
> b
> > in_ppc-linux_4.2.2/trlo_ctrl
> > > > > > > EXP_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck
> > > > > > > HTOOLS_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/htools
> > > > > > >
> > > > > > > As I copied the complete folder structure of '2023_mcalstruck' to
> > > > > > > '2024_mcalstruck', to be consistent I will redefine all this variables
> > > > > > > to point to the new folder.
> > > > > >
> > > > > > Good idea, and eventually you may want to automate this with a set of
> > > > > > other scripts for future DAQ:s :)
> > > > > >
> > > > > > > Best greetings from Jena
> > > > > > >
> > > > > > > Günter
> > > > > > Cheers,
> > > > > > Hans
> > > > > > --
> > > > > > subexp-daq mailing list
> > > > > > subexp-daq at lists.chalmers.se
> > > > > > https://lists.chalmers.se/mailman/listinfo/subexp-daq
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chalmers.se/pipermail/subexp-daq/attachments/20240110/772c3b05/attachment-0001.html>
More information about the subexp-daq
mailing list