rtcpu_vinotify_event: CHANSEL_NOMATCH

When I connect cameras to xavier through vc-id, I cannot get image by v4l2-ctrl. The errors are like this:

kworker/1:2-1776 [001] … 502.123168: rtcpu_vinotify_event: tstamp:15878478974 tag:FS channel:0x00 frame:0 vi_tstamp:15878211970 data:0x00000010
kworker/1:2-1776 [001] … 502.123187: rtcpu_vinotify_event: tstamp:15878479101 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:15878211973 data:0x00000000
kworker/1:2-1776 [001] … 502.123188: rtcpu_vinotify_event: tstamp:15878479262 tag:CHANSEL_NOMATCH channel:0x01 frame:0 vi_tstamp:15878212240 data:0x00000549
kworker/1:2-1776 [001] … 502.123189: rtcpu_vinotify_event: tstamp:15878479385 tag:FE channel:0x00 frame:0 vi_tstamp:15878475727 data:0x00000020
kworker/1:2-1776 [001] … 502.123190: rtcpu_vinotify_error: tstamp:15878996366 tag:CHANSEL_NOMATCH channel:0x01 frame:0 vi_tstamp:15878993537 data:0x00000549

I want to know 0x549 means what, and what makes the “NOMATCH” happen. I have already checked that the width, height and format of image are right.

Thank you.

It could be the sensor output embedded data but your DT not define embedded_metadata_height=“number of the data line of metadata”

Hi, I don’t know how to understand the “embedded_metadata_height” and how to set the value.

And we set embedded_metadata_height = 0 now, we tried embedded_metadata_height = 1 and embedded_metadata_height = 2, the error is the same and we cannot get v4l2 image.

Could it be something else?

Our camera connect to xavier like this: sensor->ub953->ub960->xavier. The image to ub960 is 1280*768 and the format is raw10. Our dtsi is like this:

mode0 { // UB960_MODE_1280X768
mclk_khz = “25000”;
num_lanes = “4”;
tegra_sinterface = “serial_a”;
vc_id = “0”;
phy_mode = “DPHY”;
discontinuous_clk = “yes”;
dpcm_enable = “false”;
cil_settletime = “0”;
mode_type = “bayer”;
csi_pixel_bit_depth = “10”;
pixel_phase = “rggb”;

				active_w = "1280";
				active_h = "768";
				readout_orientation = "0";
				line_length = "1600";
				inherent_gain = "1";
				mclk_multiplier = "12.8";
				pix_clk_hz = "320000000";

				min_gain_val = "1.0";
				max_gain_val = "177";
				gain_step_pitch = "0.1";
				min_hdr_ratio = "1";
				max_hdr_ratio = "1";
				min_framerate = "1.5";
				max_framerate = "60";
				min_exp_time = "16.165";
				max_exp_time = "165770";
				exp_time_1h = "8";
				embedded_metadata_height = "0";
			};
			ports {
				#address-cells = <1>;
				#size-cells = <0>;
				port@0 {
					reg = <0>;
					liub960_ub960_out0: endpoint {
						vc-id = <0>;
						port-index = <0>;
						bus-width = <4>;
						remote-endpoint = <&liub960_csi_in0>;
					};
				};
			};

I think “embedded_metadata_height” means insert several lines in every frame image data?

We have already closed this function by setting sensor registers, and set embedded_metadata_height=0 in dtsi, but xavier report “NOMATCH”.

So could it be something else?

Where can I see the interpretation of this error number “0x549”?

For each frame VI throws out a NOMATCH event to indicate a line with data type = 0x2A(bit5-10) received, but no VI channel is programmed to capture this data type.

Hi, ShaneCCC

Our image data type is 0x2b(raw10), now we will go to find why the sensor send a line with data type=0x2a.

By the way, now we are using vc-id, one sensor connect to ub960 through one vc-id, and then connect to xavier.

One vc-id channel can only process one data type? If there is another type data we don’t know, the image data will be discarded?