We have two coupled image sensors (IMX290) connected via FPD-III to CSI, where one sensor acts as a Master and provides synchronized clocking (HSYNC, VSYNC) to the slave sensor. Reason is to have a good-quality stereo capture where both sensors are recording images at exactly the same time.
However, we find that we are having difficulties starting both captures simultaneously because LIBARGUS hits a timeout on the slave sensor. The slave is likely to require some more time to synchronize to the external XVS than the master sensor which just runs when started.
The same setup has worked nicely with R28.1/2 but is no longer working with R32.1. We have seen that there is a new “set_mode_delay_ms” property in the DTB but no similar “start_delay_ms” or a more general “max_frame_delay_ms” property to configure such requirements. This would be vital in our application!
The error recovery capabilities of the NVidia camera software stack have not improved at all between releases: when ever a single frame gets missing somehow, the whole software stack just hangs and must forcedly be killed. If the application links against libargus (which is said to be preferred to using the gstreamer plugin), the application must kill and restart itself. Sometimes one must wait a few minutes in between to allow hardware timeouts to trigger so that a new capture can start cleanly. Sometimes even a reboot seems to be required to get the ISP running again. Please improve on that, this is not production-quality software!