Build JetPack Yocto images for NVIDIA Jetson platforms
Introduction
Understand Yocto image builds for NVIDIA Jetson
Provision a Google Axion C4A VM for Arm Yocto builds
Build a Yocto image for NVIDIA Jetson on a Google Axion VM
Flash the Yocto image onto the NVIDIA Jetson device
Run the Yocto image on the NVIDIA Jetson device
Next Steps
Build JetPack Yocto images for NVIDIA Jetson platforms
Who is this for?
This is an advanced topic for embedded Linux developers familiar with Yocto and NVIDIA JetPack. You’ll build and flash custom images for NVIDIA Jetson Orin NX, Orin Nano, and Thor platforms.
What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Explain how Yocto uses OpenEmbedded, BitBake, and layers to create custom Linux distributions
- Provision a Google Axion C4A virtual machine for Yocto image builds
- Build a custom Yocto image for a supported NVIDIA Jetson platform
- Flash and run the Yocto image on the NVIDIA Jetson platform
Prerequisites
Before starting, you'll need the following prerequisites:
- Basic proficiency with Linux shell commands, SSH, and file transfers
- A Google Cloud account with permission and quota to create a
c4a-standard-32virtual machine - A supported NVIDIA Jetson platform
- A computer running Ubuntu 22.04 or later with USB access for flashing the image
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll use a Google Cloud C4A virtual machine powered by Google Axion to build a custom Yocto-based NVIDIA JetPack image. You’ll configure the build with OpenEmbedded, BitBake, and target layers, then create a bundled flashing archive. Then, you’ll transfer the archive to a local Ubuntu host and flash it to a supported NVIDIA Jetson platform. After the device boots, you’ll explore the Matchbox desktop and verify the NVIDIA GPU drivers and Docker runtime.