<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 <span>Hċkan,</span></p>
<p><span><br>
</span></p>
<p><span>I followed your suggestion and the result is this:</span></p>
<p><span><br>
</span></p>
<p><span></p>
<div><span style="font-size:10pt">RIO4-MCAL-2 mbsdaq > make drasi</span><br>
<span style="font-size:10pt">rm -f build_cc_ppc-linux_4.2.2_debug</span><br>
<span style="font-size:10pt">[ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p build_cc_ppc-linux_4.2.2_debug_drasi</span><br>
<span style="font-size:10pt">ln -s build_cc_ppc-linux_4.2.2_debug_drasi build_cc_ppc-linux_4.2.2_debug</span><br>
<span style="font-size:10pt">make -f Makefile.drasi</span><br>
<span style="font-size:10pt">make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'</span><br>
<span style="font-size:10pt">CC build_cc_ppc-linux_4.2.2_debug/subevent.o</span><br>
<span style="font-size:10pt">In file included from ./subevent.h:11,</span><br>
<span style="font-size:10pt"> from subevent.c:1:</span><br>
<span style="font-size:10pt">/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/s_veshe.h:16: error: expected specifier-qualifier-list before 'CHARS'</span><br>
<span style="font-size:10pt">make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1</span><br>
<span style="font-size:10pt">make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'</span><br>
<span style="font-size:10pt">make: *** [drasi] Error 2</span><br>
</div>
<br>
</span>
<p></p>
<p><span><br>
</span></p>
<p><span>Best greetings</span></p>
<p><span>Günter<br>
</span></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 Hċkan T Johansson <f96hajo@chalmers.se><br>
<b>Gesendet:</b> Mittwoch, 10. Januar 2024 16:07:52<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<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"><br>
Dear Günter,<br>
<br>
those errors look strange to me. I am not able to reproduce on a similar <br>
system.<br>
<br>
As a workaround (to see how far we get), in subevent.h in the r3bfuser/ <br>
directory, could you uncomment these:<br>
<br>
#define MBS_TYPEDEFS_H<br>
typedef char CHARX;<br>
typedef int short INTS2;<br>
typedef int INTS4;<br>
<br>
and comment out the "typedefs.h" in<br>
<br>
/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/s_veshe.h<br>
<br>
on line 6. And then try again.<br>
<br>
Cheers,<br>
Hċkan<br>
<br>
<br>
On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear Hans,<br>
> <br>
> <br>
> I now did rebuild NURDLIB and DRASI. Then I tried to compile R3BFUSER and this is the result:<br>
> <br>
> <br>
> RIO4-MCAL-2 mbsdaq > cd r3bfuser/<br>
> 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>
> make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
> NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args<br>
> UDP:ARPA_INET_H<br>
> CC build_cc_ppc-linux_4.2.2_debug/f_user.o<br>
> CC build_cc_ppc-linux_4.2.2_debug/subevent.o<br>
> In file included from /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/s_veshe.h:6,<br>
> from ./subevent.h:11,<br>
> from subevent.c:1:<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:6: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTS8'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:7: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTU8'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:8: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTS4'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:9: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTU4'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTS2'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:11: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTU2'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:12: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTS1'<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/typedefs.h:13: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'INTU1'<br>
> In file included from ./subevent.h:11,<br>
> from subevent.c:1:<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/s_veshe.h:11: error: expected specifier-qualifier-list before 'INTS4'<br>
> subevent.c: In function 'begin_goosy_vme_subevent':<br>
> subevent.c:12: error: 's_veshe' has no member named 'l_dlen'<br>
> subevent.c: In function 'end_goosy_vme_subevent':<br>
> subevent.c:45: error: 's_veshe' has no member named 'l_dlen'<br>
> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1<br>
> make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
> make: *** [drasi] Error 2<br>
> <br>
> Reminder: I am using the most recent versions of NURDLIB and DRASI, but because of the incompatibility of the VULOM firmware I use the old version of TRLOII. In addition,<br>
> because of the leap seconds issue I compiled DRASI first on the PC and then recompiled it on the RIO (without "make clean").<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Best greetings<br>
> Günter<br>
> <br>
> <br>
> __________________________________________________________________________________________________________________________________________________________________________<br>
> Von: Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
> Gesendet: Mittwoch, 10. Januar 2024 13:18:41<br>
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, Guenter Dr.<br>
> Betreff: Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version <br>
> Dear Günter,<br>
> <br>
> I would suggest rebuilding nurdlib now that trlo2 has been rebuilt, and<br>
> then also rebuild r3bfuser.<br>
> <br>
> After that probably you can try to run the DAQ :)<br>
> <br>
> Cheers,<br>
> Hans<br>
> <br>
> On 2024-01-10 13:15, Weber, Guenter Dr. wrote:<br>
> > Dear Hċkan,<br>
> ><br>
> ><br>
> > using the old TRLOII folder and then recompiling was successfull.<br>
> ><br>
> ><br>
> > Should I now give it a try to start the DAQ? Or is there something else<br>
> > I still need to adjust?<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Best greetings<br>
> ><br>
> > Günter<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ------------------------------------------------------------------------<br>
> > *Von:* subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von<br>
> > Hċkan T Johansson <f96hajo@chalmers.se><br>
> > *Gesendet:* Mittwoch, 10. Januar 2024 12:34:26<br>
> > *An:* Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> > *Betreff:* Re: [subexp-daq] NURDLIB: - how to check which version is<br>
> > installed and how to update to the most recent version<br>
> ><br>
> > Hi Günter,<br>
> ><br>
> > On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:<br>
> ><br>
> >><br>
> >> Hi folks,<br>
> >><br>
> >><br>
> >> the old "./find_firmware.pl" was working. This is the output:<br>
> >><br>
> >><br>
> >> a1729cda ../ver/rimfaxe0_trlo/rfx0_defs.h<br>
> >> 0866c243 ../ver/rimfaxe1_trlo/rfx1_defs.h<br>
> >> 5e8f5ef4 ../ver/tridi1_trlo/tridi_defs.h<br>
> >> 6e4ba1a9 ../ver/vulom4_trlo/trlo_defs.h<br>
> >> 68f8955e ../ver/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
> >> af33ed35 ../ver/vulom4_trlo_big/trlo_big_defs.h<br>
> >> 1409285e ../ver/vulom4b_trlo/trlo_defs.h<br>
> >> d374466d ../fw/tridi1_trlo/tridi_defs.h<br>
> >> d96ffc88 ../fw/vulom4_trlo/trlo_defs.h<br>
> >> 5b298165 ../fw/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
> >> 6f28c0f8 ../fw/vulom4_trlo_big/trlo_big_defs.h<br>
> >> fa5020ea ../fw/vulom4_trlo_led/trlo_defs.h<br>
> >> 426cb99c ../fw/vulom4b_trlo/trlo_defs.h<br>
> >> MKDIR fw_a1729cda_rfx0 # ../ver/rimfaxe0_trlo/rfx0_defs.h<br>
> >> SYMLINK fw_a1729cda_rfx0/rfx0_defs.h -> ../../ver/rimfaxe0_trlo/rfx0_defs.h<br>
> >> MKDIR fw_0866c243_rfx1 # ../ver/rimfaxe1_trlo/rfx1_defs.h<br>
> >> SYMLINK fw_0866c243_rfx1/rfx1_defs.h -> ../../ver/rimfaxe1_trlo/rfx1_defs.h<br>
> >> MKDIR fw_5e8f5ef4_tridi # ../ver/tridi1_trlo/tridi_defs.h<br>
> >> SYMLINK fw_5e8f5ef4_tridi/tridi_defs.h -> ../../ver/tridi1_trlo/tridi_defs.h<br>
> >> MKDIR fw_6e4ba1a9_trlo # ../ver/vulom4_trlo/trlo_defs.h<br>
> >> SYMLINK fw_6e4ba1a9_trlo/trlo_defs.h -> ../../ver/vulom4_trlo/trlo_defs.h<br>
> >> SYMLINK fw_1409285e_trlo -> fw_6e4ba1a9_trlo<br>
> >> MKDIR fw_68f8955e_trlo_all_in # ../ver/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
> >> SYMLINK fw_68f8955e_trlo_all_in/trlo_all_in_defs.h -> ../../ver/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
> >> MKDIR fw_af33ed35_trlo_big # ../ver/vulom4_trlo_big/trlo_big_defs.h<br>
> >> SYMLINK fw_af33ed35_trlo_big/trlo_big_defs.h -> ../../ver/vulom4_trlo_big/trlo_big_defs.h<br>
> >> MKDIR fw_d374466d_tridi # ../fw/tridi1_trlo/tridi_defs.h<br>
> >> SYMLINK fw_d374466d_tridi/tridi_defs.h -> ../../fw/tridi1_trlo/tridi_defs.h<br>
> >> MKDIR fw_d96ffc88_trlo # ../fw/vulom4_trlo/trlo_defs.h<br>
> >> SYMLINK fw_d96ffc88_trlo/trlo_defs.h -> ../../fw/vulom4_trlo/trlo_defs.h<br>
> >> SYMLINK fw_426cb99c_trlo -> fw_d96ffc88_trlo<br>
> >> SYMLINK fw_fa5020ea_trlo -> fw_d96ffc88_trlo<br>
> >> MKDIR fw_5b298165_trlo_all_in # ../fw/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
> >> SYMLINK fw_5b298165_trlo_all_in/trlo_all_in_defs.h -> ../../fw/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
> >> MKDIR fw_6f28c0f8_trlo_big # ../fw/vulom4_trlo_big/trlo_big_defs.h<br>
> >> SYMLINK fw_6f28c0f8_trlo_big/trlo_big_defs.h -> ../../fw/vulom4_trlo_big/trlo_big_defs.h<br>
> >><br>
> >> However, the compilation did end with an error:<br>
> >><br>
> >><br>
> >> make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo'<br>
> >> CC bld_ppc-linux_4.2.2/src/trlo_check_version.o<br>
> >> CC bld_ppc-linux_4.2.2/src/trlo_functions.o<br>
> >> ../trlolib/src/trlo_functions.c: In function 'trlo_clear_config':<br>
> >> ../trlolib/src/trlo_functions.c:144: error: 'trlo_setup_map' has no member named 'sync_check_start_mux'<br>
> >> ../trlolib/src/trlo_functions.c:146: error: 'trlo_setup_map' has no member named 'sync_check_stop_mux'<br>
> >> ../trlolib/src/trlo_functions.c: In function 'trlo_print_config':<br>
> >> ../trlolib/src/trlo_functions.c:825: error: 'trlo_setup_map' has no member named 'sync_check_start_mux'<br>
> >> ../trlolib/src/trlo_functions.c:829: error: 'trlo_setup_map' has no member named 'sync_check_stop_mux'<br>
> >> ../trlolib/src/trlo_functions.c: In function 'trlo_print_trig_status':<br>
> >> ../trlolib/src/trlo_functions.c:1155: error: 'trlo_output_map' has no member named 'trig_sync_check'<br>
> >> make[1]: *** [bld_ppc-linux_4.2.2/src/trlo_functions.o] Error 1<br>
> >> make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo'<br>
> >><br>
> >> make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi'<br>
> >> CC bld_ppc-linux_4.2.2/src/tridi_check_version.o<br>
> >> CC bld_ppc-linux_4.2.2/src/tridi_functions.o<br>
> >> ../trlolib/src/trlo_functions.c: In function 'tridi_clear_config':<br>
> >> ../trlolib/src/trlo_functions.c:144: error: 'tridi_setup_map' has no member named 'sync_check_start_mux'<br>
> >> ../trlolib/src/trlo_functions.c:146: error: 'tridi_setup_map' has no member named 'sync_check_stop_mux'<br>
> >> ../trlolib/src/trlo_functions.c: In function 'tridi_print_config':<br>
> >> ../trlolib/src/trlo_functions.c:825: error: 'tridi_setup_map' has no member named 'sync_check_start_mux'<br>
> >> ../trlolib/src/trlo_functions.c:829: error: 'tridi_setup_map' has no member named 'sync_check_stop_mux'<br>
> >> ../trlolib/src/trlo_functions.c: In function 'tridi_print_trig_status':<br>
> >> ../trlolib/src/trlo_functions.c:1155: error: 'tridi_output_map' has no member named 'trig_sync_check'<br>
> >> make[1]: *** [bld_ppc-linux_4.2.2/src/tridi_functions.o] Error 1<br>
> >> make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi'<br>
> >> make: *** [fw_d374466d_tridi_build] Error 2<br>
> ><br>
> > That's what I feared. The new code want something (sync_check_...) not in<br>
> > the older firmware...<br>
> ><br>
> >> The fallback option is now to delete the new TRLOII folder and replace it with old one and then repeat the following steps?<br>
> >><br>
> >><br>
> >> cd trloii<br>
> >> make clean<br>
> >> make<br>
> >> cd trloctrl<br>
> >> make fw_d96ffc88_trlo_build<br>
> >> make fw_d374466d_tridi_build<br>
> >><br>
> >><br>
> >> Is this correct?<br>
> ><br>
> > Yes.<br>
> ><br>
> > There should then already be the trloii/fw/ directory, and the links that<br>
> > are created by find_firmware.pl<br>
> ><br>
> ><br>
> >> I also looked for the "--addr=" and this is the result:<br>
> ><br>
> >> ...<br>
> ><br>
> > Ok. I was too optimistic here. I looked through the grep results, but<br>
> > nothing obvious. Should be figurable by checking the old scripts and<br>
> > following them around. Is a good way to see how things are done anyhow ;)<br>
> ><br>
> > Cheers,<br>
> > Hċkan<br>
> ><br>
> ><br>
> >><br>
> >><br>
> >><br>
> >> Best greetings<br>
> >><br>
> >> Günter<br>
> ><br>
> <br>
></div>
</span></font>
</body>
</html>