What Is a Jetson Carrier Board? How to Choose the Right One

A carrier board, also called a baseboard, is the circuit board a system-on-module plugs into, and for NVIDIA Jetson it is what turns a module into a working computer. The Jetson module carries the processor, GPU and memory; the carrier board breaks its interfaces out to real connectors and supplies the power, storage, mounting and form factor the product needs.

A Jetson module on its own cannot be deployed. Two systems with the same module can be completely different products depending on the carrier: one a sealed in-vehicle computer, the other an open development board. The module decides how much AI compute you have; the carrier board decides what you can connect it to and where it can go.

This guide explains what a Jetson carrier board does, which module fits which carrier, how the carriers in our range compare, when a custom board pays off and how to choose. You can use an off-the-shelf Jetson carrier board, adapt one, or design a custom board for the exact requirement.

The Jetson module connects to the carrier through a high-density connector, and the carrier exposes the module’s signals as the ports a product needs: power, networking, cameras, storage, serial and expansion. It also sets the form factor, the mounting and the operating envelope.

Carrier boards are not unique to Jetson. Any system-on-module needs one, and the same idea runs through x86 computer-on-module standards; our COM Express carrier boards and the comparison of SMARC, Qseven, OSM and COM Express cover that side. For the wider picture of the module, the JetPack software and where Jetson fits, see what NVIDIA Jetson is and how the platform fits together.

A carrier board is designed for one module family and connector, so the board and module have to be a pair. The table shows the connector families across current and recent Jetson modules.

Can you use a Jetson Orin NX on an Orin Nano carrier board? Usually, yes: the two share the SO-DIMM connector, and many boards are sold for both, as our Jetson Orin NX carrier boards show. Check that the carrier’s power stage covers the Orin NX at the mode you plan to run, and that the vendor’s board support package supports the module. Thor is different: our answer on whether Jetson Thor needs a new carrier board explains why an Orin board cannot take it, and the SO-DIMM explainer covers the smaller modules’ connector.

List the interfaces the product needs before you look at boards. The table shows what to look for in each area.

Cameras deserve particular care. Most Jetson carriers bring MIPI CSI-2 out on short flexible cables, which suits cameras mounted close to the board. Robots and vehicles with cameras metres away use GMSL2, which needs a deserialiser on the carrier or an add-on board; our guides to the GMSL camera interface on Jetson and MIPI CSI-2 cover both, and our GMSL frame grabbers add GMSL2 inputs where the carrier has none.

The matrix compares carriers from our range across the points that usually decide a design. Facts come from each product’s own specification.

Two patterns stand out. GMSL2 is usually an add-on rather than built into the carrier, so count the camera path as part of the board choice. And the input voltage range varies widely, from 7–20 V to 18–36 V, which matters on 24 V vehicles and 48 V robots. We fit the module, storage and wireless, add the camera boards the system needs and test the assembly before it ships.

A Jetson developer kit is itself a carrier board: NVIDIA’s reference design, with the module fitted and a generic set of ports for evaluation. It is the fastest way to bring up software and benchmark a module, but it is not built for any particular product. Our answer on the module versus a developer kit covers the difference in full. Once the module is chosen, the kit is set aside and the module moves onto a carrier built for the job.

Do I need a custom carrier board?

Usually not. Most projects start with an off-the-shelf carrier from an established maker: a known-good design, available now, with a common set of I/O. A custom carrier makes sense when the I/O, the form factor or the environment is specific enough that no standard board fits, or when volumes are high enough that a board with no unused parts pays back its engineering. Between the two sits a middle path: adapting an existing board, which covers many requirements without a full design.

A custom design follows a defined path. It starts from NVIDIA’s product design guide and reference schematics for the module, uses NVIDIA’s pinmux spreadsheet to assign the module’s pins, then moves through layout, power and signal-integrity checks, a board support package with its device tree, and prototype validation. Expect several board spins and plan the BSP maintenance for every future JetPack release, because that cost lasts as long as the product.

We take on all three routes. Our custom Jetson carrier board build shows the custom route, and the Osbourne-ER rugged carrier board for Jetson AGX Orin, with latching I/O for shock and vibration, shows how far an off-the-shelf board can go.

Yes. A board support package tells JetPack which connectors exist on a particular carrier: the device tree describes the cameras, Ethernet controllers, USB ports and GPIO, and the pinmux sets what each module pin does. NVIDIA’s BSP covers its own developer kits; every third-party carrier needs its vendor’s BSP, or one you build.

This has three practical consequences. Vendor BSPs often follow NVIDIA’s JetPack releases by weeks or months, so the newest JetPack may not yet support your carrier. A production fleet should pin one JetPack and BSP version and change it deliberately. And the carrier’s BSP lifecycle matters as much as the module’s, because a board without updates leaves the system on an old kernel. Our guide to NVIDIA JetPack explains how releases map to Jetson Linux, and JetPack 7.2 and Yocto for production Orin fleets covers the minimal-image route.

The carrier board supplies the module’s power and usually carries its thermal interface, so it has to be sized for the mode the system will run, not the module’s lowest rating.

Add the carrier’s own load on top: cameras, PoE ports, NVMe drives and wireless modules can add tens of watts. A carrier rated for 9–28 V DC also needs protection for the transients a vehicle produces, which is why vehicle carriers add surge protection and ignition control.

Carrier board lifecycle

For a product that ships for years, board availability and the module’s production life matter as much as the specification. NVIDIA publishes the module lifecycle; the carrier vendor sets the board’s. Ask how long the board will be built, how revisions are notified and how long the BSP will follow new JetPack releases. The early end of the Xavier and TX2 modules, covered in our guide to Jetson Xavier end of life, showed why a carrier that takes more than one module generation is worth having.

Take a rugged in-vehicle AI computer: an Orin NX module for multi-camera vision, four GMSL camera inputs, dual Gigabit Ethernet on M12 connectors, a CAN bus for the vehicle, an M.2 slot for cellular and a 9–36 V ignition-controlled power input, in a sealed, wide-temperature enclosure.

No single requirement is unusual, but the combination narrows the field quickly. A compact Orin NX carrier with two MIPI inputs needs a GMSL2 add-on board for four cameras; an AGX-class carrier has the camera lanes but more power and size than the job needs. An off-the-shelf rugged carrier may cover most of the list; if the camera count, the connectors or the form factor do not line up, an adapted or custom board closes the gap. In many cases a complete rugged computer that already combines these is the shorter route.

Sealing the enclosure also changes how the module is cooled, and our guide to Jetson fans, heat sinks and conduction-cooled heat spreaders sets out the options. Vehicle power brings its own rules; our explainer on ignition control covers how a carrier handles engine start and shutdown.

We work across the whole range. We supply off-the-shelf carriers, including Jetson Orin carrier boards and Jetson Thor carrier boards, adapt existing boards, and design custom carriers when the requirement calls for it. For Thor, the MILBOARD‑THR mil-grade carrier board for Jetson Thor is an open board for programmes building their own enclosure.

Whichever route, the board is only part of the job. We pair it with the module suited to the workload, build the rugged Jetson computer around it where needed, and configure the software image, so what you receive is a finished, validated system. If you are still choosing a module, our guide to the Jetson modules walks the options.