[subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version

Wed Jan 10 13:18:41 CET 2024

Dear Günter,

I would suggest rebuilding nurdlib now that trlo2 has been rebuilt, and 
then also rebuild r3bfuser.

After that probably you can try to run the DAQ :)

Cheers,
Hans

On 2024-01-10 13:15, Weber, Guenter Dr. wrote:
> Dear Håkan,
> 
> 
> using the old TRLOII folder and then recompiling was successfull.
> 
> 
> Should I now give it a try to start the DAQ? Or is there something else 
> I still need to adjust?
> 
> 
> 
> 
> 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:* Mittwoch, 10. Januar 2024 12:34:26
> *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
> 
> Hi Günter,
> 
> On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:
> 
>> 
>> 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
> 
> That's what I feared.  The new code want something (sync_check_...) not in
> the older firmware...
> 
>> 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?
> 
> Yes.
> 
> There should then already be the trloii/fw/ directory, and the links that
> are created by find_firmware.pl
> 
> 
>> I also looked for the "--addr=" and this is the result:
> 
>> ...
> 
> Ok.  I was too optimistic here.  I looked through the grep results, but
> nothing obvious.  Should be figurable by checking the old scripts and
> following them around.  Is a good way to see how things are done anyhow ;)
> 
> Cheers,
> Håkan
> 
> 
>> 
>> 
>> 
>> Best greetings
>> 
>> Günter
> 