FMC ADC 100M 14b 4cha - Gateware issueshttps://ohwr.org/project/fmc-adc-100m14b4cha-gw/issues2019-08-05T11:16:43Zhttps://ohwr.org/project/fmc-adc-100m14b4cha-gw/issues/21Expose more info in the status and/or interrupt registers2019-08-05T11:16:43ZDimitris LampridisExpose more info in the status and/or interrupt registersIn particular various error flags.
Taken from v4.0 gateware manual:
Add error flags to status reg (+interrupt?):
\- Instead of overwriting memory for a given acquisition.
\- If read during acquisition (or even block read during acq?).
Also, add over-heat and input over-load interrupts (from original
specification)V5.0 gateware releaseDimitris LampridisDimitris Lampridishttps://ohwr.org/project/fmc-adc-100m14b4cha-gw/issues/22Cannot use last DPRAM sample2019-08-05T11:16:41ZDimitris LampridisCannot use last DPRAM sampleIf in multi-shot mode an acquisition makes use of the full DPRAM, the
data is delivered to the host corrupt. The cause of this should be
investigated and fixed.
For now (release 4.1), there is a limit in place inside the gateware
which only allows for using "max-1" samples, effectively masking the bug
from the higher layers (driver, apps).V5.0 gateware releaseDimitris LampridisDimitris Lampridishttps://ohwr.org/project/fmc-adc-100m14b4cha-gw/issues/23Account for trigger sample in post-trigger samples2019-08-05T11:16:39ZDimitris LampridisAccount for trigger sample in post-trigger samplesThe "extra" trigger sample is a source of confusion during communication
between gateware, drivers and applications developers.
It makes much more sense to "absorb" the trigger sample into the
post-trigger samples. Thus, a post-samples value of 1 will mean that
only the trigger sample will be acquiredV5.0 gateware releaseDimitris LampridisDimitris Lampridis