NVIDIA Jetson Mini-ITX Carrier Board for Edge AI
A Mini-ITX carrier-board platform for integrating NVIDIA Jetson modules into production edge AI systems.
Freeze the Jetson module, power mode, camera topology, storage, JetPack/BSP, thermal solution, and I/O map for the production carrier.
- Jetson Carrier BoardCompute module selected separately or by project
- Mini-ITX170 × 170 mm carrier-board direction
- Camera IntegrationCSI topology and connector mapping by SKU
- JetPack / BSPSoftware release pinned to hardware configuration

Configuration Baseline
Jetson Module and Carrier-Board Compatibility
The carrier board does not define compute capability by itself. Confirm the supported Jetson module family, connector, input power, I/O mapping, camera lanes, storage, and software release for the production design.

Lock the Jetson Module, Carrier I/O, Power Mode, and JetPack Release Together
Send the Jetson module, camera count and lane needs, storage, networking, expansion, displays, power source, enclosure, thermal method, JetPack release, and quantity.

System Architecture
Design the Carrier Around the Module, Cameras, Storage, and Software
A production Jetson system depends on correct pin mapping, power sequencing, camera routing, recovery access, and software adaptation—not only the compute module.
Deployment Fit
Edge AI Systems Built Around a Production Jetson Carrier
Use a custom carrier when the application needs a defined camera topology, compact mechanics, production I/O, and controlled software deployment.
Machine Vision and Inspection
Connect synchronized cameras, storage, networking, lighting control, and machine I/O around the selected Jetson module.
Explore relevant systems →Robotics and Autonomous Equipment
Integrate cameras, sensors, CAN, GPIO, wireless, storage, and recovery access in a compact edge controller.
Explore relevant systems →Video Analytics and Smart Infrastructure
Process multiple streams locally and send events or metadata upstream after validating ingest, inference, storage, and thermal limits.
Explore relevant systems →Do not assume a developer-kit image, connector, or software configuration transfers directly to a production module and custom carrier. Module pinout, power, camera lanes, recovery, and device-tree settings must be verified.
Project Configuration
Jetson Module, Camera, BSP, and Carrier I/O Configuration
Release the carrier board only after the module, power mode, camera topology, storage, I/O, JetPack, BSP, thermal solution, and flashing process are validated together.
Select the supported Jetson module, input power, module power mode, sequencing, protection, and peripheral budget.
Define CSI lanes, connectors, clocks, I2C, synchronization, cable, sensor drivers, and production camera modules.
Map NVMe, Ethernet, USB, wireless, cellular, CAN, GPIO, displays, and custom expansion to available interfaces.
Pin software releases, device tree, drivers, flashing, secure boot, recovery, module SKU, carrier revision, and change notices.
Compare Jetson module and GPU-compute directions.
Explore NVIDIA platforms →PlatformAI-Ready PlatformsReview integrated and module-based edge AI architectures.
Explore AI-ready platforms →ValidationEngineering ValidationPlan camera, power, thermal, BSP, and recovery testing.
Review validation process →ReferenceReference PlatformsReview integration patterns for industrial edge AI systems.
View reference platforms →Selection Questions
NVIDIA Jetson Carrier-Board Integration Questions
Resolve the remaining product-specific decisions before the board, software image, and mechanical design are released.
Is the Jetson compute module included with the carrier board?
Module supply depends on the quoted configuration. Confirm the exact Jetson module SKU, memory capacity, production status, and whether it is supplied separately or installed.
Can one carrier board support every Jetson module?
No. Compatibility depends on the module family, connector, pinout, power requirements, mechanical envelope, firmware, and carrier design. Use the approved module list for the selected SKU.
Can the developer-kit software image be used unchanged?
Not always. A custom carrier may require a board-specific BSP, device tree, pinmux, drivers, flashing configuration, and recovery process matched to the chosen JetPack release.
How many CSI cameras can be connected?
Camera count depends on available CSI lanes, connector routing, lane grouping, clocks, I2C control, sensor drivers, synchronization, and the selected Jetson module.
What must be frozen before production release?
Freeze the module SKU, carrier revision, power design, camera pinout, storage, I/O, JetPack, BSP, device tree, drivers, flashing image, thermal solution, and validation report.



