jetson-init-image

Extract Jetson BSP tarballs, apply the correct GPU stack flag, and record image metadata in the target profile.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-init-image
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetson-init-image
Source: https://github.com/JORDAN0615/bsp_factory/tree/main/skills/jetson-init-image
Command: npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-init-image

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually extracting Jetson BSP tarballs, configuring the correct GPU driver stack for target hardware, and tracking the resulting image path in the target profile is error-prone and time-consuming for Jetson developers, leading to failed builds and misconfigured environments.

Core Features & Use Cases

  • Automated Tarball Extraction: Extracts matching Jetson Linux and sample-rootfs tarballs to the correct workspace path, validating version consistency between the two files.
  • GPU Stack Configuration: Automatically selects the correct apply_binaries.sh flag (nvgpu for T234/Orin, OpenRM for T264+/Thor+) based on the active target profile's hardware definition.
  • Use Case: A developer working on an Orin-based Jetson device can use this skill to quickly set up their BSP image without manually verifying the correct GPU driver stack or tracking the image path in their target profile.

Quick Start

Use the jetson-init-image skill to extract your staged Jetson BSP tarballs, run apply_binaries with the correct GPU stack flag for your active target, and record the resulting image path and version in your target profile.

Frequently Asked Questions about jetson-init-image

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Jetson BSP image initialization and apply the correct GPU stack?

Automating Jetson BSP image initialization involves extracting matching Linux and rootfs tarballs, applying binaries with the correct GPU stack flag, and recording image metadata. This process eliminates manual configuration errors during BSP setup.

What is the correct GPU driver stack flag for Orin and Thor Jetson devices?

The correct GPU driver stack flag is nvgpu for T234 Orin devices and OpenRM for T264+ Thor devices. This selection is derived automatically based on the hardware definition in the active target profile.

How do I validate tarball version consistency when extracting Jetson Linux images?

Validating tarball version consistency during Jetson Linux image extraction is handled automatically by checking the matching Jetson Linux and sample-rootfs tarballs before extraction. This prevents build failures caused by mismatched files.

Can I use this BSP setup process for Jetson target hardware beyond Orin?

Yes, this BSP setup process applies to Jetson Linux development workflows for target hardware including Orin T234 and Thor T264+ devices. It automatically configures the appropriate GPU driver stack for each specific hardware profile.

Why does my Jetson apply_binaries.sh configuration fail during manual BSP setup?

Manual Jetson apply_binaries.sh configuration fails due to selecting the wrong GPU driver stack or tracking the incorrect image path. Automating tarball extraction and profile updates eliminates these manual configuration errors.