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
At 320x32 resolution with max fps, some frames are excessively bright. This only happened at max fps, and only after a reboot.
It went away after switching to another resolution and back to 320x32 resolution with max fps.
It also did not occur with fps lowered to 20k, even after a reboot.
tested on 0.4.0-beta27, FPGA revision 3.24
The text was updated successfully, but these errors were encountered:
skronstein
added
the
p2
This issue will impact most users of the camera, but the camera is still usable.
label
Mar 16, 2020
These "bright flashes" can be recorded and they will show up in video memory like normal frames. However, when you observe them they are actually just random data, which tends to make them brighter than the valid frames thanks to FPN correction.
The frequency at which they occur seems to be related to the recording speed of the camera, and there appears to be something stateful about this corruption. Switching framerate and back will sometimes make the camera come good, after which no corruption will occur. When examining the register maps of the FPGA and camera both in the good and corrupted states shows identical register mappings.
I suspect that this is more likely due to some kind of race condition in the FPGA, either in the recording sequencer or the deserializer that is getting the write addresses wrong, and it is simply unable to handle these extreme framerates without triggering the bug.
At 320x32 resolution with max fps, some frames are excessively bright. This only happened at max fps, and only after a reboot.
It went away after switching to another resolution and back to 320x32 resolution with max fps.
It also did not occur with fps lowered to 20k, even after a reboot.
tested on 0.4.0-beta27, FPGA revision 3.24
The text was updated successfully, but these errors were encountered: