jetson-build-source

Rebuilds changed Jetson BSP kernel artifacts and generates a trace-to-dirty manifest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually rebuilding kernel-side BSP artifacts (DTBs, OOT modules, kernel Image) after source changes under bsp_sources/ is error-prone and inefficient, as it requires manually following NVIDIA's full build recipe even when only a subset of artifacts are affected by recent changes.

Core Features & Use Cases

  • Dirty-repo aware build modes: Auto-detects modified source repositories to run only the required build mode (dt, oot, kernel, or full) instead of the full build chain, saving significant time on incremental changes.
  • Composite overlay registration: Automatically handles build, Makefile, and flash configuration registration for kernel device tree custom overlays, ensuring custom DT changes are correctly included in rebuilt artifacts.
  • Trace-to-dirty manifest generation: Produces a manifest listing only artifacts affected by source changes, which downstream promotion steps use to copy only relevant files to the BSP image, avoiding baseline divergence noise.
  • Use Case: A BSP engineer making a device tree change for a custom carrier board can run this skill to automatically rebuild only the affected DTBs, register the custom overlay, and generate the manifest for promotion, eliminating manual make command errors and missed registration steps.

Quick Start

Invoke the jetson-build-source skill with no argument after making source changes under bsp_sources/ to auto-detect the required build mode, rebuild affected kernel artifacts, and generate the manifest for downstream promotion steps.

Frequently Asked Questions about jetson-build-source

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

FAQPage Schema
How do I rebuild Jetson BSP kernel artifacts after modifying device tree source?

To rebuild Jetson BSP kernel artifacts after source edits, this skill auto-detects modified repositories under bsp_sources/ and runs only the required build mode (dt, oot, kernel, or full) to generate affected device tree blobs, modules, or images.

What is the best way to automate incremental kernel builds for Jetson Embedded Linux?

Automating incremental kernel builds for Jetson Embedded Linux is handled via a dirty-repo watermarking system that traces source modifications, running targeted build modes instead of the full chain to save time and generate a trace-to-dirty manifest.

Can I use this to register custom device tree overlays for a Jetson carrier board?

Yes, you can register custom device tree overlays for a Jetson carrier board. The skill automatically handles build, Makefile, and flash configuration registration to ensure custom DT changes are correctly included in rebuilt artifacts.

Does this skill validate the toolchain before building out-of-tree modules?

Yes, the skill validates the toolchain before building out-of-tree modules. It enforces build safety guardrails, including toolchain validation and composite overlay registration, to prevent errors during the BSP artifact generation process.

Why does rebuilding NVIDIA Jetson kernel images manually cause baseline divergence?

Rebuilding NVIDIA Jetson kernel images manually causes baseline divergence because all artifacts are typically copied. This skill generates a trace-to-dirty manifest listing only artifacts affected by source changes for downstream promotion, avoiding baseline divergence noise.