From 16e9b272c7c6038439fd14347e8ae8e720016e0b Mon Sep 17 00:00:00 2001 From: Dhanya Thattil Date: Mon, 7 Nov 2022 12:49:04 +0100 Subject: [PATCH] release notes --- RELEASE.txt | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/RELEASE.txt b/RELEASE.txt index 50a6f3345..454cf6e00 100644 --- a/RELEASE.txt +++ b/RELEASE.txt @@ -107,10 +107,14 @@ This document describes the differences between v7.0.0 and v6.x.x - ctb, moench, jungfrau (pll reset at start fixed, before no defines) - pybind built into package, no need to update submodule when previous release had different pybind version - adcvpp moved from dac.. and api added (ctb, moench) -- eiger server fix (eiger server: fix for fw workaround where stop acquisition processing done signal does not come up, by removing reset in stop acquisition and waiting for2 seconds for feb done processing signal to go down, if it doesnt, throw if status is not idle. -error messages not setup for some eiger server errors -quad fix (chip signals to trim quad, both left and right registers can be different) -minor logical error of no consequence (stop acquisition returns a different enum than expected)) +- eiger (removed feb reset in stop acquisition as it caused processing bit to randomly not go high (leads to infinite loop waiting for it to go high). This is anyway done at prepare acquisition and set trimbits. + - left AND right registers monitored for processing bit done + - febProcessinginprogress returns STATUS_IDLE and not IDLE + - In feb stop acquisition, if processing bit is running forever, checks for 1 s, then if acq done bit is high, returns ok, else throws + - feb stop acquisition returns 1 if success and fucntion in list calling it compares properly instead of STATUS_IDLE (no effect, but incorrect logic) + - chipsignals to trimquad should only monitor right fpga (not both as it will throw) + - fixed error messages of readregister inconsistent values + - setmodule and read frame was returning fail without setting error messages (leading to broken tcp connection due to no error message) ) - 2. Resolved Issues