jetson-init-source

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.