skills.rest
JORDAN0615
JORDAN0615COMMUNITY
Explore all skills by this author →
GitHub

jetson-derive-carrier

Derive per-board filesets and DT overlays for custom NVIDIA Jetson carriers.

1|Updated Jun 12, 2026
Search Tags:#bootloader#bsp#embedded linux#jetson#custom carrier#device tree overlay#board bring-up
One-click install
npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-derive-carrier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jetson-derive-carrier
Source: https://github.com/JORDAN0615/bsp_factory/tree/main/skills/jetson-derive-carrier
Command: npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-derive-carrier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually deriving and configuring all per-board files for a custom NVIDIA Jetson carrier board from a reference devkit is time-consuming, error-prone, and easy to get wrong due to the large number of board-specific configuration files, naming conventions, and BSP workflow rules.

Core Features & Use Cases

  • Automated File Forking & Renaming: Automatically copies and renames carrier-specific board files (flash configs, BCTs, nvpmodel/nvfancontrol configs) from a reference devkit to match the custom carrier's ID and SKU, following NVIDIA's strict naming and content rules.
  • DT Overlay Scaffolding: Creates a device tree overlay for carrier-specific hardware deltas, so the kernel base DTB remains tied to the reference devkit and can be easily updated when the reference BSP changes.
  • Validated Workflow with Safety Gates: Runs all edits through commit preview gates, re-verifies every file edit to catch silent failures, and follows NVIDIA's BSP customization commit batching rules to keep changes organized and reviewable.
  • Use Case: If you are bringing up a new custom Jetson carrier board, use this skill to automatically derive all required board-specific files and overlays from an existing reference devkit, eliminating manual copy-paste errors and ensuring compliance with NVIDIA BSP standards.

Quick Start

Use the jetson-derive-carrier skill to derive all required custom carrier board files and DT overlays from your configured reference Jetson devkit.

Frequently Asked Questions about jetson-derive-carrier

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

FAQPage Schema
How do I derive custom Jetson carrier board files from a reference devkit?▼

Deriving custom Jetson carrier board files from a reference devkit requires forking and renaming flash configs, BCTs, and nvpmodel files. This process automates that file generation to match your custom carrier's ID and SKU while adhering to NVIDIA BSP customization standards.

What is the best way to create a device tree overlay for Jetson carrier board bring-up?▼

Creating a device tree overlay for Jetson carrier board bring-up isolates carrier-specific hardware deltas from the kernel base DTB. This scaffolding approach keeps the base DTB tied to the reference devkit, allowing easy updates when the reference BSP changes.

Can I automate boot and power configuration updates for a custom Jetson carrier?▼

Automating boot and power configuration updates for a custom Jetson carrier is supported by editing targeted flash configurations. It re-verifies every file edit to catch silent failures and runs all changes through commit preview gates for reviewable BSP workflows.

Does deriving NVIDIA BSP files for custom carrier boards require manual copy-pasting?▼

Deriving NVIDIA BSP files for custom carrier boards does not require manual copy-pasting. The workflow eliminates manual effort by automating file forking and renaming according to strict board-specific naming and content rules to prevent configuration errors.

Why should I use device tree overlays instead of modifying the base DTB for embedded Linux board bring-up?▼

Using device tree overlays instead of modifying the base DTB for embedded Linux board bring-up maintains separation between carrier hardware deltas and reference devkit defaults. This ensures reproducible carrier derivation and prevents breaking base functionality during BSP updates.

What are the limitations of automated Jetson carrier board file derivation?▼

Automated Jetson carrier board file derivation relies on having a configured reference Jetson devkit as the baseline. It scaffolds files and DT overlays but requires you to manually define the specific hardware deltas and validate the final board bring-up behavior.

Related Skills

Explore More Software Engineering Skills→
NVIDIA-AI-IOTNVIDIA-AI-IOT
46

jetson-customize-clocks

Customize Jetson clock settings by editing BPMP DTB and nvpower.sh files.

Official
Advanced
JORDAN0615JORDAN0615

jetson-customize-camera

Generate validated kernel device-tree overlays for MIPI/GMSL camera sensors on custom Jetson carrier boards.

Community
Advanced
mikegogulskimikegogulski

embedded-systems

Develops firmware for STM32 and ESP32 microcontrollers using RTOS and bare-metal programming.

Community
Advanced
NVIDIA-AI-IOTNVIDIA-AI-IOT
46

jetson-derive-carrier

Fork reference files and create a Device Tree overlay for custom carrier boards.

Official
Intermediate