Embedded Meta Data from MIPI CSI2 in Xavier NX

Hi,

I’m trying to get Embedded Data along with Image Data from an External ISP Connected with Xavier NX. As per the Readout Pixel Diagram, only the first row contains Embedded Data and rest contains Image Data. I’m using 1920*1080 as the resolution for Image Data and using the below device tree settings.

				mclk_khz = "24000";
				num_lanes = "2";
				tegra_sinterface = "serial_d";
				discontinuous_clk = "no";
				dpcm_enable = "false";
				cil_settletime = "0";
				dynamic_pixel_bit_depth = "16";
				csi_pixel_bit_depth = "16";
				mode_type = "yuv";
				pixel_phase = "yuyv";

				active_w = "1920";
				active_h = "1080";
				readout_orientation = "0";
				line_length = "2468";

				embedded_metadata_height = "1";

By using the above settings if i tried to stream the data, I’m getting only initial frame and rest of the frames are in a stuck condition. I used the below pipeline in order to stream data. Please suggest me, if my device tree settings or the methodology to collect data founds wrong.

gst-launch-1.0 v4l2src -v device=/dev/video2 ! identity silent=FALSE ! videoconvert ! xvimagesink

Also, If I wanted to collect the embedded data seperately in a buffer, what all modification should I need to make in the vi5_fops.c?

Kindly help me to get some solution, in order to resolve this issue.

Please note the embedded data doesn’t include the output size.
Get the trace log to check.

https://elinux.org/Jetson/l4t/Camera_BringUp#Steps_to_enable_more_debug_messages

Hi @ShaneCCC

I’m not making use of nvarguscamera. I’m using v4l2src and v4l
media frameworks only. Is there any way to get it using v4l?.

I’m attaching the trace logs as well as kernel logs for your reference.
tracelog.txt (606.6 KB)
kernlog.txt (18.5 KB)

Below tell the output height less than expected.

kworker/0:4-5935  [000] ....   148.621466: rtcpu_vinotify_event: tstamp:4967287762 tag:CHANSEL_SHORT_FRAME channel:0x08 frame:0 vi_tstamp:4966993896 data:0x01000000

It could be the embedded data size incorrect or data type incorrect.

kworker/0:4-5935  [000] ....   148.621499: rtcpu_vinotify_error: tstamp:4968070179 tag:CHANSEL_NOMATCH channel:0x08 frame:0 vi_tstamp:4968067586 data:0x000003c9

Below tell the pixel runaway means the width doesn’t as expected.

     kworker/0:4-5935  [000] ....   148.621504: rtcpu_vinotify_event: tstamp:4968256848 tag:CHANSEL_FAULT channel:0x23 frame:0 vi_tstamp:4967776052 data:0x04380040

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