jetson-init-source

Initialize Jetson BSP source workspace with overlay tracker, source tree, and Crosstool-NG toolchain.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Setting up a Jetson BSP source workspace for customization requires correctly initializing the Linux_for_Tegra overlay tracker, populating the bsp_sources source tree, and configuring the exact NVIDIA Crosstool-NG cross-compile toolchain, a multi-step process that is error-prone when done manually and can block all downstream kernel, device tree, and out-of-tree module development work.

Core Features & Use Cases

  • Overlay Tracker Initialization: Creates a clean, empty Linux_for_Tegra git repository to track pristine and customization commits, or mounts a user-provided custom tracker repo.
  • Flexible BSP Sources Materialization: Supports three precedence-ordered methods to populate the bsp_sources directory: local public_sources.tbz2 archive extraction (offline default), source_sync.sh fallback, or customer git repo clone, with validation to prevent incorrect source tree states.
  • Automated Toolchain Configuration: Auto-discovers existing Crosstool-NG installs, extracts pre-downloaded x-tools.tbz2 archives, or prompts for a valid toolchain prefix, then writes the resolved path to the active target profile for downstream build skills.
  • Use Case: Embedded Linux engineers working with NVIDIA Jetson platforms use this skill immediately after running jetson-init-image to prepare a reproducible, version-pinned source workspace for BSP customization tasks.

Quick Start

Run the jetson-init-source skill after completing the jetson-init-image workflow to automatically set up your Jetson BSP source workspace with the correct overlay tracker, source tree, and cross-compile toolchain.

Frequently Asked Questions about jetson-init-source

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

FAQPage Schema
How do I set up a Jetson BSP source workspace for kernel and device tree customization?

To set up a Jetson BSP source workspace, you need to initialize the Linux_for_Tegra overlay tracker, populate the bsp_sources tree, and configure the NVIDIA Crosstool-NG toolchain. This skill automates that entire initialization process to ensure a reproducible workspace.

Can I populate the bsp_sources directory offline using a local public_sources.tbz2 archive?

Yes, you can populate the bsp_sources directory offline by extracting a local public_sources.tbz2 archive. This is the default method, with source_sync.sh and customer git repo clone available as fallback options.

How does automated Crosstool-NG toolchain configuration work for Jetson cross-compilation?

Automated Crosstool-NG toolchain configuration auto-discovers existing installs, extracts pre-downloaded x-tools.tbz2 archives, or prompts for a toolchain prefix, then writes the resolved path to the active target profile for downstream builds.

Do I need to run jetson-init-image before using this source setup skill?

Yes, you should run jetson-init-image before this skill. It is designed to run immediately after image extraction to prepare a reproducible, version-pinned source workspace for BSP customization tasks.

What is the best way to track pristine and customization commits in a Linux_for_Tegra overlay?

The best way to track commits in a Linux_for_Tegra overlay is by initializing a clean git repository tracker, or by mounting a user-provided custom tracker repo to manage pristine and customization commits.

Why does my Jetson BSP source setup fail during source tree materialization?

Jetson BSP source setup fails during materialization due to incorrect source tree states. The skill validates the bsp_sources directory after population to prevent downstream build and customization failures.