jetson-init-target

What it does

Authors a new target-platform YAML profile (target-platform/<name>.yaml) for a Jetson platform, based on a reference devkit and optional custom carrier details, and updates the active_target pointer accordingly. It is used to create a target, not to switch existing profiles.

How it works

• Load a platform_template.yaml as the schema and fill placeholders according to a Quick-start prefill contract, consuming quick_start_prefill.target.active_platform and quick_start_prefill.target.custom_carrier when available.
• Read and bootstrap the target-platform directory if needed, creating target-platform/active_target.yml from active_target_template.yaml.
• Read the platform catalogue (bsp-platforms-catalogue.md) to pick a reference product, building a list with stable indexes and presenting shortcuts like 'Index N — <Product Name>'. Resolve a single catalogue row from user input.
• Choose the flash config: default is 1; if variants exist, present them as numbered options. Handle special cases like raw-conf variants and '(same as <other>)' placeholders.
• Optionally collect custom_carrier details via an interactive process (AskUserQuestions UI) with separate forms for custom_carrier.name/id/sku/revision and then custom_carrier.flash_config. Respect required vs optional fields and allow NA where appropriate.
• Build the final YAML shape depending on whether custom_carrier was added, then show a proposed filename derived from the catalogue product name or custom_carrier.name. Write target-platform/<filename>.yaml and update target-platform/active_target.yml to set active: <filename>.yaml if bootstrap or activation is approved.
• In bootstrap, auto-activate the new profile in the Write step and inform the user. In existing-profile cases, prompt for activation unless multiple profiles are being authored.

When to use it

• When the user asks to create / author / add a new target platform profile.
• When there are no existing target-profile YAMLs (bootstrap case) or when the user wants to add a new profile alongside existing ones.

What it can touch

• Writes: target-platform/<filename>.yaml
• Edits: target-platform/active_target.yml
• Reads: target-platform/active_target.yml, target-platform/*.yaml, ../../references/platform_template.yaml, ../../references/bsp-platforms-catalogue.md

Caveats

• The skill is explicit about using the catalogue for product names and the platform_template.yaml as the schema; it does not write until user input resolves a single catalogue row and flash config.
• Activation behavior depends on bootstrap vs existing profiles: bootstrap auto-activates; existing profiles may prompt for activation.
• Custom-carrier details are collected via AskUserQuestions and must be provided verbatim by the user; certain fields require non-empty values unless the user enters NA. The template omits custom_carrier.module and custom_carrier.chip_family.