ZED X mini on Orin NX not able to connect

linh.nguyen · January 23, 2024, 8:17am

I’m using ZED X Mini with capture card connecting to Jetson Orin NX devkit. Jetpack 5.1.2, ZED SDK 4.0.8. Driver and SDK are installed correctly. I saw green LED on capture card after boot up.

But I can’t connect to the camera by ZED_Explorer or any app. I have tried to reduce the MIPI bandwidth to 1.6G per lane, but it is still doesn’t work.

Diagnostic result and dmesg attached.
dmesg_2.log (12.3 KB)

ZED_Diagnostic_Results.json (5.2 KB)

Looks like the I2C is failed to write register setting to image sensors. I have tried on shorter FPC flat cable (15cm, current one is 20cm) but the same error, I don’t have shorter cable.

Do you have any idea what the problem is?

Thank you.

Myzhar · January 23, 2024, 10:20am

Hi @linh.nguyen
we recommend using shorter cables (max 7 cm).
If you do not own them you can try to use the fix reported in the online documentation:

linh.nguyen · January 23, 2024, 10:23am

Hi Myzhar,

Thank you for your response.
I have tried to reduce the MIPI bandwidth as suggested, but it doesn’t help.
I will try to find shorter cables. Thank you.

linh.nguyen · January 23, 2024, 10:51am

Hi Walter,

It is already attached in the first post.

But here is it:

Created: Tue Jan 23 2024

###########################################
############ DMESG [ZEDX] LOG #############
###########################################

[ 17.809350] zedx 30-0018: Driver Version : v0.6.1
[ 17.809358] zedx 30-0018: Probing v4l2 sensor.
[ 17.809527] zedx 30-0018: tegracam sensor driver:video0_v2.0.6
[ 25.628754] zedx 30-0018: zedx_links_check: 1 link(s) detected
[ 28.559228] zedx 30-0018: Single ZED-X camera detect success
[ 28.790526] zedx 30-0018: zedx_set_frame_rate: Unsupported value
[ 29.119794] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0018 bound
[ 29.120718] zedx 30-0018: Detected ZED-X sensor
[ 29.120892] zedx 30-0010: Driver Version : v0.6.1
[ 29.120894] zedx 30-0010: Probing v4l2 sensor.
[ 29.121061] zedx 30-0010: tegracam sensor driver:video1_v2.0.6
[ 29.131246] zedx 30-0018: zedx_open: Accessing the camera
[ 29.228999] zedx 30-0010: zedx_links_check: 1 link(s) detected
[ 29.454721] zedx 30-0010: zedx_set_frame_rate: Unsupported value
[ 29.783754] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0010 bound
[ 29.784545] zedx 30-0010: Detected ZED-X sensor
[ 29.784680] zedx 31-0018: Driver Version : v0.6.1
[ 29.784682] zedx 31-0018: Probing v4l2 sensor.
[ 29.784859] zedx 31-0018: tegracam sensor driver:video2_v2.0.6
[ 29.787485] zedx 30-0010: zedx_open: Accessing the camera
[ 29.892931] zedx 31-0018: zedx_links_check: 1 link(s) detected
[ 29.893661] zedx 31-0018: zedx_write_reg:i2c write failed, 0x301a = 2058
[ 29.900641] zedx 31-0018: ZED-X detect error
[ 29.900754] zedx: probe of 31-0018 failed with error -1
[ 29.909072] zedx 31-0010: Driver Version : v0.6.1
[ 29.909077] zedx 31-0010: Probing v4l2 sensor.
[ 29.909294] zedx 31-0010: tegracam sensor driver:video3_v2.0.6
[ 30.016973] zedx 31-0010: zedx_links_check: 1 link(s) detected
[ 30.017594] zedx 31-0010: zedx_write_reg:i2c write failed, 0x301a = 2058
[ 30.024512] zedx 31-0010: ZED-X detect error
[ 30.024589] zedx: probe of 31-0010 failed with error -1
[ 64.246879] zedx 30-0010: zedx_open: Accessing the camera
[ 64.246965] zedx 30-0018: zedx_open: Accessing the camera
[ 891.808127] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0010 unbind
[ 891.812700] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0018 unbind
[ 891.844179] zedx 30-0018: Driver Version : v0.6.1
[ 891.844186] zedx 30-0018: Probing v4l2 sensor.
[ 891.844352] zedx 30-0018: tegracam sensor driver:video0_v2.0.6
[ 899.607892] zedx 30-0018: zedx_links_check: 1 link(s) detected
[ 902.511618] zedx 30-0018: Single ZED-X camera detect success
[ 902.739013] zedx 30-0018: zedx_set_frame_rate: Unsupported value
[ 903.068599] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0018 bound
[ 903.069918] zedx 30-0018: Detected ZED-X sensor
[ 903.070074] zedx 30-0010: Driver Version : v0.6.1
[ 903.070077] zedx 30-0010: Probing v4l2 sensor.
[ 903.070285] zedx 30-0010: tegracam sensor driver:video1_v2.0.6
[ 903.075550] zedx 30-0018: zedx_open: Accessing the camera
[ 903.177488] zedx 30-0010: zedx_links_check: 1 link(s) detected
[ 903.403123] zedx 30-0010: zedx_set_frame_rate: Unsupported value
[ 903.732603] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0010 bound
[ 903.733371] zedx 30-0010: Detected ZED-X sensor
[ 903.733460] zedx 31-0018: Driver Version : v0.6.1
[ 903.733463] zedx 31-0018: Probing v4l2 sensor.
[ 903.733635] zedx 31-0018: tegracam sensor driver:video2_v2.0.6
[ 903.737647] zedx 30-0010: zedx_open: Accessing the camera
[ 903.841673] zedx 31-0018: zedx_links_check: 1 link(s) detected
[ 903.842402] zedx 31-0018: zedx_write_reg:i2c write failed, 0x301a = 2058
[ 903.849362] zedx 31-0018: ZED-X detect error
[ 903.849477] zedx: probe of 31-0018 failed with error -1
[ 903.854944] zedx 31-0010: Driver Version : v0.6.1
[ 903.854947] zedx 31-0010: Probing v4l2 sensor.
[ 903.855194] zedx 31-0010: tegracam sensor driver:video3_v2.0.6
[ 903.961658] zedx 31-0010: zedx_links_check: 1 link(s) detected
[ 903.962313] zedx 31-0010: zedx_write_reg:i2c write failed, 0x301a = 2058
[ 903.969252] zedx 31-0010: ZED-X detect error
[ 903.969349] zedx: probe of 31-0010 failed with error -1

###########################################
############ DMESG [DTS] LOG #############
###########################################

[ 0.002860] DTS File Name: /builds/sl/jetson-gmsl-kernel/src/kernel/kernel-5.10/arch/arm64/boot/dts/../../../../../../hardware/nvidia/platform/t23x/p3768/kernel-dts/tegra234-p3767-0000-p3768-0000-a0.dts
[ 2.365668] tegra-pmc c360000.pmc: scratch reg offset dts data not present

###########################################
############ DTB list original ###########
###########################################

/boot/dtb/kernel_tegra234-p3767-0000-p3768-0000-a0.dtb

###########################################
############ DTB list SLabs ###########
###########################################

/boot/stereolabs/tegra194-p2888-0001-p2822-0000.dtb
/boot/stereolabs/tegra194-p3668-0000-p3509-0000.dtb
/boot/stereolabs/tegra194-p3668-0001-p3509-0000.dtb
/boot/stereolabs/tegra234-p3701-0000-p3737-0000.dtb
/boot/stereolabs/tegra234-p3701-0004-p3737-0000.dtb
/boot/stereolabs/tegra234-p3701-0005-p3737-0000.dtb
/boot/stereolabs/tegra234-p3701-0008-p3737-0000.dtb
/boot/stereolabs/tegra234-p3767-0000-p3509-a02.dtb
/boot/stereolabs/tegra234-p3767-0000-p3768-0000-a0.dtb
/boot/stereolabs/tegra234-p3767-0001-p3509-a02.dtb
/boot/stereolabs/tegra234-p3767-0003-p3768-0000-a0.dtb

/boot/stereolabs/utils:
extlinux.py
fio.py
__pycache__

###########################################
############ EXTlinux file ###########
###########################################

TIMEOUT 30
DEFAULT Stereolabs

MENU TITLE L4T boot options

LABEL primary
 MENU LABEL primary kernel
 LINUX /boot/Image
 FDT /boot/dtb/kernel_tegra234-p3767-0000-p3768-0000-a0.dtb
 INITRD /boot/initrd
 APPEND ${cbootargs} root=PARTUUID=d9b5dc01-ee1b-4ae3-b0a5-e916714a629d rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb

# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot

# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# FDT /boot/dtb/kernel_tegra234-p3767-0000-p3768-0000-a0.dtb
# INITRD /boot/initrd
# APPEND ${cbootargs}


LABEL Stereolabs
      MENU LABEL Stereolabs kernel
      LINUX /boot/Image
      FDT /boot/stereolabs/tegra234-p3767-0000-p3768-0000-a0.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=d9b5dc01-ee1b-4ae3-b0a5-e916714a629d rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb

####################################
############ Driver list ###########
####################################

/usr/lib/modules/5.10.120-tegra/kernel/drivers/stereolabs/max96712/sl_max96712.ko==> exists
/usr/lib/modules/5.10.120-tegra/kernel/drivers/stereolabs/zedx/sl_zedx.ko ==> exists

################################################
############ ZEDX Daemon Status LS #############
################################################

● zed_x_daemon.service - ZED-X Daemon service
 Loaded: loaded (/etc/systemd/system/zed_x_daemon.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2024-01-23 08:04:26 UTC; 1min 6s ago
 Main PID: 3101 (ZEDX_Daemon)
 Tasks: 3 (limit: 18304)
 Memory: 832.0K
 CGroup: /system.slice/zed_x_daemon.service
 └─3101 /usr/sbin/ZEDX_Daemon

Jan 23 08:04:26 orbitone-orin systemd[1]: Started ZED-X Daemon service.
Jan 23 08:04:26 orbitone-orin ZEDX_Daemon[3101]: [ "Tue Jan 23 08:04:26 2024" ] ** Start ZED-X Daemon
Jan 23 08:04:26 orbitone-orin ZEDX_Daemon[3101]: [ "Tue Jan 23 08:04:26 2024" ] ** Searching for Preload file "/etc/systemd/system/zed_x_daemon.preload" : false
Jan 23 08:04:27 orbitone-orin ZEDX_Daemon[3101]: [ "Tue Jan 23 08:04:27 2024" ] Process "insmod /usr/lib/modules/5.10.120-tegra/kernel/drivers/stereolabs/max96712/sl_max96712.ko" outputs "insmod: ERROR: could not insert module /usr/lib/modules/5.10.120-tegra/kernel/drivers/stereolabs/max96712/sl_max96712.ko: File exists\n"
Jan 23 08:04:39 orbitone-orin ZEDX_Daemon[3101]: ** ZED-X Driver loaded
Jan 23 08:04:39 orbitone-orin ZEDX_Daemon[3101]: [ "Tue Jan 23 08:04:39 2024" ] ** Searching for Postload file "/etc/systemd/system/zed_x_daemon.postload" : false
Jan 23 08:04:39 orbitone-orin ZEDX_Daemon[3101]: [ "Tue Jan 23 08:04:39 2024" ] ** Created Endpoint "tcp://127.0.0.1:20026"

################################################
############ I2C Trace [-l] #############
################################################

i2c-3 i2c   3190000.i2c     I2C adapter
i2c-30      i2c   i2c-2-mux (chan_id 0)     I2C adapter
i2c-1 i2c   c240000.i2c     I2C adapter
i2c-8 i2c   31e0000.i2c     I2C adapter
i2c-6 i2c   31c0000.i2c     I2C adapter
i2c-33      i2c   i2c-2-mux (chan_id 3)     I2C adapter
i2c-4 i2c   Tegra BPMP I2C adapter     I2C adapter
i2c-31      i2c   i2c-2-mux (chan_id 1)     I2C adapter
i2c-2 i2c   3180000.i2c     I2C adapter
i2c-0 i2c   3160000.i2c     I2C adapter
i2c-9 i2c   NVIDIA SOC i2c adapter 0     I2C adapter
i2c-7 i2c   c250000.i2c     I2C adapter
i2c-5 i2c   31b0000.i2c     I2C adapter
i2c-32      i2c   i2c-2-mux (chan_id 2)     I2C adapter

################################################
############ I2C Trace /dev/i2C-30 #############
################################################

 0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: UU -- -- -- -- -- -- -- UU 19 -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- 49 -- -- -- -- -- --
50: -- -- -- -- 54 55 -- -- 58 59 -- -- -- -- -- --
60: -- -- 62 -- -- -- -- -- -- 69 -- -- -- -- -- --
70: UU -- -- -- -- -- -- --

################################################
############ I2C Trace /dev/i2C-31 #############
################################################

 0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- 29 -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --

################################################
############ I2C Trace /dev/i2C-32 #############
################################################

 0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --

################################################
############ I2C Trace /dev/i2C-33 #############
################################################

 0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --
#########################

Thank you,
Linh

linh.nguyen · January 26, 2024, 1:54pm

Hi again,

I found that ZED X driver version 0.6.1 for JP 5.1.2 doesn’t support Orin NX 8GB Ram (p3767-0001) devkit. After installed the driver, in extlinux.conf it use this DTB FDT /boot/stereolabs/tegra234-p3767-0001-p3768-0000-a0.dtb but this file is not available. I only saw tegra234-p3767-0000-p3768-0000-a0.dtb and tegra234-p3767-0003-p3768-0000-a0.dtb. So I changed the dtb in extlinux.conf to FDT /boot/stereolabs/tegra234-p3767-0000-p3768-0000-a0.dtb, it starting to work.
Can you please add support for Orin NX 8GB RAM in next release?

Now I changed to use short cables, 5cm CSI cables. It starts working, but the left & right image is just noisy

and the board hangs after short time.
The diagnostic at first (before running Explorer or Depth_Viewer) shows all good.
I have tried connecting ZED X Mini camera to all 4 GMSL2 ports, but all the same noisy output.
Do you have any idea about this problem?

Thank you.

Myzhar · January 26, 2024, 2:58pm

@linh.nguyen thank you for reporting the compatibility issue. The team will fix it as soon as possible.

Are the noisy images coming from the Orin NX 8GB module?

linh.nguyen · January 27, 2024, 8:00am

Hi @Myzhar,

Yes, it is on Orin NX 8GB module. I don’t have Orin NX 16GB module to test yet.

Myzhar · January 29, 2024, 8:21am

@linh.nguyen I can confirm that the device 3767-0001 is missing from the build/installer.
We are fixing this problem in the next release.

linh.nguyen · January 29, 2024, 2:38pm

Hi @Myzhar ,

Thank you for the confirmation regarding Orin NX 3767-0001. Do you have a roughly timeline when the release will be available?
In the picture & in my first post, I’m using Orin NX 16GB 3767-0000. I made a pair short cables now (6cm). But still not able to connect, ZED_Diagnostic give failed on camera test, diagnostic file & dmesg is still the same as the first post. Do you have any idea?

zedx_connect_short1920×1440 180 KB

Console output

~$ ZED_Diagnostic 
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
"Errors occurred<br />A detailed report can be saved to be shared with support if needed.<br />"
"<b>Specific resolutions are not available</b> <br/> Replug your device or connect the camera to another <b>USB 3.0</b> port."

dmesg.log (10.3 KB)
ZED_Diagnostic_Results.json (5.2 KB)

Myzhar · January 30, 2024, 8:51am

The team is on it. We are going to release the update very soon.

We are analyzing all the information that you forwarded and we’ll get back if we can find a plausible cause for this issue.

lguerlin-sl · January 30, 2024, 9:52am

Hi @linh.nguyen ,

Can you try to reduce the MIPI bandwidth and boost the ISP/VI/NVCSI clocks?

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

Thanks!

linh.nguyen · January 30, 2024, 10:51am

Hi @lguerlin-sl ,

I have reduced MIPI bandwitdth + boost the clocks as suggested. It still gives the same log/output as in my previous post.

Thank you.

lguerlin-sl · January 30, 2024, 11:13am

@linh.nguyen , I think it is related to the Waveshare carrier board you are using. MIPI lanes data polarity might be changed compared to the Orin Nano/NX devkit.

Are you running L4T35.3?

linh.nguyen · January 31, 2024, 8:00am

Hi @lguerlin-sl ,
I’m using L4T 35.4.1 (Jetpack 5.1.2).

I don’t have NVIDIA Orin carrier board here to verify this. But have you ever seen issues with WaveShare Orin carrier board?

Thank you.

lguerlin-sl · January 31, 2024, 8:58am

Hi @linh.nguyen,

I never got the WaveShare carrier board in my hands, so we did not do the integration on this one. I will compile a new dtb for you to test my theory.

Best regards

marshallm900 · February 3, 2024, 12:06am

Hey! Is there a chance this could also be the same issue on a Xavier NX carrier board when it is used with an Orin NX SOM?

We were very early adopters of the Orin NX and as such have been using it with Xavier NX carriers for a while. I’d prefer not to have to source more Orin Nano carriers if there was a way to make it work. I’m going to speculate that the waveshare carrier is based on the Xavier NX carrier and might have the same issue.

lguerlin-sl · February 5, 2024, 12:24pm

Hi @marshallm900 ,

I am not sure we are talking about the same issue, but there is a high probability we are.

I think the issue you mentions is related to a CSI lane polarity switch on CSI input A on the Orin NX SOM when compared to the Xavier NX.

My guess is that Waveshare routed the CSI port A with correct polarities, while most of the devkit types of carrier boads require a lane polarity swap (including the Orin Nano devkit if I remeber well).

marshallm900 · February 5, 2024, 12:40pm

Fair enough. I honestly haven’t gotten into the weeds on it yet. We’re trying to source more Orin Nano DevKit boards. We know they work. It is odd though that the Xavier NX devkit boards don’t work with the Orin NX though - they seem to work for everything else and NVIDIA (at least at one point) claimed they were compatible.

lguerlin-sl · February 5, 2024, 6:17pm

I am currently out of office, but I will try to ship the device tree to @linh.nguyen by wednesday to settle this issue. If it doesn’t work, we will try to get our hands on a carrier board to fix it.

linh.nguyen · February 7, 2024, 2:30am

Hi,

Our electrical did measure the pins and confirmed that the CSI pins on waveshare carrier board is the same as Nvidia carrier board. We are using Orin carrier board, Waveshare also confirmed the carrier board is compatible with Orin Nano carrier board. I think the polarity of CSI should be the same.

We are ordering the Orin Nano devkit to check.