The GMSL Camera Interface: Integrating Stereolabs ZED X with NVIDIA Jetson

The GMSL camera interface is the serialiser–deserialiser link that carries uncompressed video, power and control from a camera such as the Stereolabs ZED X to an NVIDIA Jetson over a single coaxial cable, ending as MIPI CSI-2 at the Jetson module. It is what lets a robot or vehicle place several synchronised cameras metres from its computer without USB’s cable limits or Ethernet’s packet handling.

The Stereolabs ZED X is built for robotics and industrial machine vision, and it connects over GMSL2 rather than USB. That choice buys long cable runs, rugged locking connectors and tight multi-camera synchronisation, which is exactly what an outdoor robot or a production cell needs.

It also means the camera cannot simply be plugged into a Jetson and recognised. The GMSL2 signal has to be deserialised back to MIPI CSI-2 on the carrier board, and the Jetson has to be told how to read it. That is a board support package job, and it is where most ZED X on Jetson projects stall. This guide covers how the interface works, how it compares with other camera links, which Jetson systems support GMSL cameras, and what the integration involves.

Each camera interface suits a different distance, bandwidth and level of integration. The table compares the links used on edge AI computers; figures are typical and depend on the exact parts and cables.

GMSL vs MIPI CSI-2. They are partners rather than rivals. MIPI CSI-2 is the camera interface the Jetson reads; GMSL extends it from centimetres to metres. A CSI-2 camera on a flex cable suits a sealed smart camera, while GMSL suits cameras mounted around a machine.

GMSL vs FPD-Link. FPD-Link from Texas Instruments is the other automotive SerDes family. The two work the same way, but they are not interoperable: a GMSL camera needs a GMSL deserialiser. The ZED X range and most industrial robot cameras use GMSL2.

GMSL vs GigE Vision and USB. GigE Vision cameras run further and use standard networking, and PoE powers them, but the host has to reassemble frames and synchronisation relies on PTP. USB cameras such as the ZED 2i are the simplest to start with and suit short, fixed installations.

A GMSL camera is a camera with a GMSL serialiser built in. GMSL, or Gigabit Multimedia Serial Link, is a serialiser–deserialiser interface for moving uncompressed high-resolution video over a single coaxial cable. A serialiser on the camera packs the sensor data onto the coax; a deserialiser on the host board unpacks it back into MIPI CSI-2, the interface the Jetson actually reads.

For the ZED X that deserialiser is typically an Analog Devices (formerly Maxim) MAX9296A on a one- or two-camera board, or a MAX96712 where four cameras share one quad deserialiser. Stereolabs ship this silicon as the ZED Link family of capture cards and the ZED Box Mini, but the same parts appear on partner Jetson carrier boards designed for camera-heavy edge AI.

Most GMSL cameras on Jetson today, including every ZED X model, are GMSL2. GMSL3 doubles the rate for higher-resolution sensors, and GMSL1 survives in older automotive cameras. Our explainer on GMSL2 covers the current generation in brief.

GMSL3 parts can run GMSL2 modes, so GMSL2 cameras work on GMSL3 deserialisers set to GMSL2. A single ZED X at full resolution needs a fraction of a GMSL2 link, so GMSL3 matters for 4K cameras at high frame rates rather than for today’s stereo cameras.

The path is the same whichever board you use. The ZED X serialises its stereo sensors onto GMSL2 coax. At the carrier board the deserialiser converts GMSL2 to MIPI CSI-2 and forwards it across the Jetson module connector. The Jetson camera subsystem then exposes it as a V4L2 device that the ZED SDK can open.

GMSL2 also carries power and a back-channel for control and triggering. That back-channel is why ZED X capture over GMSL supports hardware synchronisation to around 15 microseconds across multiple cameras, an accuracy a USB camera chain cannot reach. Synchronised capture is what makes stereo depth, multi-camera fusion and SLAM on a moving robot reliable; our comparison of global shutter vs rolling shutter explains why every ZED X stereo model uses global shutter sensors for the same reason.

A GMSL2 camera can typically sit up to about 15 m from the deserialiser over automotive coax. The ZED Link Mono product data quotes the same figure for ZED X cameras on Stereolabs GMSL2 FAKRA cables. Reach is limited by the cable’s signal loss rather than by a fixed length, so cheap or thin coaxial cable, extra in-line joints and high temperatures shorten it.

Yes, GMSL carries power. Power over Coax puts the camera’s DC supply on the same cable as the video and control channels; the ZED Link cards supply 12 V to the camera. That leaves one cable per camera on a robot arm or a vehicle body, with Z-coded FAKRA connectors that lock and cannot be plugged into the wrong port.

Every current Jetson module can take GMSL cameras through a deserialiser, from Orin Nano to Thor. What changes is how many cameras fit, which boards carry the deserialiser, and whether a ZED X driver already exists for that board. The matrix lists systems and capture cards from our range; the deserialiser is given where the manufacturer publishes it.

“Board support package work” means the camera can be made to run, but the ZED X driver and device tree have to be built and validated for that board and JetPack release, as the next section explains. Where a project has no strong reason to use another board, a ZED Link card or ZED Box Mini is the shortest route. Our guide to the Jetson modules compared helps size the module for the number of cameras.

Stereolabs publish ready-made drivers for their own ZED Link cards and for several reference Jetson developer kits. On those, installation is close to a single command: a deb package drops in the kernel module, the device tree and the ZED daemon, and a reboot applies them.

The moment the carrier board is not one of those reference designs, the device tree no longer describes the hardware. The CSI lane mapping, the deserialiser address and the GPIO assignments are board-specific, and a mismatched device tree shows up as a V4L2 capture timeout: the camera looks present but never delivers a frame. Resolving that means taking the deserialiser driver and rebuilding the device tree against the actual carrier board, then validating capture and synchronisation. Our guides to NVIDIA JetPack and to choosing a Jetson carrier board cover the software and hardware sides.

Stereolabs build their GMSL2 range in two families: stereo depth cameras and single-sensor ZED X One cameras. All take the same ZED Link cards and ZED SDK, so a robot can mix them on one Jetson. Figures are from our product pages.

Polarised builds of the ZED X and ZED X Mini cut glare from wet tarmac, glass and water outdoors. The full range is on our Stereolabs page.

Several of the rugged Jetson carrier boards and box PCs we work with already carry a GMSL deserialiser and FAKRA camera ports, which makes them a natural starting point for a ZED X build. As the system integrator, our job is to recommend the right computer for the application first, often one where the camera is already supported, and then take on the board support package work where it is needed: matching the ZED Link driver and device tree to the board and module, confirming the deserialiser configuration, and validating capture and multi-camera sync.

The result is a computer that arrives with the camera already enumerating, not a deserialiser the integrator still has to fight. For robots, our robot computer guide covers the rest of the onboard compute, and our ROS explainer covers the software framework most ZED X robots run.

Cameras and computers on machines face heat, water and vibration, and the GMSL link is only as reliable as the hardware at each end.

Our industrial temperature range explainer sets out what the ratings mean, and our Jetson thermal design guide covers sealed computers in the heat.