After a series of operations, the camera has no image

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

Hi：
The camera cannot produce pictures. Please help to find out what is the reason.
The steps are as follows:
clinet：

v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb，image ok
v4l2-ctl -d /dev/video3 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 depth，image ok
v4l2-ctl -d /dev/video2 --stream-mmap --stream-to-host 192.168.1.111 —> open imx390，image ok
v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb，no image
v4l2-ctl -d /dev/video3 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb，no image
service：
qvidcap -p

Software version：
JP5.1.2

root@tegra:/home/robot# cat /etc/nv_tegra_release

R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 1 19:57:35 UTC 2023

Block Diagram：

image
image916×301 8.99 KB

image
image1270×284 33.8 KB

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

cd /sys/kernel/debug/dynamic_debug/
echo file csi2_fops.c +p > control

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

echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace

trace log：
trace.log (563.4 KB)

dmesg:
dmesg.txt (137.7 KB)

dts:
temp.txt (430.0 KB)

camera info:

root@tegra:/home/robot# v4l2-ctl -d 5 -D
Driver Info:
        Driver name      : tegra-video
        Card type        : vi-output, DS5 mux 31-001a
        Bus info         : platform:tegra-capture-vi:2
        Driver version   : 5.10.120
        Capabilities     : 0x84a00001
                Video Capture
                Metadata Capture
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x04200001
                Video Capture
                Streaming
                Extended Pix Format
Media Driver Info:
        Driver name      : tegra-camrtc-ca
        Model            : NVIDIA Tegra Video Input Device
        Serial           :
        Bus info         :
        Media version    : 5.10.120
        Hardware revision: 0x00000003 (3)
        Driver version   : 5.10.120
Interface Info:
        ID               : 0x03000082
        Type             : V4L Video
Entity Info:
        ID               : 0x00000080 (128)
        Name             : vi-output, DS5 mux 31-001a
        Function         : V4L2 I/O
        Pad 0x01000081   : 0: Sink
          Link 0x02000086: from remote pad 0x1000006 of entity '13e40000.host1x:nvcsi@15a00000-': Data, Enabled
root@tegra:/home/robot# v4l2-ctl -d 3 -D
Driver Info:
        Driver name      : tegra-video
        Card type        : vi-output, DS5 mux 31-001a
        Bus info         : platform:tegra-capture-vi:2
        Driver version   : 5.10.120
        Capabilities     : 0x84a00001
                Video Capture
                Metadata Capture
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x04200001
                Video Capture
                Streaming
                Extended Pix Format
Media Driver Info:
        Driver name      : tegra-camrtc-ca
        Model            : NVIDIA Tegra Video Input Device
        Serial           :
        Bus info         :
        Media version    : 5.10.120
        Hardware revision: 0x00000003 (3)
        Driver version   : 5.10.120
Interface Info:
        ID               : 0x03000056
        Type             : V4L Video
Entity Info:
        ID               : 0x00000054 (84)
        Name             : vi-output, DS5 mux 31-001a
        Function         : V4L2 I/O
        Pad 0x01000055   : 0: Sink
          Link 0x0200005a: from remote pad 0x1000003 of entity '13e40000.host1x:nvcsi@15a00000-': Data, Enabled
root@tegra:/home/robot# v4l2-ctl -d 2 -D
Driver Info:
        Driver name      : tegra-video
        Card type        : vi-output, ar0233 31-001c
        Bus info         : platform:tegra-capture-vi:2
        Driver version   : 5.10.120
        Capabilities     : 0x84200001
                Video Capture
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x04200001
                Video Capture
                Streaming
                Extended Pix Format
Media Driver Info:
        Driver name      : tegra-camrtc-ca
        Model            : NVIDIA Tegra Video Input Device
        Serial           :
        Bus info         :
        Media version    : 5.10.120
        Hardware revision: 0x00000003 (3)
        Driver version   : 5.10.120
Interface Info:
        ID               : 0x03000036
        Type             : V4L Video
Entity Info:
        ID               : 0x00000034 (52)
        Name             : vi-output, ar0233 31-001c
        Function         : V4L2 I/O
        Pad 0x01000035   : 0: Sink
          Link 0x0200003a: from remote pad 0x1000009 of entity '13e40000.host1x:nvcsi@15a00000-': Data, Enabled
root@tegra:/home/robot#
3

The CHANSEL_NOMATCH could be report incorrect embedded data or virtual channel ID incorrect.

And CHANSEL_SHORT_FRAME tell the output size less than expected.

Thanks

4

Hi:

Sorry, the above log is the log of the entire test process. I captured the logs of each situation separately, as follows:

Normally

root@tegra:~# v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111
                VIDIOC_CROPCAP returned -1 (Inappropriate ioctl for device)
                VIDIOC_G_STD returned -1 (Inappropriate ioctl for device)
                VIDIOC_G_DV_TIMINGS returned -1 (Inappropriate ioctl for device)
<<<<<<<<<<<<<<<<<< 16.99 fps 96% compression
<<<<<<<<<<<<<< 15.43 fps 96% compression
<<<<<<<<<<<<<< 14.96 fps 96% compression
<<<<<<<<<<<<<< 14.60 fps 96% compression
<<<4064 != 88220
<root@tegra:~#

trace log:
trace_d457_ok.txt (377.5 KB)
trace_imx390_ok.txt (141.8 KB)

Abnormal situation：

root@tegra:~# v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111
                VIDIOC_CROPCAP returned -1 (Inappropriate ioctl for device)
                VIDIOC_G_STD returned -1 (Inappropriate ioctl for device)
                VIDIOC_G_DV_TIMINGS returned -1 (Inappropriate ioctl for device)
^C^C^C^C^C^C
root@tegra:~#

trace log:
trace_d457_error.txt (5.6 KB)

PS：
The code has been modified as follows：

image
image1040×326 29.7 KB

5

The failed log shows didn’t receive any validate data from sensor.
Suppose it could be the driver configure problem to send correct data to MIPI bus.

Thanks

6

Hi，
I used an oscilloscope to capture the waveforms between max9296 and Orin NX. The waveforms are the same under normal conditions and abnormal conditions.
PS:
I turn off max9295 sending of rgb camera

7

Does below sequency have problem?

v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb
v4l2-ctl -d /dev/video3 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 depth
v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb
v4l2-ctl -d /dev/video3 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 depth

8

After the device starts,The execution command is as follows:
v4l2-ctl -d /dev/video3 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 depth ----OK
End the above command
v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb --OK
End the above command
v4l2-ctl -d /dev/video3 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 depth ----fail
End the above command
v4l2-ctl -d /dev/video5 --stream-mmap --stream-to-host 192.168.1.111 —> open d457 rgb --OK

9

I would suggest consulting with vendor of max929x for this kind of issue.

11

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