domains / families / devops / jetson-derive-carrier

jetson-derive-carrier

separate

Bootstrap a custom carrier board by forking carrier files and scaffolding a DT overlay from the reference devkit. Use after jetson-init-source; not for module-level or kernel-DTB changes.

When to use

• Customize the per-board fileset for a new carrier board so downstream `customize-*` skills, `nvpower.sh`, and the boot chain land on the custom carrier instead of the reference devkit. Base DTB stays at the reference; carrier deltas live i…

When not to use

• Kernel base DTB and its source DTS are **not** forked — carrier
• BPMP DTB fork is opt-in (default OFF). Most carrier swaps share the
• Flash-conf content substitution is **targeted**, not blanket. Vars
• Custom-carrier IDs need not follow NVIDIA `pNNNN` style; the
• Does not customize module-level files. Use the relevant

Skill page

Source