jetson-init-target — UI samples

This file only shows output YAML shapes. Do not put product lists or flash-config lists here; jetson-init-target and jetson-quick-start must build those directly from references/bsp-platforms-catalogue.md.

Confirm-step YAML shape

Two cases, distinguished by whether the user added custom-carrier details in the optional step.

Reference devkit only:

reference_devkit:
  name: <product name from catalogue>
  module:
    id: <pXXXX from CVM-SKU>
    sku: "<SKU digits>"
  carrier:
    id: <pXXXX from CVB-SKU>
    sku: "<SKU digits>"
  flash_config: <chosen-conf>.conf

Reference devkit + custom carrier:

reference_devkit:
  name: <baseline product name>
  module:
    id: <pXXXX from baseline CVM-SKU>
    sku: "<SKU digits>"
  carrier:
    id: <pXXXX from baseline CVB-SKU>
    sku: "<SKU digits>"
  flash_config: <baseline-conf>.conf

custom_carrier:
  name: <custom product name>
  id: <custom board ID or project ID>
  sku: "<custom SKU or variant identifier>"
  flash_config: <custom-name>.conf

The bsp_image: block is appended later by jetson-init-image; the source: block by jetson-init-source (only if the user overrides <workspace>/Source); the documents: block by jetson-link-docs. None is written by jetson-init-target.

Third-party checks

No alerts3mo3 checks · Risk SAFE

Gen Agent Trust Hub3mo
The skill facilitates the creation of Jetson target-platform profiles by guiding the user through selecting reference hardware and optionally adding custom carrier details. It operates on local YAML configuration files and follows a structured template. No malicious activities, data exfiltration, or safety bypasses were detected.
Socket3mo
No alerts
Snyk3mo
Risk: LOW · No issues

/jetson-init-target

referencesui-samples.md