[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
Thu Jan 11 11:23:50 CET 2024
Dear Håkan, dear Hans,
ok, so the problem is that we would need to update the firmware of the VULOM to make it work with the new TRLOII software, which in turn is probably needed to avoid the problem when compiling R3BFUSER? Is this correct?
So, I will set up a system with identical hardware, copy the software from the present system and then the first step would be to update the VULOM firmware on the new system?
Best greetings
Günter
________________________________
Von: Håkan T Johansson <f96hajo at chalmers.se>
Gesendet: Donnerstag, 11. Januar 2024 08:15:14
An: Weber, Guenter Dr.
Cc: Hans Toshihide Törnqvist
Betreff: Re: AW: AW: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version
Dear Günter,
thanks!
1) may be the reason for that strange error in typedefs.h, since it may be
that it picks up the mystdint.h from the trloii compile but uses it in the
drasi header somehow - or vice versa.... (They are the same and typically
kept in sync, but we may here have hit a snag with the different versions
and an update I did a while ago...)
2) Should be fine, is just an attempt at indenting the pre-processor
directives, without having my editor unindent the code.
It sounds like a very nice plan if you have the hardware to set up a
second system from scratch. I have attached a short instruction on how to
downloading and compiling the codes from scratch.
It would not surprise me if there already exist something like that, but
then we have two of them :-) If not, we can put this (with whatever fixes
are needed) up somewhere (gitlab wiki or so).
I did test it - but that does not guarantee much...
Cheers,
Håkan
On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:
>
> P.S. I looked a bit into the code that is compiled right before the error
> appear.
>
>
> I have no idea if this might causing problems, but in
>
> ../dtc_arch/acc_def/mystdint.h
> I found two things:
>
>
> 1)
>
> New version:
>
> #if ACC_DEF__MYSTDINT_stdint_h
> # include <stdint.h>
> #endif
> /* This is a local fall-back solution, so should be last. */
> #if ACC_DEF__MYSTDINT_mystdint
>
> Old version:
>
> #if ACC_DEF_MYSTDINT_stdint_h
> # include <stdint.h>
> #endif
> /* This is a local fall-back solution, so should be last. */
> #if ACC_DEF_MYSTDINT_mystdint
>
> (Note the double "_" before MYSTDINT.)
>
>
> 2)
>
> In both versions there are strange blanks after "#" at two positions:
>
> # include "acc_auto_def/mystdint.h"
> # define UINT64_C(v) v##ULL
>
>
>
> Best greetings
>
> Günter
>
>
> ____________________________________________________________________________
> Von: Weber, Guenter Dr.
> Gesendet: Mittwoch, 10. Januar 2024 19:32:59
> An: Hans Toshihide Törnqvist
> Betreff: AW: AW: [subexp-daq] NURDLIB: - how to check which version is
> installed and how to update to the most recent version
>
> Dear Hans,
>
>
> I could not reproduce the error from two hours ago. Nurdlib was laready set
> to the right branch and in a second try compiled without problems on the
> RIO.
>
>
> However, we are now back at square one:
>
>
> 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
> make[1]: Entering directory
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args
> UDP:ARPA_INET_H
> CC build_cc_ppc-linux_4.2.2_debug/f_user.o
> CC build_cc_ppc-linux_4.2.2_debug/subevent.o
> In file included from/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> s_veshe.h:6,
> from ./subevent.h:11,
> from subevent.c:1:
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:6: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS8'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:7: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU8'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:8: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS4'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:9: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU4'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:10: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS2'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:11: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU2'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:12: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS1'
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:13: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU1'
> In file included from ./subevent.h:11,
> from subevent.c:1:
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> s_veshe.h:11: error: expected specifier-qualifier-list before 'INTS4'
> subevent.c: In function 'begin_goosy_vme_subevent':
> subevent.c:12: error: 's_veshe' has no member named 'l_dlen'
> subevent.c: In function 'end_goosy_vme_subevent':
> subevent.c:45: error: 's_veshe' has no member named 'l_dlen'
> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1
> make[1]: Leaving directory
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> make: *** [drasi] Error 2
> RIO4-MCAL-2 mbsdaq >
>
> Thus, downloading and recompiling DRASI, NURDLIB, and R3BFUSER did not solve
> the problem with the latter.
>
>
>
> 😞
>
>
>
>
>
>
> Best greetings
>
> Günter
>
>
>
>
> ____________________________________________________________________________
> Von: Hans Toshihide Törnqvist <hans.tornqvist at chalmers.se>
> Gesendet: Mittwoch, 10. Januar 2024 18:24:21
> An: Weber, Guenter Dr.
> Betreff: Re: AW: [subexp-daq] NURDLIB: - how to check which version is
> installed and how to update to the most recent version
> Sorry I got held up.
>
> I compiled 'mcal_daq_merge' from Gitlab on a rio4 just fine, so I am
> just as puzzled where those event buffer test errors come from...
>
> Any luck with a 'make clean && make'?
>
> Cheers,
>
> Hans
>
> On 2024-01-10 17:36, Weber, Guenter Dr. wrote:
> > Dear Hans,
> >
> >
> > now things really get weird.
> >
> >
> > I again downloaded NURDLIB, DRASI, and R3BFUSER. DRASI compiled without
> > problems (first on PC, then on RIO).
> >
> >
> > Now NURDLIB compilation stops with an error:
> >
> >
> > LD build_cc_ppc-linux_4.2.2_debug/test_ntest
> > LD build_cc_ppc-linux_4.2.2_debug/test
> > /bin/sh: line 1: 22504 Aborted
> > ./build_cc_ppc-linux_4.2.2_debug/test >
> > build_cc_ppc-linux_4.2.2_debug/test.log 2>&1
> > [tests/argmatch.c:127: Shorts]
> > [tests/argmatch.c:128: Longs]
> > [tests/argmatch.c:129: Combos]
> > [tests/argmatch.c:130: ShortsWithValues]
> > [tests/argmatch.c:131: LongsWithValues]
> > [tests/argmatch.c:132: MissingValue]
> > [tests/base.c:110: MemoryCheck]
> > [tests/base.c:111: EventBufferAdvance]
> > 2024-02-10,19:58:33:ERRR: Invalid pointer to advance event buffer.
> > [tests/base.c:47]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:47]
> > 2024-02-10,19:58:33:ERRR: Invalid pointer to advance event buffer.
> > [tests/base.c:56]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:56]
> > 2024-02-10,19:58:33:ERRR: Tried to advance outside event buffer.
> > [tests/base.c:72]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:72]
> > [tests/base.c:112: EventBufferInvariant]
> > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e008:11 !=
> > 0x1080e008:10). [tests/base.c:87]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:87]
> > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e008:9 !=
> > 0x1080e008:10). [tests/base.c:91]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:91]
> > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e009:10 !=
> > 0x1080e008:10). [tests/base.c:95]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:95]
> > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e007:10 !=
> > 0x1080e008:10). [tests/base.c:99]
> > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:99]
> > [tests/bits.c:43: Gets]
> > [tests/bits.c:44: CountLoops]
> > [tests/caen_v1190.c:79: DefaultConfig]
> > 2024-02-10,19:58:33:INFO: Will try default cfg
> > path='/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg',
> > can be set with NURDLIB_DEF_PATH. [config/config.c:181]
> > 2024-02-10,19:58:33:INFO: Opened './tests/caen_v1190_empty.cfg' {
> > [config/parser.c:287]
> > 2024-02-10,19:58:33:ERRR: .Could not load default or user config
> > 'caen_v1190.cfg'. [config/config.c:1483]
> > 2024-02-10,19:58:33:ERRR: .Calling abort()... [config/config.c:1483]
> > make: *** [build_cc_ppc-linux_4.2.2_debug/test_ok] Error 1
> >
> >
> > Did you change anything in the GITLAB version between yesterday and 15
> > minutes ago?
> >
> >
> >
> > Sorry, sorry, sorry 😞
> >
> >
> >
> >
> > Best greetings
> >
> > Günter
> >
> >
> >
> > P.S. Tomorrow or on Friday, I will set up a second DAQ system with
> > identical hardware. Then we can play around with no limits, including
> > flashing the firmware of the VULOM, without messing around with the
> > already running system as it is the case now.
> >
> >
> > ------------------------------------------------------------------------
> > *Von:* Hans Toshihide Törnqvist <hans.tornqvist at chalmers.se>
> > *Gesendet:* Mittwoch, 10. Januar 2024 16:59:07
> > *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,
> >
> > Did you try to update r3bfuser? I cannot see this problem with new
> > versions of drasi+nurdlib+r3bfuser that are on Gitlab, and the trloii
> > version shouldn't matter much in this case.
> >
> > Cheers,
> >
> > Hans
> >
> > On 2024-01-10 16:54, Weber, Guenter Dr. wrote:
> >> Dear Håkan,
> >>
> >>
> >> I followed your suggestion and the result is this:
> >>
> >>
> >> 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
> >> make[1]: Entering directory
> >> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> >> CC build_cc_ppc-linux_4.2.2_debug/subevent.o
> >> In file included from ./subevent.h:11,
> >> from subevent.c:1:
> >>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> s_veshe.h:16: error: expected specifier-qualifier-list before 'CHARS'
> >> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1
> >> make[1]: Leaving directory
> >> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> >> make: *** [drasi] Error 2
> >>
> >>
> >> 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 16:07:52
> >> *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,
> >>
> >> those errors look strange to me. I am not able to reproduce on a similar
> >> system.
> >>
> >> As a workaround (to see how far we get), in subevent.h in the r3bfuser/
> >> directory, could you uncomment these:
> >>
> >> #define MBS_TYPEDEFS_H
> >> typedef char CHARX;
> >> typedef int short INTS2;
> >> typedef int INTS4;
> >>
> >> and comment out the "typedefs.h" in
> >>
> >>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> s_veshe.h
> >>
> >> on line 6. And then try again.
> >>
> >> Cheers,
> >> Håkan
> >>
> >>
> >> On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:
> >>
> >>>
> >>> Dear Hans,
> >>>
> >>>
> >>> I now did rebuild NURDLIB and DRASI. Then I tried to compile R3BFUSER
> and this is the result:
> >>>
> >>>
> >>> RIO4-MCAL-2 mbsdaq > cd r3bfuser/
> >>> 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
> >>> make[1]: Entering directory
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> >>> NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args
> >>> UDP:ARPA_INET_H
> >>> CC build_cc_ppc-linux_4.2.2_debug/f_user.o
> >>> CC build_cc_ppc-linux_4.2.2_debug/subevent.o
> >>> In file included from/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> s_veshe.h:6,
> >>> from ./subevent.h:11,
> >>> from subevent.c:1:
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:6: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS8'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:7: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU8'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:8: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS4'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:9: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU4'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:10: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS2'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:11: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU2'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:12: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTS1'
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> typedefs.h:13: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'INTU1'
> >>> In file included from ./subevent.h:11,
> >>> from subevent.c:1:
> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/
> s_veshe.h:11: error: expected specifier-qualifier-list before 'INTS4'
> >>> subevent.c: In function 'begin_goosy_vme_subevent':
> >>> subevent.c:12: error: 's_veshe' has no member named 'l_dlen'
> >>> subevent.c: In function 'end_goosy_vme_subevent':
> >>> subevent.c:45: error: 's_veshe' has no member named 'l_dlen'
> >>> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1
> >>> make[1]: Leaving directory
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'
> >>> make: *** [drasi] Error 2
> >>>
> >>> 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,
> >>> because of the leap seconds issue I compiled DRASI first on the PC and
> then recompiled it on the RIO (without "make clean").
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Best greetings
> >>> Günter
> >>>
> >>>
> >>>___________________________________________________________________________
> __________________________________________________________________________
> _____________________
> >>> Von: Hans Toshihide Törnqvist <hans.tornqvist at chalmers.se>
> >>> Gesendet: Mittwoch, 10. Januar 2024 13:18:41
> >>> 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,
> >>>
> >>> 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_d96ff
> c88_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_d96ff
> c88_trlo'
> >>> >>
> >>> >> make[1]: Entering directory`/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d3744
> 66d_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_d3744
> 66d_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
> >>> >
> >>>
> >>>
> >>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chalmers.se/pipermail/subexp-daq/attachments/20240111/0bf1b57c/attachment-0001.html>
More information about the subexp-daq
mailing list