<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:14pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Dear Hans,</p>
<p><br>
</p>
<p>here is the result when I try to compile DRASI:</p>
<p><br>
</p>
<p></p>
<div>RIO4-MCAL-2 mbsdaq > make drasi<br>
rm -f build_cc_ppc-linux_4.2.2_debug<br>
[ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p build_cc_ppc-linux_4.2.2_debug_drasi<br>
ln -s build_cc_ppc-linux_4.2.2_debug_drasi build_cc_ppc-linux_4.2.2_debug<br>
make -f Makefile.drasi<br>
sed: can't read ../nurdlib/build_cc_ppc-linux_4.2.2_debug/hconf.cache: No such file or directory<br>
sed: can't read ../nurdlib/build_cc_ppc-linux_4.2.2_debug/hconf.cache: No such file or directory<br>
make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
make -C ../nurdlib lib<br>
Could not figure out RFX1 firmware (8-xdigit number), skipping.<br>
TRIDI_FW=d374466d<br>
VULOM4_FW=d96ffc88<br>
RFX1_FW=<br>
make[2]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib'<br>
make[2]: Nothing to be done for `lib'.<br>
make[2]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib'<br>
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.<br>
make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
make: *** [drasi] Error 2</div>
<div><br>
</div>
<div>As "hconf.cache" is not found, I had a look at the content of "<span>nurdlib/build_cc_ppc-linux_4.2.2_debug</span>":</div>
<div><br>
</div>
<div>
<div>RIO4-MCAL-2 mbsdaq > ls -l<br>
total 8084<br>
drwxr-sr-x 2 mbsdaq daq 4096 Jan 8 14:27 config/<br>
drwxr-sr-x 2 mbsdaq daq 4096 Jan 8 14:27 crate/<br>
drwxr-sr-x 2 mbsdaq daq 4096 Jan 9 10:54 ctrl/<br>
-rw-r--r-- 1 mbsdaq daq 2165210 Jan 9 10:54 libnurdlib.a<br>
-rwxr-xr-x 1 mbsdaq daq 19930 Jan 8 14:27 md5summer*<br>
drwxr-sr-x 54 mbsdaq daq 4096 Jan 8 14:28 module/<br>
drwx--S--- 5 mbsdaq daq 4096 Jan 8 14:27 nconf/<br>
-rw-r--r-- 1 mbsdaq daq 400 Jan 8 14:27 nconf.args<br>
-rw-r--r-- 1 mbsdaq daq 4 Jan 8 14:27 nconf.args.1st<br>
-rwxr-xr-x 1 mbsdaq daq 27707 Jan 8 14:27 nconfer*<br>
drwx--S--- 3 mbsdaq daq 4096 Jan 8 14:27 nconfing/<br>
drwxr-sr-x 3 mbsdaq daq 4096 Jan 8 14:29 ntest/<br>
-rwxr-xr-x 1 mbsdaq daq 1726034 Jan 9 10:54 nurdctrl*<br>
drwxr-sr-x 5 mbsdaq daq 4096 Jan 8 14:27 replacements/<br>
-rwxr-xr-x 1 mbsdaq daq 2381977 Jan 8 14:29 test*<br>
-rw-r--r-- 1 mbsdaq daq 116999 Jan 9 10:54 test.log<br>
-rwxr-xr-x 1 mbsdaq daq 1724366 Jan 9 10:54 test_ctrl*<br>
-rw-r--r-- 1 mbsdaq daq 3612 Jan 9 10:54 test_ctrl.log<br>
-rw-r--r-- 1 mbsdaq daq 0 Jan 9 10:54 test_ctrl_ok<br>
-rwxr-xr-x 1 mbsdaq daq 42392 Jan 8 14:29 test_ntest*<br>
-rw-r--r-- 1 mbsdaq daq 1217 Jan 8 14:29 test_ntest.log<br>
-rw-r--r-- 1 mbsdaq daq 0 Jan 8 14:29 test_ntest_ok<br>
-rw-r--r-- 1 mbsdaq daq 0 Jan 9 10:54 test_ok<br>
drwxr-sr-x 3 mbsdaq daq 4096 Jan 9 10:54 tests/<br>
drwxr-sr-x 2 mbsdaq daq 4096 Jan 9 10:55 tools/<br>
drwxr-sr-x 2 mbsdaq daq 4096 Jan 8 14:28 util/</div>
<br>
</div>
<p></p>
<p><br>
</p>
<p>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?</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
<p><br>
</p>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
<b>Gesendet:</b> Dienstag, 9. Januar 2024 11:31:34<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, Guenter Dr.<br>
<b>Betreff:</b> Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Dear Günter,<br>
<br>
On 2024-01-09 11:18, Weber, Guenter Dr. wrote:<br>
> Dear Hans, dear Hċkan,<br>
> <br>
> now the compilation was successful.<br>
<br>
*Thumbs up*<br>
<br>
> Side note:<br>
> <br>
> 'export VARIABLE_NAME=VARIABLE_VALUE' did not work on our RIO4. Instead <br>
> 'setenv VARIABLE_NAME VARIABLE_VALUE' needed to be used. Probably, this <br>
> due to not using bash but tcsh (for whatever reason).<br>
<br>
If I remember correctly, the historical reason was to easily have the <br>
.bashrc for normal systems and the .tcshrc for DAQ systems.<br>
<br>
> Now I updated the NURDLIB, right? To check if it actually works with the <br>
> hardware present, I would now need to run the DAQ and have a look at the <br>
> output data.<br>
<br>
You also need to rebuild the f-user. Nurdlib provides the library to <br>
read out hardware, the f-user is the piece of code between nurdlib and <br>
the DAQ backend, in this case drasi.<br>
So, something like:<br>
<br>
cp -r r3bfuser r3bfuser.20240109 # Backup!<br>
cd r3bfuser<br>
rm -rf build_*<br>
make drasi<br>
<br>
I'm pretty sure that r3bfuser looks for nurdlib in "../nurdlib/".<br>
<br>
> Will DRASI automatically work with the new NURDLIB or do I need to <br>
> compile it again?<br>
<br>
This would solved with the r3bfuser rebuild :)<br>
Eventually, once this nurdlib business is settled, you could consider <br>
updating drasi too. It's good practice, updating and backing things up.<br>
<br>
> Will also UCESB automatically adapt to the new NURDLIB or do I need to <br>
> compile it again?<br>
<br>
Should be fine as is.<br>
<br>
> (I am a bit puzzled by the fact that it is <br>
> '~/mbsrun/rio4/mcalstruck/ucesb/...' and not <br>
> '~/mbsrun/rio4/2023_mcalstruck/ucesb/...'. This seems to be inconsistent.)<br>
<br>
Feel free to play around, again once the nurdlib stuff is done!<br>
<br>
> Moreover, I found the following environment variables that (to my <br>
> understanding) tell the various parts of the DAQ software where it can <br>
> find some necessary stuff:<br>
> <br>
> TRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii<br>
> TRIDI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/bin_ppc-linux_4.2.2/tridi_ctrl<br>
> TRIMI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trimictrl/bin_ppc-linux_4.2.2/trimictrl<br>
> TRLOII_FLASH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/flash/bin_ppc-linux_4.2.2/vulomflash<br>
> VULOM4_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/bin_ppc-linux_4.2.2/trlo_ctrl<br>
> EXP_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck<br>
> HTOOLS_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/htools<br>
> <br>
> As I copied the complete folder structure of '2023_mcalstruck' to <br>
> '2024_mcalstruck', to be consistent I will redefine all this variables <br>
> to point to the new folder.<br>
<br>
Good idea, and eventually you may want to automate this with a set of <br>
other scripts for future DAQ:s :)<br>
<br>
> Best greetings from Jena<br>
> <br>
> Günter<br>
Cheers,<br>
Hans<br>
-- <br>
subexp-daq mailing list<br>
subexp-daq@lists.chalmers.se<br>
<a href="https://lists.chalmers.se/mailman/listinfo/subexp-daq">https://lists.chalmers.se/mailman/listinfo/subexp-daq</a><br>
</div>
</span></font>
</body>
</html>