Skip to content

Cart

Your cart is empty

What is GMSL and When Should You Use it for AI vision?

Updated on: November 11, 2026

GMSL (Gigabit Multimedia Serial Link) is a cable link that sends camera video, control signals and power over a single cable. It lets you mount cameras where they see best and keep the computer somewhere safe, several metres away if the design needs it. For AI vision, that means more freedom in where cameras go.

 

Most vision projects start with the same awkward fact: the best place for a camera is rarely the best place for a computer. A camera belongs on a bumper, a robot arm or a mast. The computer belongs in a protected, cooled enclosure. If your embedded system can't sit next to its cameras, you need a link that carries frames across that gap without drama. GMSL is one of the main options, and it comes with trade-offs worth knowing before you design around it.

 

Title

What does a GMSL link actually consist of?

A GMSL link has two chips and one cable. A serializer next to the image sensor packs the video into a serial stream, the cable carries it, and a deserializer at the computer unpacks it and passes it on over MIPI CSI-2. The same cable also carries control signals and, with Power over Coax, the camera's power.

 

That design keeps the camera small. Between the lens and the cable there is the sensor and the serializer, and no camera-side processor. At the computer end, one deserializer can handle several camera links, so a robot with four cameras can run four thin cables to a single board.

 

Control travels the same way. The host configures the sensor over the same cable, so you don't need a second cable for settings. And because the sensor speaks MIPI at one end and the deserializer speaks MIPI CSI-2 at the other, GMSL doesn't replace MIPI. It extends it. NVIDIA's reference setup for Jetson is wired exactly like this.

When does GMSL beat GigE Vision or USB?

GMSL wins when several cameras sit a few metres from the computer and you need low, predictable delivery and cameras that capture together. GigE Vision wins on distance and on plug-and-play software. USB suits prototypes. Direct MIPI suits cameras mounted right next to the board. 

Your situation Better fit Why
Three to four cameras a few metres from a Jetson, with synchronised capture GMSL Each camera gets its own link, and settings and power travel on the same cable.
Cameras tens of metres away, or already on a plant network GigE Vision Uses standard Ethernet cabling and equipment.
One camera mounted on the carrier board Direct MIPI CSI-2 No serializer or deserializer needed.
Quick bench prototype USB Plugs into almost any host with little setup.

Run the numbers on a typical case. One 1080p, 30 fps, 12-bit stream carries about 0.75 Gbps of pixel data (1920 × 1080 × 12 × 30). Four cameras total about 3 Gbps. On GMSL each stream has its own link. On a single 1 Gbps Ethernet uplink the same four streams wouldn't fit, so you'd need several ports or a faster link. Move the cameras tens of metres away and the answer flips, because long runs are where Ethernet cameras are strongest.

 

One practical trade-off: ask early who writes and maintains the camera driver. With GMSL it is usually part of the project, while GigE Vision cameras are closer to plug and play, so budget engineering time for it.

Title

What does GMSL change inside an AI vision pipeline?

GMSL doesn't change your model's accuracy, but it affects what the model receives. It gives each camera a dedicated path, keeps the camera itself simple, and makes it practical to trigger several cameras together, so multi-camera images are captured at the same moment.

 

Synchronisation is where this pays off. A robot moving at 2 m/s travels 2 cm in 10 ms, so two cameras that expose 10 ms apart see a scene that has shifted by 2 cm between views. Anything that stitches or measures depth across both images inherits that error. So ask any supplier how a trigger reaches every camera and how you can check it.

 

Two limits are worth knowing. If you need a shared clock across the cameras and the computer, plan for timestamps in your software design and don't assume the link provides them. And a better cable won't fix a detector that misses objects at night. Lens, exposure and training data still decide accuracy. GMSL just makes sure the frames you designed for are the frames that arrive.

Title

How do you budget bandwidth, cable length and power?

Check three numbers before you choose cameras: data rate, cable length and power. Add up the data rate of every camera, ask your supplier for the cable length they actually tested, and keep camera power under the port limit, such as 6.6 W per channel on the DSADDON-GMSL-NX at 11 V and 600 mA.

 

Data rate: multiply pixels by bits by frames per second. A 1080p, 30 fps, 12-bit stream is about 0.75 Gbps. An 8 MP (3840 × 2160) stream at the same settings is about 3 Gbps. A full set of eight 1080p cameras, the maximum on FORECR's GMSL boards, would send about 6 Gbps in total. These figures ignore overhead, so leave headroom, and remember the Jetson has to absorb the total.

 

Cable length: don't take a length from a brochure. Ask for the cable type and length your supplier tested with your exact camera, and remember that connectors, bends and heat all eat into the margin. Then test with your real cable.

 

Power: at 11 V and 600 mA, a channel delivers at most 6.6 W before cable losses. The DSADDON-GMSL-THRMAX supplies 12 V at the same current, or at most 7.2 W. A 2.5 W camera fits easily. An 8 W camera with an infrared illuminator doesn't, and needs its own supply. These camera loads are examples, so check your camera's own limits.

 

Title

What should you check before choosing a GMSL camera for Jetson?

Check that your exact camera, serializer, deserializer, carrier board and Jetson Linux release have been tested together. 

 

NVIDIA's reference setup, for instance, was validated on Jetson AGX Orin with Sony IMX390 sensors and a MAX9295 and MAX9296 pair. A camera labelled GMSL2 is not enough on its own. 

 

NVIDIA describes that module as a starting point for bringing up another one, not as a compatibility list. A different sensor or carrier board means driver and device-tree work. Treat "GMSL2 camera" as the start of your questions, not as a specification.

 

So ask your supplier five things, in writing: the camera model and sensor modes, the serializer and deserializer part numbers, the carrier board and Jetson module, the Jetson Linux release, and who maintains the driver after an update. If you're still choosing a module, our Jetson embedded systems guide covers the families. For a worked configuration, the ZED X camera guide shows DSBOARD-ORNX-LAN with a GMSL2 camera board on JetPack 6.

 

How should you test a GMSL setup before committing?

Test the complete setup in its final layout before you commit to a design. Run every camera at full resolution and frame rate for hours, unplug and replug a camera to check recovery, move a target across overlapping views to check synchronisation, and log dropped frames next to your model's results.

The final layout matters because cable bends, connector retention and nearby motors or power electronics change what the link sees. A bench test with a short cable proves less than it appears to.

Agree what "passing" means before the test starts, for example no dropped frames over a long soak and every camera returning after a replug. Logging frame counters and link errors beside inference results also tells you quickly whether a bad detection came from the model or from the transport.

A short example plan: power the system up from cold ten times, run an overnight soak with all cameras streaming, replug each camera in turn, then repeat the soak with the final cable routing and the motors running. Treat the numbers as a starting point and adjust them to your duty cycle.

Title

Which FORECR GMSL board fits your Jetson?

FORECR offers three GMSL2 camera boards, each matched to a Jetson platform. The DSADDON-GMSL-NX serves Orin NX and Orin Nano systems, the DSADDON-GMSL-AGX-8CH serves Jetson AGX Orin, and the DSADDON-GMSL-THRMAX fits the DSBOARD-THRMAX carrier board. All three supply Power over Coax at up to 600 mA per channel. 

Board Built for Cameras Connectors Power over Coax Input
DSADDON-GMSL-NX Orin NX and Orin Nano Up to 8 MMCX (default) or Quad Mini-FAKRA 11 V, up to 600 mA per channel 12–36 V DC
DSADDON-GMSL-AGX-8CH Jetson AGX Orin Up to 8 MMCX 11 V, up to 600 mA per channel 12–36 V DC
DSADDON-GMSL-THRMAX DSBOARD-THRMAX Up to 8 Quad Mini-FAKRA 12 V, up to 600 mA per channel 18–36 V DC

Choose by Jetson platform first, because each board is built for a specific module or carrier. Then check the connector. The NX and AGX boards use locking MMCX connectors, which the datasheets recommend for IP-rated systems. The THRMAX board uses Quad Mini-FAKRA. Finally, compare the input voltage range with your power supply and the camera's draw with the per-channel limit.

 

Every camera output has current limiting and ESD protection, and the NX and AGX boards are specified for −40 °C to +85 °C operation. If your project needs something different, such as another connector, the customization service can adapt a board to your layout.

Title

Need help?

Frequently Asked Questions