that’s expected since it’s software to duplicate single capture event to these two camera driver.
if one of the camera failed to output a complete frame, it’s making syncpt timeout error from the low-level driver side, this also cause user-space cannot program the capture buffer.
may I know what’s the reason of this camera failed?
thanks
Hi, JerryChange:
I don’t mean that we are now encountering the problem of one camera failed.
What I mean is if one camera occasionally drop frame or failed, due to external factors such as hardware or emc, I hope that it not affect the other camera.
as I mentioned in comment #3, it’s software stack to expect the camera stream sending without failures continuously.
there’s implementation for Argus error resiliency,
please refer to Topic 170086, if you’re using JetPack-4.3; the later JetPack release has already include the changes.
however, it’s still need to confirm what’s the failure in the actual use-case.
it cannot avoid the camera stack to report failure if you’re having hardware issue, such as losing camera connections.
thanks