Hi,
I’m setting up a ZED Link Duo GMSL2 capture card on a Jetson Orin (p3768 carrier board) running Jetson Linux (L4T) R36.5.0. The driver installs without error, but ZED Diagnostics reports no GMSL driver found, and I’ve traced this down to the device tree itself never containing the camera overlay content.
Steps taken:
- Installed the driver with:
sudo dpkg -i stereolabs-zedlink-duo_1.4.3-LI-MAX96712-L4T36.5.0_arm64.deb
The install log reports:
Detected DTB to update : tegra234-p3768
Detected capture card : zedlink-duo
Set FDT to : /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb
2. Rebooted. dmesg shows the correct kernel command line for the Stereolabs extlinux entry, and /proc/device-tree/compatible correctly shows nvidia,p3768-0000+p3767-0005-super, confirming the right boot entry and DTB file were loaded.
3. However, sudo dmesg | grep -iE ‘zedx|gmsl|max96712’ returns nothing, and find /proc/device-tree -iname ‘*max96712*’ -o -iname ‘*gmsl*’ returns nothing.
4. I decompiled the DTB the installer produced (kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb) with dtc -I dtb -O dts, and it contains no max96712 or gmsl nodes at all. It appears to be functionally identical to the stock carrier board DTB, not a DTB with the ZED Link Duo camera overlay merged in.
5. As a test, I manually merged the installed overlay (/boot/tegra234-p3768-camera-zedlink-duo-sl-overlay.dtbo) onto the base DTB myself using fdtoverlay, and confirmed with dtc that the resulting file does contain the expected max96712_a@29 (compatible = “stereolabs,sl_max96712”) and zedxone_hdr_1@4f nodes. So the .dtbo file itself is valid — it’s specifically the DTB the installer produces/points FDT to that is missing this content.
6. I tried pointing extlinux.conf’s FDT line directly at my manually merged DTB, and separately tried writing that merged DTB directly into the active kernel-dtb partition (A_kernel-dtb) via dd, confirmed via readback/cmp that the write was byte-for-byte correct, and rebooted. In both cases, /proc/device-tree still showed no GMSL/max96712 nodes after reboot, and dmesg still showed nothing. Secure boot is disabled on this device, so that’s not a rejection mechanism.
This suggests the DTB the installer itself generates and points FDT to is missing the camera overlay content, and that a plain fdtoverlay merge isn’t sufficient to reproduce whatever your official tooling does to bind the overlay correctly (possibly related to plugin-manager / board-ID matching in the overlay).
Could you let me know what I should do next?
Happy to provide any files if useful.