jetson-set-target

Switch the active target platform profile in active_target.yml after validating profile existence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually editing the active target platform configuration pointer for Jetson BSP development is error-prone and time-consuming, especially when switching between different devkit or carrier board profiles for build, flash, or customization tasks.

Core Features & Use Cases

  • Safe Profile Switching: Updates the active target platform pointer only after validating that the selected profile YAML exists in the target-platform/ directory, preventing broken configuration references.
  • Preserves Existing Config: Maintains all header comments in the active_target.yml file, only modifying the active: line to avoid losing custom annotations.
  • Use Case: If you have pre-configured profiles for the Jetson AGX Orin 32GB devkit and a custom carrier for the Jetson AGX Thor, you can instantly switch between them without manually editing YAML files, and downstream skills like jetson-customize-clocks will automatically use the newly selected profile.

Quick Start

Use the jetson-set-target skill to switch the active target platform to the jetson-agx-orin-32gb profile.

Frequently Asked Questions about jetson-set-target

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

FAQPage Schema
How do I switch the active target platform for Jetson BSP development?

To switch the active target platform for Jetson BSP development, you can use a profile-switching tool that updates the active pointer in your target-platform YAML configuration file automatically, validating the profile exists before writing.

Why does manually editing the active target platform YAML cause configuration errors?

Manually editing the active target platform YAML causes configuration errors because it is easy to accidentally delete header comments or reference a non-existent profile, which breaks downstream Jetson BSP build and flash workflows.

Can I preserve YAML header comments when switching Jetson target profiles?

Yes, you can preserve YAML header comments when switching Jetson target profiles by using an automated profile switcher that modifies only the active line in the active_target.yml file while leaving existing custom annotations untouched.

What is the best way to manage multiple Jetson carrier board profiles for builds?

The best way to manage multiple Jetson carrier board profiles for builds is to maintain pre-authored profile YAMLs in a target-platform directory and use an automated switching mechanism to safely select the active configuration without manual file editing.

Does the Jetson target profile switcher validate profile existence before applying?

Yes, the Jetson target profile switcher validates that the selected profile YAML exists in the target-platform directory before updating the active_target.yml file, preventing broken configuration references during BSP development.

When do I need to update the active target platform profile in Jetson BSP workflows?

You need to update the active target platform profile in Jetson BSP workflows when switching between different devkit or carrier board targets for downstream build, flash, or customization tasks to ensure the correct hardware configuration is applied.