You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 15, 2025. It is now read-only.
The bolo-pro-test script lives in a separate package, and is currently won't work if bolo8dsp.init from this package has been run. It relies on mm hacks to set BOLODSP registers, and doesn't work properly with the latest ACQ400 firmware versions unless parts of the bolo powerup script are run to properly initialise the BOLO8's DACs.
Moving the production test into this repository would enable the use of set.site 14 commands rather than mm. It would also provide a more logical home for the script, which requires a BOLODSP FPGA personality anyway.
It shouldn't be too difficult to provide a flag in the /mnt/local/sysconfig/bolo.sh file to indicate production test mode: something like BOLO_PRO_TEST=1 could set DSP_BYPASS=1 and nchan=16 per site with data32=0.
The
bolo-pro-testscript lives in a separate package, and is currently won't work if bolo8dsp.init from this package has been run. It relies on mm hacks to set BOLODSP registers, and doesn't work properly with the latest ACQ400 firmware versions unless parts of the bolo powerup script are run to properly initialise the BOLO8's DACs.Moving the production test into this repository would enable the use of
set.site 14commands rather thanmm. It would also provide a more logical home for the script, which requires a BOLODSP FPGA personality anyway.It shouldn't be too difficult to provide a flag in the
/mnt/local/sysconfig/bolo.shfile to indicate production test mode: something likeBOLO_PRO_TEST=1could setDSP_BYPASS=1andnchan=16per site withdata32=0.