NVIDIA Jetson Orin - JetPack 7.2 - Obtaining Sources
🚧 Documentation is under development
The NVIDIA Jetson Orin guide is currently under active development. Some sections may be incomplete or change without notice.
Questions? Contact RidgeRun or email to support@ridgerun.com.
- Introduction
- JetPack 7.2
- JetPack 6.1
- JetPack 5.0.2
-
Development in the Board
-
Getting into the Board
-
- Emulation
- Supported Cameras
- GStreamer Pipelines
- RidgeRun Products
- RidgeRun Reference Designs
- Reference Documentation
- Contact Us
Obtaining the kernel and BSP sources is the first step for compiling Jetson Linux in JetPack 7.2.
This section explains the prerequisites you must meet and the two supported ways to download the sources: synchronizing with Git through the source_sync.sh script, or manually downloading and extracting the official archives from NVIDIA.
Prerequisites
Before obtaining the kernel and BSP sources, ensure your host environment meets the following requirements:
- The build will be performed on a Linux host computer using cross-compilation.
- The Jetson Linux 39.2 BSP is extracted on your host system, providing the
Linux_for_Tegra/directory. - The following dependencies are installed:
- git
- build-essential
- bc
- flex
- bison
- libssl-dev
- zstd
On Debian-based systems you can install them with:
sudo apt install git build-essential bc flex bison libssl-dev zstd
Internet access is required to download the sources. For Git synchronization, allow the outbound connections required by Git, including port 9418.
Obtaining the Sources
There are two supported ways to obtain the Jetson Linux kernel sources:
- Syncing the sources using Git with the
source_sync.shscript. - Manually downloading and extracting the sources from the NVIDIA Jetson Linux Archive.
Both approaches generate the same outcome: a full kernel source tree, NVIDIA out-of-tree modules, and device tree definitions that align with the JetPack 7.2 release.
Syncing the Sources
NVIDIA recommends using the source_sync.sh script, which is located in the Linux_for_Tegra/source/ directory. This script downloads the kernel, out-of-tree modules, and device tree sources for the exact JetPack release you are targeting.
1. Export the location of your Jetson Linux BSP. Replace the example path with the actual location of your Linux_for_Tegra/ directory:
export DEVDIR="/absolute/path/to/Linux_for_Tegra"
2. Run the script with the appropriate options:
cd "$DEVDIR/source" ./source_sync.sh -k -t jetson_39.2_GA
Where:
-kfetches all kernel-related sources (kernel, nvgpu, out-of-tree drivers, device tree files, etc.).-t jetson_39.2_GAspecifies the tag that corresponds to JetPack 7.2 (L4T r39.2).
After the script finishes, the folder $DEVDIR/source/ will contain the complete source tree, ready for the build steps.
Manually Downloading the Sources
If you cannot use source_sync.sh (for example, in a restricted network environment), you can download and extract the sources manually.
1. Export the location of your Jetson Linux BSP. Replace the example path with the actual location of your Linux_for_Tegra/ directory:
export DEVDIR="/absolute/path/to/Linux_for_Tegra"
2. Copy the public_sources.tbz2 archive
Download public_sources.tbz2 from NVIDIA's Jetson Linux 39.2 release downloads (Driver Package (BSP) Sources) for JetPack 7.2.
Then copy it into your Jetson Linux BSP directory:
cd "$DEVDIR" cp ~/Downloads/public_sources.tbz2 .
3. Extract the kernel, out-of-tree modules, and display driver sources:
tar xf public_sources.tbz2 -C "$DEVDIR/.." cd "$DEVDIR/source" tar xf kernel_src.tbz2 tar xf kernel_oot_modules_src.tbz2 tar xf nvidia_kernel_display_driver_source.tbz2 tar xf nvidia_unified_gpu_display_driver_source.tbz2
This extracts the kernel source to the kernel/ subdirectory, and the NVIDIA out-of-tree kernel modules sources to the current directory.
After this step, your $DEVDIR/source/ directory will contain the full kernel source tree, out-of-tree modules, and display driver code, ready for the build steps.
Once the sources are obtained, continue with the next section: Building the Kernel, OoT Modules and DTBs.