Hello,
We are currently developing a custom embedded system that interfaces with the StereoLabs one ZED X and one ZED X mini camera via GMSL2, but not using the ZED Link capture card. Instead, we are utilizing our own carrier board equipped with a MAX96712 deserializer, connected to a custom soc platform running Linux(ubuntu 22.04,aarch64), with a custom driver stack managing the GMSL interface.
It needs to be clarified that our requirement only requires obtaining the color maps of Zed x and zed mini, and does not require obtaining the depth map;
Our custom SOC does not support CUDA.
From what I understand, the ZED SDK is designed to work with the ZED Link hardware, which includes drivers and capture logic tightly integrated with the SDK. What’s currently unclear is whether the SDK can function with alternative GMSL hardware setups, like ours, or whether it is dependent on proprietary ZED Link components.
We would appreciate clarification on the following points:
Is it possible to substitute our own MAX96712-based GMSL hardware and drivers for the ZED Link, and still use the ZED SDK with the ZED X camera and ZED mini camera on our custom soc?
Is there a defined driver interface or protocol that the SDK expects, which we can conform to? Or is the integration reliant on proprietary functionality unique to the ZED Link?
If necessary, can StereoLabs provide source code or documentation for the ZED Link drivers or low-level interface, to help us implement SDK compatibility?
Would access to that driver source code require an NDA or other legal agreement?
We’re particularly interested in understanding what the SDK expects from the video stream (e.g., format, metadata), device interfaces (e.g., /dev/videoX), and control paths (e.g., I2C commands). Any documentation, examples, or guidance you can offer would be greatly appreciated.
Thank you,
Jumby
26.07.27