Customized carrier board with two 4-lane ports unable to capture frame properly

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

Hi,

I’m working on a customized carrier board which has two 4-lane CSI ports. I updated the device tree overlay for the camera, and mounted two 4K sensors to the ports, but still unable to capture frames properly. For CSI 0, the capture is working but the frame looks very noisy, and for CSI 1, the capture is not very well. I attached the captures for those two ports, and also enclosed the dts file. Could anyone give any suggestion on this? I believe there must be something wrong with the device tree configuration. Thanks in advance!

Best,
Wenhai.

kernel_tegra234-p3767-0001-auvidea-jnx42-base-user-custom.txt (445.7 KB)

capture_cam0_4lanes
capture_cam0_4lanes1920×1080 340 KB

capture_cam1_4lanes
capture_cam1_4lanes1920×1080 693 KB

3

Did you boost the clocks to try?

sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee  /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate
4

Hi Shane,

Yes, I have tried, but the issue is still not solved. I tried for 2-lane setup. Cam0 is working well, but I can still see some noise. Cam1 is still not working.

5

All of the sensor modes(resolutions) have the same noise?

Please check if v4l2-ctl working for camera1 and get the trace log.

Example for v4l2-ctl command.

v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap
6

Hi,

I tried the v4l2-ctl command, but nothing was showing on when i entered the command. I got some error from dmesg:

For command “v4l2-ctl --device 0 --set-fmt-video=width=1920,height=1080,pixelformat=GB10 --set-ctrl bypass_mode=0 --stream-mmap”, errors are:

[ +10.371052] bwmgr API not supported
[Apr17 14:46] imx715 9-001a: imx715_check_unsupported_mode: selected mode is not supported with RAW10, switching to default
[  +0.063593] bwmgr API not supported
[  +0.159416] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 1, flags: 0, err_data 39845984
[  +0.033327] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 2, flags: 0, err_data 39845984
[  +0.033331] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 3, flags: 0, err_data 39845984
[  +0.033329] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 4, flags: 0, err_data 39845984

For command “v4l2-ctl --device 1 --set-fmt-video=width=1920,height=1080,pixelformat=GB10 --set-ctrl bypass_mode=0 --stream-mmap”, the errors are:

[  +1.739582] bwmgr API not supported
[Apr17 14:48] imx715 10-001a: imx715_check_unsupported_mode: selected mode is not supported with RAW10, switching to default
[  +0.063919] bwmgr API not supported
[  +0.142813] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 1, flags: 0, err_data 131072
[  +0.017236] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 2, flags: 0, err_data 262144
[  +0.017235] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 3, flags: 0, err_data 262144
[  +0.034456] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 5, flags: 0, err_data 131072

When I set the resolution to “--set-fmt-video=width=3864,height=2192”, the unsupported mode error has gone, but those “tegra-capture-vi” errors are still there.

Best,
Wenhai.

7

Get the trace log to check.

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

8

Hi Shane,

This is the trace file when I launched command “v4l2-ctl --device 1 --set-fmt-video=width=3864,height=2192,pixelformat=GB10 --set-ctrl bypass_mode=0 --stream-mmap”.
trace.txt (4.2 MB)

9

There are CRC error and SOT error, I would suspect it could be the HW signal problem.

     kworker/1:9-154     [001] ....  2933.993349: rtcpu_nvcsi_intr: tstamp:92649850885 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:0 status:0x00000004
     kworker/1:9-154     [001] ....  2933.993349: rtcpu_nvcsi_intr: tstamp:92649850885 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000022
10

Thanks for helping with analysis, and also please find the trace log for the /dev/video0, while running “v4l2-ctl --device 0 --set-fmt-video=width=3864,height=2192,pixelformat=GB10 --set-ctrl bypass_mode=0 --stream-mmap”.
trace.txt (1.2 MB)

For this sensor device, even though the camera capture is working but it appears some noises on the frame.

11

I would suspect the noise could be HW signal interference.
Try get dump the raw data to confirm.

13

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