Hi everyone,
I’m trying to use a ZED X camera on a Jetson Orin NX 16GB mounted on a TwoWin TW-T808P-G carrier board via GMSL2.
Setup:
- Jetson Orin NX 16GB, JetPack 6.2.1 (L4T R36.4.3)
- TwoWin TW-T808P-G carrier board
- MAX96712 deserializer connected to Jetson CSI port-index 0 (serial_a), 4-lane CSI
- Built Stereolabs BSP drivers from zedx-driver-bsp (L4T 36.x branch), all v1.4.0
- Custom device tree overlay adapted for TwoWin’s hardware
What’s working:
- All three kernel modules load and probe successfully
- GMSL2 link is active, camera detected on correct port
- Camera serial number confirmed, “camera pipeline operational”
- /dev/video0 and /dev/video1 created
- ZED SDK detects the camera as “AVAILABLE”
What’s NOT working:
- V4L2 capture always times out: “uncorr_err: request timed out after 2500 ms”
- No video data flows from deserializer to Jetson VI
- ZED SDK fails with “CAMERA FAILED TO SETUP”
Details:
TwoWin’s carrier board uses 4-lane CSI (bus-width=4, opt-csi-port=“a”). The driver reports “Setup Deser as 4 lanes output” which is correct. However, it seems like the 4-lane CSI output mode may not be fully initializing the deserializer’s output — the 2-lane mode works on Stereolabs’ own carrier boards but 4-lane mode on a third-party board does not.
I’ve confirmed the correct CSI wiring with TwoWin (port-index, lane count, lane polarity) so the device tree overlay is correct.
Questions:
- Is 4-lane CSI mode (2x4) fully supported in the current BSP driver (v1.4.0)?
- Is there a newer driver version with improved support for 4-lane CSI configurations?
- Has anyone successfully used ZED X on a third-party carrier board that uses 4-lane CSI?
- Are there any additional device tree properties or driver configurations needed for 4-lane mode on non-Stereolabs boards?
Happy to share dmesg logs or device tree overlay privately if it helps debug.
Thanks!