NVIDIA Jetson Orin - JetPack 6.1 - Customization Workflow

From RidgeRun Developer Wiki



Follow Us On Twitter LinkedIn Email Share this page


Previous: JetPack_6.1/Getting_Started/Components Index Next: JetPack_6.1/Customization_Workflow/Obtaining_Sources






The Customization Workflow section introduces the steps required to adapt and rebuild the Linux for Tegra (L4T) software stack on NVIDIA Jetson Orin devices. JetPack provides a complete software environment ready to use, but many development scenarios require adjustments beyond the default configuration. Developers often need to recompile the kernel, add support for new peripherals, apply custom patches, or modify device tree settings in order to achieve project-specific goals. This section outlines the main areas that remain customizable in JetPack 6.1 and explains how the process is structured.

The first step in the workflow is Obtaining Sources. At a high level, this process provides access to the kernel, driver modules, and device tree definitions that match the JetPack release installed on the board. Obtaining the correct sources is critical, since mismatched versions can result in build errors or runtime instability. This subsection explains how to synchronize your development environment with NVIDIA’s official release so that any modifications you introduce are applied on top of a consistent baseline.

The second step is Building the Kernel, OoT Modules and DTBs. In this stage, developers configure and compile the kernel with their required options, rebuild out-of-tree modules provided by NVIDIA, and generate device tree blobs (DTBs). These outputs represent the core customizable elements of the Jetson BSP. Together they allow fine-grained control over hardware support and system performance, which is essential when integrating additional devices or optimizing system behavior.

It is important to note that not all parts of the BSP are available in source form. Components such as the boot firmware and cboot remain distributed as binaries and cannot be rebuilt. The customization workflow therefore focuses exclusively on the kernel and device tree layers, which provide the flexibility needed for most development use cases.

By following the subsections in order, the customization workflow establishes a reproducible path from source acquisition to build outputs. It provides a clear starting point for developers who need to test, validate, and deploy changes, while ensuring alignment with NVIDIA’s official JetPack 6.1 release.



Previous: JetPack_6.1/Getting_Started/Components Index Next: JetPack_6.1/Customization_Workflow/Obtaining_Sources