After inserting the camera driver using insmod, I can stream successfully. However, when I stop the streaming and start it again, it throws an uncorr_error. Below is the error log:
I have probed the MIPI data from the deserializer, and it appears to be working correctly. My main concern is about the platform board. I have boosted all the clocks and run the Jetson clock utility, but the issue still persists.
I am using a 6.4 Gbps MIPI output data rate from the deserializer.
I have applied the kernel patch from this Topic 305007
Whenever I stop the initial streaming and start it again, it throws an uncorr_error. Additionally, I cannot switch resolutions during the first streaming. The same error persists.
After this, I removed the driver using rmmod and reloaded it using insmod. I successfully started the initial streaming again, but stopping and restarting it results in the same uncorr_error. The issue remains consistent.
I stopped the first-time streaming and started it again, it throws an uncorr_error. After resetting the SerDes, I was able to stream.
For subsequent attempts, if I start the stream within 5 seconds, it works fine. However, if I start the stream after 5 seconds, I need to reset the SerDes every time to get the stream.
Is it necessary to perform a full reset of the SerDes every time to get the stream?
thanks for issue narrow down, it’s helpful information.
it’s camera firmware driver looking for camera initialization sequence (i.e. LP sequence), and it’s output data-rate to determine whether it needs to wait for skew calibration; it’ll enable pixel parser when deskew calibration has completed.
hence… it’s necessary for SerDes use-case.