We got one ox08b40 connected to csi-a 4-lanes directly, and added lane_polarity = "6"; in dts.
kernel log got error like：
\[ 152.592691\] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
\[ 152.601895\] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
\[ 152.612566\] (NULL device \*): vi_capture_control_message: NULL VI channel received
\[ 152.620298\] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
\[ 152.631502\] (NULL device \*): vi_capture_control_message: NULL VI channel received
\[ 152.639758\] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
\[ 152.651122\] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
\[ 155.407680\] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
\[ 155.416878\] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
\[ 155.427498\] (NULL device \*): vi_capture_control_message: NULL VI channel received
\[ 155.435204\] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
\[ 155.445875\] (NULL device \*): vi_capture_control_message: NULL VI channel received
\[ 155.453698\] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
\[ 155.464608\] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
\[ 158.222376\] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
\[ 158.231526\] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
\[ 158.241569\] (NULL device \*): vi_capture_control_message: NULL VI channel received
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing an issue with a Jetson AGX Orin module connected to a CSI-A interface with 4 lanes. The error message you’re encountering is not explicitly stated, but you’ve mentioned a “trace log” which suggests that there might be some kernel-level logging information available.
To better assist you, I’ll provide some general information about the Jetson AGX Orin’s CSI-A interface and some potential troubleshooting steps.
The Jetson AGX Orin module has a CSI-A interface that supports up to 4 lanes, which can be used to connect cameras or other peripherals. The CSI-A interface is a high-speed interface that uses the MIPI CSI-2 protocol.
To troubleshoot the issue, you can try the following steps:
Verify the hardware connection: Ensure that the CSI-A interface is properly connected to the ox08b40 device and that all cables are securely attached.
Check the device tree configuration: Verify that the device tree configuration (dts) is correctly set up for the CSI-A interface. You can check the kernel logs to see if there are any errors related to the device tree configuration.
Check the kernel logs: Analyze the kernel logs to see if there are any errors related to the CSI-A interface or the ox08b40 device. You can use the dmesg command to view the kernel logs.
Check the CSI-A interface configuration: Verify that the CSI-A interface is properly configured in the kernel. You can check the kernel configuration files (e.g., csi-a.conf) to ensure that the interface is enabled and configured correctly.
In terms of comparing the Jetson AGX Orin to other modules, it’s worth noting that the CSI-A interface is a common interface used on many NVIDIA Jetson modules, including the Jetson Xavier and Jetson Nano. However, the specific configuration and usage of the CSI-A interface may vary depending on the module and the application.
If you’re still experiencing issues after trying the above troubleshooting steps, it may be helpful to provide more information about the error message you’re seeing, as well as any relevant kernel logs or configuration files. This will allow me to provide more specific guidance and assistance.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
And we use gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 '!' 'video/x-raw(memory:NVMM)' '!' nvvidconv '!' 'video/x-raw(memory:NVMM),width=1920,height=1080' '!' nv3dsink to preview raw but getting all black image
nvidia@nvidia-desktop:~$ gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! 'video/x-raw(memory:NVMM),width=1920,height=1080,framerate=30/1' ! nvvidconv ! 'video/x-raw,format=I420' ! xvimagesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:751 No cameras available
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: Pipeline construction is invalid, please add queues.
Additional debug info:
gstbasesink.c(1209): gst_base_sink_query_latency (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
Not enough buffering available for the processing deadline of 0:00:00.015000000, add enough queues to buffer 0:00:00.015000000 additional data. Shortening processing latency to 0:00:00.000000000.
Got EOS from element "pipeline0".
Execution ended after 0:00:00.002298270
Setting pipeline to NULL ...
Freeing pipeline ...
I capture raw using v4l2-ctl -d /dev/video0 --set-fmt-video=width=3840,height=2160,pixelformat=RG12 --stream-mmap=3 --stream-skip=10 --stream-to=08b-dot.raw --stream-count=1 --stream-poll and view it on my pc tool, it seems ok with the raw.
