With lt6911c Orin N custom board, only the green screen can be captured

Both module with imx219 can capture video with nvgstcapture-1.0 command. The gst-launch-1.0 preview command is not found.

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

Hi kayccc,

Yes.

May I ask if any custom board of CSI0+CSI1 used by others can work normally?

I meet the same issue, a few orin-nx can work well, but others not, if connect to imx577 or imx477 sensor, all work well, i suppose the lt6911c bridge is not compatible to orin-nx, how to calibrate the MIPI timings on orin-nx?

Do you upgrade to r35.5 the RCE firmware have some calibration improvement.

Thanks

Thank for your concern at first, I try the r35.5.0 version, but problem is still here!

Hi, may I ask which CSI lanes you use?

What’s the trace log?

tracer: nop

entries-in-buffer/entries-written: 44/44 #P:6

_-----=> irqs-off

/ _----=> need-resched

| / _—=> hardirq/softirq

|| / _–=> preempt-depth

||| / delay

TASK-PID CPU# |||| TIMESTAMP FUNCTION

| | | |||| | |

 kworker/4:0-35      [004] ....    93.137784: rtcpu_string: tstamp:3500208665 id:0x04010000 str:"VM0 deactivating."

gst-plugin-scan-3142 [002] … 99.380285: tegra_channel_open: vi-output, lt6911c 9-002b
gst-plugin-scan-3142 [002] … 99.380369: tegra_channel_close: vi-output, lt6911c 9-002b
gst-plugin-scan-3142 [002] … 99.380377: tegra_channel_open: vi-output, lt6911c 10-002b
gst-plugin-scan-3142 [002] … 99.380389: tegra_channel_close: vi-output, lt6911c 10-002b
gst-launch-1.0-3141 [004] … 99.463483: tegra_channel_open: vi-output, lt6911c 9-002b
gst-launch-1.0-3141 [004] … 99.463568: tegra_channel_close: vi-output, lt6911c 9-002b
gst-launch-1.0-3141 [004] … 99.463578: tegra_channel_open: vi-output, lt6911c 10-002b
gst-launch-1.0-3141 [004] … 99.463589: tegra_channel_close: vi-output, lt6911c 10-002b
gst-launch-1.0-3141 [000] … 99.477757: tegra_channel_open: vi-output, lt6911c 9-002b
v4l2src0:src-3144 [000] … 99.486573: tegra_channel_set_power: lt6911c 9-002b : 0x1
v4l2src0:src-3144 [000] … 99.486588: camera_common_s_power: status : 0x1
v4l2src0:src-3144 [000] … 99.487832: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2src0:src-3144 [000] … 99.487834: csi_s_power: enable : 0x1
v4l2src0:src-3144 [000] … 99.488496: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1080 fmt 13
v4l2src0:src-3144 [001] … 99.496364: tegra_channel_set_stream: enable : 0x1
v4l2src0:src-3144 [000] … 99.500905: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2src0:src-3144 [000] … 99.500908: csi_s_stream: enable : 0x1
v4l2src0:src-3144 [000] … 99.501127: tegra_channel_set_stream: lt6911c 9-002b : 0x1
kworker/4:0-35 [004] … 99.529635: rtcpu_string: tstamp:3699999505 id:0x04010000 str:“VM0 activating.”
kworker/4:0-35 [004] … 99.529640: rtcpu_vinotify_event: tstamp:3700657394 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118405305280 data:0x759d580010000000
kworker/4:0-35 [004] … 99.529640: rtcpu_vinotify_event: tstamp:3700657651 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118405315072 data:0x0000000031000001
kworker/4:0-35 [004] … 99.529640: rtcpu_vinotify_event: tstamp:3700657935 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118405406720 data:0x759d550010000000
kworker/4:0-35 [004] … 99.529640: rtcpu_vinotify_event: tstamp:3700658183 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118405416608 data:0x0000000031000002
vi-output, lt69-3147 [000] … 102.159841: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1080 fmt 13
kworker/4:0-35 [004] … 102.169558: rtcpu_vinotify_event: tstamp:3783665834 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:121074874208 data:0x759d580010000000
kworker/4:0-35 [004] … 102.169562: rtcpu_vinotify_event: tstamp:3783666094 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:121074916928 data:0x0000000031000001
kworker/4:0-35 [004] … 102.225558: rtcpu_vinotify_event: tstamp:3784208570 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:121084651456 data:0x759d550010000000
kworker/4:0-35 [004] … 102.225561: rtcpu_vinotify_event: tstamp:3784208828 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:121084694784 data:0x0000000031000002
vi-output, lt69-3147 [003] … 106.001361: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1080 fmt 13
kworker/4:0-35 [004] … 112.981408: rtcpu_string: tstamp:4121520410 id:0x04010000 str:“VM0 deactivating.”
gst-launch-1.0-3141 [002] … 113.566282: tegra_channel_set_stream: enable : 0x0
gst-launch-1.0-3141 [002] … 113.566286: tegra_channel_set_stream: lt6911c 9-002b : 0x0
gst-launch-1.0-3141 [002] … 113.566299: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x0
gst-launch-1.0-3141 [002] … 113.566301: csi_s_stream: enable : 0x0
gst-launch-1.0-3141 [002] … 113.570033: tegra_channel_set_power: lt6911c 9-002b : 0x0
gst-launch-1.0-3141 [002] … 113.570041: camera_common_s_power: status : 0x0
gst-launch-1.0-3141 [002] … 113.570075: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x0
gst-launch-1.0-3141 [002] … 113.570077: csi_s_power: enable : 0x0
kworker/4:0-35 [004] … 113.597411: rtcpu_string: tstamp:4139969264 id:0x04010000 str:“WARNING: core/hsp/hsp-vm.c:283 [camrtc_hsp_full_”
kworker/4:0-35 [004] … 113.597417: rtcpu_string: tstamp:4139969553 id:0x04010000 str:“ss_isr] “”
kworker/4:0-35 [004] … 113.597418: rtcpu_string: tstamp:4139970459 id:0x04010000 str:“VM0 issued IVC in inactive state.”
kworker/4:0-35 [004] … 113.597419: rtcpu_string: tstamp:4139970906 id:0x04010000 str:”"
"
gst-launch-1.0-3141 [002] … 114.685856: tegra_channel_close: vi-output, lt6911c 9-002b

I would suspect the signal output due to the trace log tell didn’t receive any validate data from sensor.

Thanks

Hi!
I have tested the video capture function on devkit by connecting CAM1 interface (CSI2+CSI3) to LT6911. all orin-nx modules can work well.
So I think CSI0+CSI1 this connection method may have some problems(maybe lanes swap).

If CSI2+CSI3 working without problem then CSI0+CSI1 need add lane_polarity = “6”;

When using CSI0+CSI1 previously, lane_polarity was already set to “6”.