Uncorr_err: request timed out after 2500 ms

jetson Orin NX platform, JetPack version is Jetson Linux 36.4 (part of JetPack 6.1), Two cameras using mipi cables directly into the jetson

The driver can be loaded and matched successfully:


pcai@pcai-desktop:~$ i2cdetect -y -r 9
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
pcai@pcai-desktop:~$ i2cdetect -y -r 10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --


pcai@pcai-desktop:~$ ls /dev/video*
/dev/video0  /dev/video1


root@pcai-desktop:~# v4l2-ctl --list-devices
NVIDIA Tegra Video Input Device (platform:tegra-camrtc-ca):
        /dev/media0

vi-output, iimx415 10-0037 (platform:tegra-capture-vi:0):
        /dev/video1

vi-output, iimx415 9-0037 (platform:tegra-capture-vi:2):
        /dev/video0

However, when I enter the command for mobile phone data frames(Even when I use video1, the scenario is the same.):

v4l2-ctl -d /dev/video0 -V --set-ctrl bypass_mode=0 --stream-mmap
v4l2-ctl -d /dev/video1 -V --set-ctrl bypass_mode=0 --stream-mmap


Increasing the clock doesn’t work either; dmesg and trace remain unchanged.

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
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

This is my source file:
imx415-overlay.dts.txt (2.9 KB)
imx415.dtsi.txt (11.8 KB)
imx415.c.txt (16.2 KB)

LOG FILE:
dmesg.txt (61.9 KB)
trace.txt (10.3 KB)

Doesn’t looks like receive any validate data from the sensor.
May need to probe the signal to confirm.

Thanks

Hi ShareCCC,
已找到原因,开流寄存器写入后没有开启XMSTA start,

Thanks

Hi ShareCCC,

After I captured a frame of data, I opened it with 7yuv and found it looked like this:

root@pcai-desktop:/home/pcai/pkg_orin_nx_jp6.1_v7.3.6# v4l2-ctl --set-fmt-video=width=3864,height=2192,pixelformat=RG12 --set-ctrl bypass_mode=0 --stream-mmap --stream-skip=9 --stream-count=1 --stream-to=test.raw -d /dev/video0 -V
Format Video Capture:
        Width/Height      : 3864/2192
        Pixel Format      : 'RG12' (12-bit Bayer RGRG/GBGB)
        Field             : None
        Bytes per Line    : 7728
        Size Image        : 16939776
        Colorspace        : sRGB
        Transfer Function : Default (maps to sRGB)
        YCbCr/HSV Encoding: Default (maps to ITU-R 601)
        Quantization      : Default (maps to Full Range)
        Flags             :
<<<<<<<<<<



Here is the specific log:
dmesg.txt (77.4 KB)
trace.txt (643.1 KB)

How should this be solved please?

Set the stride to 32 alignment by below command to verify.

v4l2-ctl -c preferred_stride=7744

If 32 alignment didn’t help try the 256 alignment.

Hi ShaneCCC,
I tried both of these, but neither worked。The log is the same as before.

Additionally, may I ask if it could be related to this log:

This is my format, but it seems to be different from the one here:


This tell the sensor output unsupported user define data.
Maybe disable it to verify.

Hi ShaneCCC,

How can I modify the configuration to avoid this error? My current configuration has been posted in the above comments and description, and I’m not sure how to do this.

Check with sensor vendor if able to remove the sensor user define data.

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