jetson-derive-carrier

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.