CHANSEL_NOMATCH data:0x00000000000003c9

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

trace.txt (251.6 KB)

I have set the camera format to UYVY in the device tree, and the connected camera outputs YUV422_8. I’m using a 4-lane camera with a resolution of 3840x2160. Why is it still reporting a CHANSEL_NOMATCH error?The camera output does not have embedded metadata.

DTS:
i2c@1 {
reg = <0x01>;
#address-cells = <0x01>;
#size-cells = <0x00>;
status = “okay”;
phandle = <0x491>;

		ca1@10 {
			use_sensor_mode_id = "true";
			sensor_model = "ca";
			devnode = "video1";
			reg = <0x10>;
			compatible = "ca";
			phandle = <0x494>;

			mode0 {
				embedded_metadata_height = [30 00];
				default_framerate = "30000000";
				step_framerate = [31 00];
				max_framerate = "30000000";
				min_framerate = "2000000";
				pix_clk_hz = "297000000";
				line_length = "4399";
				csi_pixel_bit_depth = "16";
				pixel_phase = "uyvy";
				mode_type = "yuv";
				active_h = "2160";
				active_w = "3840";
				lane_polarity = [30 00];
				cil_settletime = [30 00];
				dpcm_enable = "false";
				discontinuous_clk = "no";
				phy_mode = "DPHY";
				tegra_sinterface = "serial_c";
				num_lanes = [34 00];
			};

			ports {
				#address-cells = <0x01>;
				#size-cells = <0x00>;

				port@0 {
					reg = <0x00>;

					endpoint {
						status = "okay";
						port-index = <0x02>;
						bus-width = <0x04>;
						remote-endpoint = <0x2c8>;
						phandle = <0x289>;
					};
				};
			};
		};
		
		
	};
2

PLS HELP!

4

It’s could be the incorrect virtual channel id in the frame package.

5

Thank you for your answer.
I want to continue asking:

  1. I don’t know the virtual_channel ID of the CSI camera. Can the Jetson find it out?
  2. I’m using a MIPI camera, and there’s only one camera on the MIPI cable—not GMSL. Could this also cause the problem?
6

My platform is Orin NX.

7

Do you make sure the sensor output YUV422_8?

8

Hi @YeAoNaiWoHe!

It seems your problem is related the output format frames of your sensor and the format you are requesting in the driver. Could you please provide the following information to help you with the debugging

  1. Could you share more details about the camera you are using? What formats does it provide? Does the camera has its own ISP? Firmware information?
  2. Could you share more information of your driver? What it does? What registers is trying to read/write?
  3. Are you using a Orin NX with a custom carrier or with devkit?

Thanks,

Oscar Fallas
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: https://www.ridgerun.com/

9

Thank you for your response.

  1. I am using a camera with another chip that outputs a YUV422 video stream, and it has its own ISP.
  2. I don’t need to operate any registers, nor do I need to control the power or IO pins; the driver only registers the device.
  3. I am using the devkit.
    Do you think the DTS is correct?
10

Yes，I’m sure.
Do you think the DTS is correct?

11

I tested the 1080p resolution without any issues, but when I changed the resolution to 3840x2160, I encountered this error. What could be the possible reason for this? Thank you.

12

The CHANSEL_NOMATCH could be cause by incorrect virtual channel id or incorrect data type.

13

Are there any entries in the device tree or driver that can be modified to attempt to resolve this issue, or is checking the video source the only option?

14

Need to check the output package from the sensor.

Thanks

15

Hi!

Sorry for the delayed response, what I can see look correct. Maybe you could share the tegra-capture-vi node to check there.

Thanks,

Oscar Fallas
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: https://www.ridgerun.com/

17

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