Multiple GMSL2 carrier board options for Jetson Orin laid out for comparison before purchase
gmsl2carrier boardjetson orinhardware selectionbsp

Choosing a GMSL2 carrier board for Jetson Orin: what to check

Aaron Angulo ·

Choosing a GMSL2 carrier board for Jetson Orin is not just about whether it has the right number of GMSL2 ports. The PCB routing quality, impedance control, and power delivery to the MAX9296 matter as much as the port count — and these differences only become visible during bring-up. This post covers what to check before you buy.

Key Insights

  • Deserializer chipset and port count determine maximum camera count — verify before committing to a carrier board
  • BSP quality varies dramatically between vendors — a carrier board without a validated GMSL2 BSP is just hardware
  • GMSL1 (MAX9286) and GMSL2 (MAX9296A/MAX96724) are different technologies with different drivers — verify which generation the board uses
  • Ask vendors specifically: supported sensors, tested JetPack version, and BSP update cadence
  • An integrated GMSL2 carrier board is simpler than an adapter board approach, but limits future camera flexibility

The four things that determine carrier board fit

Choosing a GMSL2 carrier board for Jetson Orin is not just a hardware purchase. The board’s BSP, the deserializer chipset, and the vendor’s support posture determine whether you are buying weeks of bring-up time or months of it.

Port count. How many cameras do you need? MAX9296A boards support 2 GMSL2 cameras. MAX96724 boards support 4. MAX96722 supports 8 but requires a custom or vendor-provided driver. Count your cameras, add one for development flexibility, then check the board specs.

Deserializer chipset. NVIDIA’s L4T R36 has reference drivers for MAX9296A and MAX96724 for specific configurations. If the board uses MAX96722, GMSL1 chipsets (MAX9286), or a newer Analog Devices part without L4T support, expect driver work.

BSP quality. A carrier board without a working GMSL2 BSP is hardware without a software stack. Ask for specifics: which sensors are supported, which JetPack version is validated, and what happens when JetPack is updated.

Physical connector type. GMSL2 cameras use FAKRA, Mini-FAKRA, or HSD connectors depending on the camera module. The carrier board must match your camera connector type, or you need adapters that add reliability risk.

Established GMSL2 carrier board vendors

These vendors have documented GMSL2 support with BSPs for Jetson Orin:

VendorNotable GMSL2 boardsBSP approach
Leopard ImagingLI-Orin-GMSL2-4CAMBundled sensor drivers for their camera modules
FRAMOSFSA-FPA seriesFRAMOS camera ecosystem BSP
Connect TechRogue, Boson carrier boardsCTI board support packages, JetPack-aligned
Tier IVIE-4000Automotive-grade, TIER IV sensor ecosystem

These vendors produce GMSL2 carrier boards as a core product, which means their BSPs get maintained when JetPack updates. A generic carrier board vendor who lists GMSL2 as a feature but has no camera sensor in their supported list is a different situation.

Questions to ask before buying

“Which specific sensors is your GMSL2 BSP validated with?” A good answer names specific sensors (IMX390, IMX728, etc.) with JetPack version numbers. A bad answer is “any GMSL2-compatible sensor.”

“What JetPack version is your BSP currently validated on?” If the answer is JetPack 5 and you are shipping on JetPack 6, you have a migration project built into your timeline.

“How are BSP updates delivered when NVIDIA releases a new JetPack?” Good vendors have a release cadence. Others ship one BSP and never update it.

“Do you provide the device tree source for your GMSL2 configuration?” If you need to modify the DTS (different sensor, different camera count), you need the source. Binary-only BSPs are a lock-in risk.

“Can your driver framework support custom sensors not in your list?” Some vendors have a plugin architecture for adding sensors. Others require full driver re-implementation.

What to watch out for in specs

“Supports GMSL2” without chipset detail. Always ask which Analog Devices part is on the board. MAX9286 is GMSL1, not GMSL2. The software stack is completely different.

Port count vs. camera count. Some boards advertise camera count based on daisy-chaining that requires non-standard wiring. Verify whether the advertised count is direct-connect ports.

“BSP available on request.” This usually means it exists but has not been recently validated. Ask for the JetPack version it was last tested on.

MAX96722: the 8-port deserializer

The MAX96722 from Analog Devices supports up to 8 GMSL2 inputs on a single chip — useful for high-camera-count deployments like autonomous vehicles or multi-view inspection systems.

What sets it apart: Unlike MAX9296A (2-port) and MAX96724 (4-port), the MAX96722 has no reference driver in NVIDIA’s L4T. NVIDIA’s kernel source includes drivers for MAX9296A and MAX96724 for specific configurations; MAX96722 requires either a custom driver or a vendor-provided BSP.

Implications for carrier board selection: If you’re evaluating a carrier board that uses MAX96722, ask the vendor:

  • Do you ship a kernel driver for MAX96722?
  • Which JetPack version is it validated on?
  • Is the driver source available, or is it binary-only?

Boards from Tier IV and some Leopard Imaging configurations have MAX96722 BSP support. Most generic carrier board vendors don’t — they may list MAX96722 as a supported chip but provide no driver.

DTS note: The MAX96722 connects to Jetson via multiple MIPI output ports. A full 8-camera configuration requires careful NVCSI port mapping in the device tree — 8 cameras split across multiple NVCSI ports depending on the SoC’s lane count. This DTS work is more complex than a 2-port or 4-port configuration and usually requires bring-up support.

If you’re selecting a carrier board with MAX96722 and need driver development or DTS configuration, ProventusNova handles GMSL2 bring-up including MAX96722 configurations.

For the GMSL2 bring-up process once you have your board, see GMSL2 camera bring-up on Jetson Orin: MAX9295/MAX9296 setup. For what to expect when bringing up GMSL2 on a custom carrier board versus a devkit, see GMSL2 cameras on a custom carrier board: what’s different.

Analog Devices’ GMSL2 product selector for their deserializer family is at the Analog Devices GMSL product page. NVIDIA’s supported carrier board list for Jetson Orin is in the Jetson Partner Hardware Catalog.


NVIDIA Jetson Expert Support

Stuck on a Jetson bring-up?

We've debugged this failure mode before. BSP, device tree, camera pipelines, OTA — most blockers clear in the first session. No long retainers. No guessing.

Frequently Asked Questions

What is the maximum number of GMSL2 cameras a Jetson Orin AGX can support?

Jetson AGX Orin has 6 NVCSI ports and supports up to 16 MIPI lanes. A practical maximum for GMSL2 cameras depends on the deserializer chipset. With MAX9296A (2-port) + MAX96724 (4-port) combinations, you can reach 6-8 synchronized cameras depending on per-camera lane count. At 2 lanes per camera, 8 cameras is achievable. At 4 lanes per camera for higher resolution, 4 cameras per MIPI link set is more realistic.

Which deserializer chipsets should I look for in a GMSL2 carrier board?

MAX9296A (2-port), MAX96724 (4-port), and MAX96722 (8-port) from Analog Devices are the most common. NVIDIA's L4T R36 provides reference drivers for MAX9296A and MAX96724 for specific carrier board configurations. MAX96722 requires a custom driver or vendor-provided BSP. Boards using older chipsets (MAX9286) are GMSL1, not GMSL2 — verify which generation the board uses.

Does the carrier board vendor provide a BSP with GMSL2 drivers?

Some do, most don't. Established GMSL2 carrier board vendors — Leopard Imaging, FRAMOS, Connect Tech — provide BSP packages with camera drivers for specific sensor modules. Generic carrier board vendors without a camera focus typically provide only the base L4T BSP without GMSL2 drivers. Always ask the vendor: which sensors are supported, which JetPack version is the BSP validated on, and what is the maintenance cadence for BSP updates.

What is the difference between a GMSL2 carrier board and a GMSL2 adapter board?

A GMSL2 carrier board is a full carrier that hosts the Jetson SoM and includes integrated GMSL2 deserialization hardware (MAX9296A or similar) on-board. A GMSL2 adapter board is an add-on (via PCIe, USB, or CSI extension) that adds GMSL2 ports to an existing carrier board. Adapter boards have more integration complexity and sometimes have bandwidth limitations that integrated carrier boards avoid.

How do I evaluate whether a carrier board vendor's GMSL2 BSP will actually work for my sensor?

Ask the vendor for a list of sensors their BSP has been tested with and which JetPack version. Then check whether your sensor is on that list. If it is not, ask specifically whether their GMSL2 driver framework supports adding custom sensors — some do via a plugin architecture, others require full driver re-implementation. A vendor who cannot answer these questions clearly does not have a mature BSP.

Aarón Angulo, Co-Founder & CEO at ProventusNova

Written by

Aarón Angulo

Co-Founder & CEO · ProventusNova

Obsessed with client outcomes. Aarón ensures every engagement delivers real results — on time, on scope, no exceptions.

Connect on LinkedIn