<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:14pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Dear friends,</p>
<p><br>
</p>
<p>attached please find a script that automatically choses the right firmware for the VULOM.</p>
<p><br>
</p>
<p>If you find time, please have a look at it and tell me if you think it is useful or if there is any mistake.</p>
<p><br>
</p>
<p>On my system it works fine so far.</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Weber, Guenter Dr. <g.weber@hi-jena.gsi.de><br>
<b>Gesendet:</b> Dienstag, 20. Februar 2024 10:46:52<br>
<b>An:</b> Hans Toshihide Törnqvist; Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] Question on default firmware for VULOM</font>
<div> </div>
</div>
<div><style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:14pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Dear Hans,</p>
<p><br>
</p>
<p>just to close this issue, here is what we are doing now to set the VULOM to the right firmware. As it is possible that a DAQ system is operating with different software versions that also require different VULOM firmware, we now load the right firmware 'on-the-fly'
as part of the startup of the DAQ system. After loading of the firmware a short waiting time is necessary before the VULOM is ready again.</p>
<p><br>
</p>
<p>---------------------------------------------------<br>
</p>
<p><span># Obtain the right firmware</span><br>
</p>
<div>VULOM4_FW=`cat ${TRLOII_PATH}/fw/vulom4b_trlo/trlo_defs.h | grep MD5SUM_STAMP | sed 's/.*0x//'`<br>
export VULOM4_CTRL=$trloiipath/trloctrl/fw_${VULOM4_FW}_trlo/bin_${machine}_${version}/trlo_ctrl</div>
<br>
<p></p>
<p></p>
<div># setup local constants<br>
addr=3<br>
firmware_region=2<br>
<br>
# restarting the VULOM to set the correct firmware version<br>
echo "Restarting VULOM with firmware region" $firmware_region<br>
$TRLOII_PATH/bin/vulomflash --addr=$addr --restart=$firmware_region<br>
echo "Waiting for VULOM to answer..."<br>
exit_code=1<br>
while [ $exit_code -ne 0 ] ; do<br>
$TRLOII_PATH/bin/vulomflash --addr=$addr --read &> /dev/null<br>
exit_code=$?<br>
if [ $exit_code -ne 0 ] ; then<br>
sleep 1 #sleep for 1 sec before retrying<br>
fi<br>
done</div>
<p></p>
<p><br>
</p>
<div># Trigger on VULOM pulser <br>
$VULOM4_CTRL --addr=$addr --clear-setup --config=vulom.trlo standalone module_trigger</div>
<p></p>
<p>----------------------------------------------------<br>
</p>
<p><br>
</p>
<p>If we did understand the naming convention in "<span>bin/vulomflash --addr=$ADDR --readprogs" a bit better, we would probably also be able to estimate from the name/number of the firmware the right firmware region on the VULOM (and we could check if the
right firmware was already loaded). But at the moment, we set <span>firmware_region</span> by hand.</span></p>
<p><span><br>
</span></p>
<p><span>In the ideal world, we would then have an init script for the DAQ that takes care of the VULOM settings just by looking at the state of the software under
<span>TRLOII_PATH</span>. This could help our guys a lot who have no idea about all this stuff :-)<br>
</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span>Best greetings</span></p>
<p><span>Günter<br>
</span></p>
<p><br>
</p>
<br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
<b>Gesendet:</b> Montag, 19. Februar 2024 10:37:37<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, Guenter Dr.; Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] Question on default firmware for VULOM</font>
<div> </div>
</div>
<div>
<div dir="auto">Dear Günter,<br>
<br>
As I understand it, the firmware you would like to have has been flashed and tested quite a lot and seems to work?<br>
<br>
Then you can flash program area 0, but you will need the --force option too. Area 0 will only be flashed if the firmware in question has been flashed into another area, as in your present case.<br>
<br>
After that it will load after every power cycle.<br>
<br>
Cheers,<br>
Hans <br>
</div>
<br>
<br>
<div class="gmail_quote">
<div dir="auto">"Weber, Guenter Dr." <g.weber@hi-jena.gsi.de> skrev: (19 februari 2024 10:15:37 CET)</div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div id="divtagdefaultwrapper" style="font-size:14pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Dear friends,</p>
<p><br>
</p>
<p>I restarted the crate and now get the following error message when starting the DAQ:</p>
<p><br>
</p>
<p></p>
<div>10: crate/crate.c:923: .Slow-init module[0]=GSI_VULOM.<br>
LOG: TRLO: MD5SUM: 0x426cb99c (CT: 5bba6507 = 2018-10-07 19:56:55 UTC)<br>
WARNING: Known firmware (alias): 0x6e4ba1a9.<br>
WARNING: Known firmware (alias): 0x1409285e.<br>
WARNING: Known firmware (alias): 0xa73c5093.<br>
WARNING: Known firmware (alias): 0x6e4ba1a9.<br>
WARNING: Known firmware (alias): 0x1409285e.<br>
FATAL: TRLO firmware wrong: 0x426cb99c, expected 0x6e4ba1a9 or alias.</div>
<p></p>
<p><br>
</p>
<p>I assume that upon power-on the VULOM is booting with a default firmware that is not the one necessary to run with the most recent version of NURDLIB, etc.</p>
<p><br>
</p>
<p>How can I tell the VULOM which firmware version from its memory it should load as default?</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Thank you very much!</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>