Does not detect ZED X Ones

Hardware
1

Hi!

We still have issue detecting our ZED X ones

System/context:

Jetson Orin NX
ZEDBox Mini / MAX9296 setup
L4T: R36.4.7
Kernel: 5.15.148-tegra
Ubuntu: 22.04.5
ZED SDK: 5.1.2
stereolabs-zedbox-mini: 1.4.2-SL-MAX9296-ZEDBOX-MINI-L4T36.4.0

The original issue is still:

No /dev/video*
ZED_Explorer --all -> No ZED detected

and in dmesg:

of_i2c: modalias failure on /bus@0/i2c@3180000/zedxone_uhd_ser@44
of_i2c: modalias failure on /bus@0/i2c@3180000/zedxone_uhd@1a
sl_max9296: probe of 2-0048 failed with error -1

Initially we suspected this might be caused by the system booting with the Super DTB:

/boot/dtb/kernel_tegra234-p3768-0000+p3767-0001-nv-super.dtb

so we added a separate test boot entry using the normal DTB:

FDT /boot/tegra234-p3768-0000+p3767-0001-nv.dtb

However, the camera issue stayed the same:

No /dev/video*
ZED_Explorer --all -> No ZED detected
sl_max9296: probe of 2-0048 failed with error -1

We then decompiled the installed overlay:

/boot/tegra234-p3768-camera-zedbox-mini-sl-overlay.dtbo

Found that the malformed nodes seem to be present in the DTBO itself, not just as a runtime artifact.

The overlay contains complete-looking nodes:

zedxone_uhd_0@1a
zedxone_uhd_ser_0@44

but it also contains non-suffixed/incomplete nodes:

zedxone_uhd@1a
zedxone_uhd_ser@44

The non-suffixed serializer is explicitly labeled in __symbols__ as:

dummy_zedxone_uhd_ser

From the decompiled DTS:

complete sensor:
zedxone_uhd_0@1a
compatible = "stereolabs,zedxone_uhd"
reg = <0x1a>
phandle = <0x4a>

complete serializer:
zedxone_uhd_ser_0@44
compatible = "stereolabs,sl_max9295"
reg = <0x44>
camera-sensors = <0x4a>
phandle = <0x39>

malformed / dummy-like sensor:
zedxone_uhd@1a
phandle = <0x3f>
missing compatible
missing reg

malformed / dummy serializer:
zedxone_uhd_ser@44
camera_model = "zedone4k"
zedx-id = "-1"
camera-sensors = <0x3f>
phandle = <0x3e>
missing compatible
missing reg

dtc also warns that the malformed zedxone_uhd@1a and zedxone_uhd_ser@44 nodes have unit addresses but no reg.

The part that looks especially suspicious is that max9296_a@48 has:

camera-serializers = <0x35 0x36 0x37 0x38 0x39 0x3a 0x3b 0x3c 0x3d 0x3e>;

where:

0x39 -> complete zedxone_uhd_ser_0@44
0x3e -> dummy/non-suffixed zedxone_uhd_ser@44

So the MAX9296 node seems to reference both the complete serializer and the dummy serializer.

This seems to match the live boot errors:

of_i2c: modalias failure on .../zedxone_uhd_ser@44
of_i2c: modalias failure on .../zedxone_uhd@1a
sl_max9296: probe of 2-0048 failed with error -1

Could you confirm whether this is expected?

Specifically:

  1. Is dummy_zedxone_uhd_ser supposed to be included in the active camera-serializers list of max9296_a@48?

  2. Should the non-suffixed nodes zedxone_uhd@1a and zedxone_uhd_ser@44 exist as enabled I2C children even though they lack compatible and reg?

  3. Is there a newer/fixed ZEDBox Mini DTBO or driver package for L4T R36.4.7?

  4. Should we use a different driver package / JetPack version / L4T version for this setup?

  5. Could this MAX9296 probe failure be caused by the physical GMSL link, cable, camera power, or wrong port/channel configuration?

  6. Would you recommend a full normal-mode reflash, or is this more likely to reproduce the same issue if the same overlay is installed again?

thank you:)

2

Hi @hatfalk
Please run sudo ZED_Diagnostic --dmesg and post here the content of the dmesg.log report file that it generates.

Please also list the cameras that you want to connect to the ZED Box Mini device.
“ZED X Ones” is too generic. The ZED Box Mini has different behaviors when using ZED X One GS, ZED X One 4K, and ZED X One S.
Please read more here: