Orin nano with 2 ahd cameras to mipi, only one camera work

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi:
My hardware connection and mipi data format as follows:

image
image629×305 3.32 KB

image
image895×265 55.7 KB

I can get /dev/video0 and /dev/video1 successfully, and test video0 cannot get video, but video1 can get video normally.
and attach my dts file:
tegra234-camera-rbpcv2-xs9922.dtsi.log (6.1 KB)

v4l2-ctl -d /dev/video1 --set-fmt-video=width=1920,height=1080,pixelformat=UYVY --stream-mmap --set-ctrl bypass_mode=0 --stream-count=100
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps
<<<<<<<<<

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=UYVY --stream-mmap --set-ctrl bypass_mode=0 --stream-count=100
--------no response

dmesg shows:

[ 6558.179919] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 6558.189058] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 6558.199124] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 6558.206842] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 6558.217507] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 6558.225224] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0
[ 6558.236016] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 6560.995829] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 6561.004964] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 6561.015191] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 6561.022912] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 6561.033583] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 6561.041308] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0
[ 6561.052054] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

attach trace log:
trace_video0_fail.log (6.5 KB)
trace_video1_ok.log (12.2 KB)

Hope get your help, Thanks!

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it appears that you are experiencing issues with the MIPI CSI video input on the Jetson Orin Nano module. You have successfully connected the camera and obtained dev/video0 and dev/video1, but are unable to get video from video0 while video1 works normally.

To troubleshoot this issue, let’s examine the provided information:

  1. Hardware Connection: You have provided images of your hardware connection, but unfortunately, I’m a text-based AI and cannot view images. However, I can provide general guidance on the connection.
  2. MIPI Data Format: You have mentioned the MIPI data format, but without specific details, it’s difficult to provide targeted advice. However, I can suggest that you verify the MIPI data format is correctly configured in your device tree file.
  3. Device Tree File: You have provided a device tree file (tegra234camerarbpcv2xs9922.dtsi) and a log file (dmesg output). These files can provide valuable information about the issue.

Based on the provided log file, it appears that there are some errors related to the camera interface. Specifically, the log file mentions:

  • tegra_csi_camera_start_streaming: buffer channel not found
  • tegra_csi_camera_stop_streaming: buffer channel not found

These errors suggest that there might be an issue with the buffer channel configuration or the camera interface.

To resolve this issue, I recommend the following steps:

  1. Verify MIPI Data Format: Double-check that the MIPI data format is correctly configured in your device tree file. Ensure that the format matches the camera’s output format.
  2. Check Buffer Channel Configuration: Verify that the buffer channel configuration is correct in your device tree file. Ensure that the buffer channels are properly defined and configured for the camera interface.
  3. Camera Interface Configuration: Review the camera interface configuration in your device tree file. Ensure that the camera interface is properly configured and enabled.
  4. Test with a Different Camera: If possible, try testing with a different camera to rule out any camera-specific issues.

If you’re still experiencing issues after trying these steps, please provide more detailed information about your setup, including the camera model, MIPI data format, and device tree file configuration. This will help me provide more targeted advice.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

@JerryChang , hope get your help checking the dts file and feedback, Thanks very much!

6

hello 1010622394,

please remove devname property if you’re running on JP-6 release version.
for example,

	tcp: tegra-camera-platform {
		modules {
			cam_module0: module0 {
				drivernode0 {
					pcl_id = "v4l2_sensor";
					devname = "xs9922 10-0031";  <== delete this property. 

			cam_module1: module1 {
				drivernode0 {
					pcl_id = "v4l2_sensor";
					devname = "xs9922 10-0032";  <== delete this property.
7

I use Jetpack 5.1.1, and I will check only one camera first, Thanks!

9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.