Welcome to Jetson Orin NANO Developer Kit repository
03.Jetson BSP custom agent skills
Jetson BSP Customization Agent Skills Tutorial
1. Function Description
jetson-bsp-skills is a set of Jetson Linux BSP customization workflow Skills provided by NVIDIA. It targets host-side development before flashing the Jetson, and is not a device skill for daily diagnostics on a booted Jetson.
This repository does not contain BSP images, source code archives or specific carrier board materials. Instead, it provides workflow guidance, templates and reference materials to help developers prepare a BSP workspace, modify the BSP, build the related artifacts, and flash and verify after confirmation.
Official repository:
https://github.com/NVIDIA-AI-IOT/jetson-bsp-skills2. Applicable Scenarios
When low-level customization of the Jetson platform is required, these Skills can be considered, for example:
Modifying Pinmux and GPIO pin multiplexing
Customizing USB, PCIe, UPHY, MGBE
Adding or modifying the device tree of a CSI camera
Adjusting clocks, DVFS, fan policies and nvpmodel
Adjusting the BSP reserved memory
Modifying the kernel, device tree or driver and rebuilding
Integrating the customization into the BSP image, then flashing and verifying
If you only install applications, deploy OpenClaw, run models or check the state of a booted system, BSP Skills are usually not required; device-side tools or jetson-device-skills can be used.
3. Working Location and Directory Relationships
BSP customization is performed in an independent workspace on a Linux host. The host can be a physical Ubuntu computer, or an Ubuntu virtual machine configured with sufficient disk space and resources.
Example directory:
xxxxxxxxxx~/jetson-bsp-workspace/├── .claude/ # BSP Skills, context and reference materials├── Linux_for_Tegra/ # Prepared BSP flashing directory, determined by the selected workflow└── source/ # Kernel, device tree and other source code initialized when neededClaude Code should be started from the BSP workspace, not from a directory of the running system on the Jetson. The Linux_for_Tegra here is the to-be-flashed BSP working directory on the host, not the root file system running on the Jetson.
4. Host Environment Preparation
Prepare the following before starting:
An Ubuntu Linux host or an Ubuntu virtual machine
An available network connection and sufficient disk space
BSP materials matching the target Jetson model, carrier board and JetPack/L4T version
Claude Code and an available Anthropic login/authorization
If actual flashing is planned: a matching power supply, a USB data cable and a Recovery USB device that can be passed through directly
A backup of important data and a recoverable original system plan
The virtual machine can be used for BSP preparation and source code work. Before actual flashing, you must also confirm that the virtual machine can recognize and stably pass through the Jetson Recovery USB; if the USB device cannot be passed through reliably, do not start flashing.
5. Obtain the BSP Skills Repository
Execute the following in the Ubuntu host terminal:
xxxxxxxxxxgit clone https://github.com/NVIDIA-AI-IOT/jetson-bsp-skills.gitcd jetson-bsp-skillsIf the repository already exists, enter it and check first instead of cloning it again:
xxxxxxxxxxcd ~/jetson-bsp-skillsgit statusgit remote -v6. Create the BSP Workspace and Install the Skills
Create an independent directory for this BSP work:
xxxxxxxxxxmkdir -p ~/jetson-bsp-workspaceRun the installation script provided by the repository to copy the Skills, context and reference materials into the workspace:
xxxxxxxxxxcd ~/jetson-bsp-skills./setup.sh --workspace ~/jetson-bsp-workspaceThe installation script creates the following in the workspace:
xxxxxxxxxx~/jetson-bsp-workspace/.claude/If this directory already exists, the script refuses to overwrite it by default. Confirm its content first; consider --force only when you clearly want to rebuild and have made a backup. Do not add --force directly just to eliminate an error, because the script deletes the existing .claude/ and recreates it.
Check the installation result:
xxxxxxxxxxfind ~/jetson-bsp-workspace/.claude -maxdepth 3 -type f | sort | head -807. Start Claude Code in the Workspace
xxxxxxxxxxcd ~/jetson-bsp-workspaceclaudeOn the first start, complete the login or authorization as prompted by Claude Code. Enter the official recommended entry request in Claude Code:
xxxxxxxxxxhelp me setup the bsp customization workspaceThis request leads to the /jetson-quick-start workflow. Follow the prompts to choose automatic preparation or guided preparation based on existing materials, and provide the real Jetson model, carrier board, BSP/JetPack version and customization goal.
Do not just tell the agent "help me DIY a BSP". First explain the exact model of the target board, the carrier board model, the current/target JetPack version, the storage medium and the specific hardware requirements.
8. BSP Workflow Stages
The repository divides the work into the following stages:
8.1 Preparation
Create or select the target configuration according to the device and BSP version, prepare the BSP input, unpack the image, initialize the source code/toolchain, and register local reference materials. Common entries include:
/jetson-quick-start
/jetson-init-target
/jetson-set-target
/jetson-download-bsp
/jetson-init-image
/jetson-init-source
/jetson-link-docs
/jetson-generate-kb
After preparation is complete, whether Linux_for_Tegra, the source directory and the knowledge base are generated in the workspace depends on the selected workflow and the provided BSP input; do not assume that starting Claude Code automatically generates a complete flashing image.
8.2 Customization
Invoke the corresponding /jetson-customize-* Skill according to the requirement, for example pinmux, USB, PCIe, UPHY, camera, clock, fan or power mode. When using a custom carrier board, first confirm whether /jetson-derive-carrier is required.
Before each modification, confirm:
The specific board model and hardware version corresponding to the modification
The paths of the original files and the target files
That the configuration/device tree matches the target BSP version
The change content and potential impact
Whether an original backup and a rollback method are available
8.3 Build and Integration
If the modification involves kernel-side source code, use /jetson-build-source to build the DTB, modules or kernel artifacts. Then use /jetson-promote-image to integrate the customized files and build artifacts into the to-be-flashed BSP image.
If the change only affects the rootfs or the configuration, the build step may be different; follow the workflow of the corresponding Skill and the current BSP version.
8.4 Flashing and Verification
Only after static checks, difference checks and target confirmation are completed should you consider:
/jetson-flash-image: Flash the prepared BSP to the Jetson
/jetson-validate-image: Post-flash static check and device-side verification
Flashing may erase the target storage, overwrite the QSPI/boot components, or make the device temporarily unable to boot. Before starting, you must clearly confirm the target Jetson, the target storage device, the Recovery state, the BSP version and the backup; you cannot infer that flashing will not affect other storage only from "an empty SSD". The flashing medium and whether QSPI is involved are determined by the target board model and the corresponding BSP flashing solution.
9. Suggestions for the First Experience
On the first use, do a workflow experience that does not write to the disk first:
Install the Skills in the Ubuntu workspace.
Start Claude Code and run help me setup the bsp customization workspace.
Provide accurate board model and version information.
Let the agent explain the Setup workflow it intends to choose and the inputs required.
Use /jetson-print-bsp-info to check the existing Linux_for_Tegra directory (if it has already been prepared).
View the customization plan and the file differences first, without performing flashing.
Only after becoming familiar with the workflow and preparing a recoverable environment should you evaluate building and deployment separately.
If you only want to experience the workflow, do not connect the Recovery device, do not run /jetson-flash-image, and do not let the agent execute commands that erase or overwrite storage.
10. Common Problems
10.1 setup.sh Reports That --workspace Is Required
The target workspace must be specified, for example:
xxxxxxxxxx./setup.sh --workspace ~/jetson-bsp-workspace10.2 It Reports .claude/ already exists
The script protects the existing directory by default and does not overwrite it. First check whether it already contains work content; only use --force to rebuild after confirming that it can be discarded and backed up.
10.3 Claude Code Cannot Find the Skills
Confirm that the current directory is the workspace specified during installation, and start Claude Code from that directory:
xxxxxxxxxxcd ~/jetson-bsp-workspaceclaudeCheck whether .claude/skills and the SKILL.md of each Skill exist in the workspace.
10.4 The Virtual Machine Cannot See the Recovery Device
First check the USB passthrough settings and the device connection state of the virtual machine. Plan the flashing only after confirming that the Recovery USB device is visible in Ubuntu. When the device does not appear stably in the virtual machine, do not run the flashing workflow.
11. Risk Notice
BSP Skills provide workflow guidance and cannot replace NVIDIA official documentation, board schematics and engineering review.
All generated plans, commands, file differences and submitted content require manual review.
Choosing the wrong board model, carrier board, BSP version or target disk may make the Jetson unable to boot or overwrite the wrong device.
Errors in the device tree, kernel, Pinmux and power configuration may cause peripheral failure, boot failure or abnormal hardware behavior.
Flashing and overwriting are high-risk operations; execute them only after confirming the target, the backup and the recovery path.
Verify the compatibility of the current Skill and BSP version first, and do not directly apply the flashing command from an old tutorial to other versions.