We are using Jetson orin NX with the following setup.
-NVIDIA Orin NX
-Custom carrier board
-3 IMX477 Raspberry Pi HQ cameras connected via CSI ports
-L4T 35.4.1 (we also tested things on 35.5.0)
-Enabled resolution 4032x3040 at 30fps
We are experiencing a persistent issue where one of the IMX477 cameras drops out after a variable amount of time during recording.
The dropout occurs after as little as 10 seconds or as long as 5 hours. Initially, we saw deskew and CRC errors before the camera dropped out.
Then we tested some pixel clock adjustments. After setting the pixel clock to 840MHz (previously 300MHz, the CRC errors are no longer present. However, the camera still drops out randomly with this error which was present previously too alongside the CRC error.
I have some logs that we captured, couldn't attached it here. Can provide to those who can help. (The logs are after switching to 840MHz)
We are using gstreamer pipeline.
In our main software, we use a customized nvarguscamera element, that launches all cameras with one CaptureSession (for frame synchronization purposes) , but we were able to reproduce the error with the standard nvarguscamerasrc element as well.
We tested 5.1.2 and 5.1.3, will try to port our changes, and test version 5.1.4 as well.
In the meantime are there other steps we can take?
We’re looking for any insights or suggestions that might help resolve the camera dropout issue. Any guidance on further debugging steps or potential causes would be greatly appreciated.
-NVIDIA Orin NX
-Custom carrier board
-3 IMX477 Raspberry Pi HQ cameras connected via CSI ports
-L4T 35.4.1 (we also tested things on 35.5.0)
-Enabled resolution 4032x3040 at 30fps
We are experiencing a persistent issue where one of the IMX477 cameras drops out after a variable amount of time during recording.
The dropout occurs after as little as 10 seconds or as long as 5 hours. Initially, we saw deskew and CRC errors before the camera dropped out.
Code:
kworker/4:9-156 [004] .... 223.360804: rtcpu_vinotify_error: tstamp:7532563920 cch:3 vi:0 tag:CSIMUX_FRAME channel:0x00 frame:125 vi_tstamp:241041604448 data:0x0000007d00e00060Code:
kworker/1:1-5731 [001] .... 7933.447653: rtcpu_vinotify_error: tstamp:248593085203 cch:2 vi:1 tag:CHANSEL_NOMATCH channel:0x04 frame:53 vi_tstamp:7954978676832 data:0x0000000000000249We are using gstreamer pipeline.
In our main software, we use a customized nvarguscamera element, that launches all cameras with one CaptureSession (for frame synchronization purposes) , but we were able to reproduce the error with the standard nvarguscamerasrc element as well.
Code:
nvarguscamerasrc sensor-id=2 wbmode=0 ! "video/x-raw(memory:NVMM),format=(string)NV12,width=(int)4032,height=(int)3040,framerate=(fraction)29/1" ! nvvidconv ! nvv4l2h264enc bitrate=60000000 insert-sps-pps=true ! tee name=video1 \nvarguscamerasrc sensor-id=1 wbmode=0 ! "video/x-raw(memory:NVMM),format=(string)NV12,width=(int)4032,height=(int)3040,framerate=(fraction)29/1" ! nvvidconv ! nvv4l2h264enc bitrate=60000000 insert-sps-pps=true ! tee name=video2 \nvarguscamerasrc sensor-id=0 wbmode=0 ! "video/x-raw(memory:NVMM),format=(string)NV12,width=(int)4032,height=(int)3040,framerate=(fraction)29/1" ! nvvidconv ! nvv4l2h264enc bitrate=60000000 insert-sps-pps=true ! tee name=video3 \video1. ! h264parse ! qtmux ! filesink location=video1.mp4 \video2. ! h264parse ! qtmux ! filesink location=video2.mp4 \video3. ! h264parse ! qtmux ! filesink location=video3.mp4In the meantime are there other steps we can take?
We’re looking for any insights or suggestions that might help resolve the camera dropout issue. Any guidance on further debugging steps or potential causes would be greatly appreciated.
Statistics: Posted by Connect-Beyond-2989 — Fri Sep 13, 2024 10:55 pm