jetson-quick-start

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Quick Start — BSP customization entrypoint

快速启动 — BSP定制入口

jetson-quick-start

is a dispatcher and intake form. It does not download, extract, materialize sources, bind documents, or derive carrier files. It chooses the setup path, gathers core answers, then hands those answers to the skills that own the actual work.

jetson-quick-start

是一个调度器和信息收集表单。它不负责下载、解压、生成源文件、绑定文档或派生载体文件。它会选择设置路径，收集核心答案，然后将这些答案交给负责实际工作的Skill。

Modes

模式

Do not ask setup mode in a separate prompt. Include it as the first field in the core quick-start questionnaire, with choices shown in this fixed order:

```
Auto Setup
```
```
Guided Setup
```
```
Use Existing Workspace
```

Offer

cancel

separately as an exit action, not as a setup mode.

Mode	Use when	Planned skills
`Auto Setup`	Fresh workspace, network available	target setup, `/jetson-download-bsp` , `/jetson-init-image` , `/jetson-init-source` , `/jetson-link-docs` , `/jetson-generate-kb` , optional `/jetson-derive-carrier`
`Guided Setup`	User already has paths, repos, or archives	target setup, `/jetson-init-image` , `/jetson-init-source` , `/jetson-link-docs` , `/jetson-generate-kb` , optional `/jetson-derive-carrier`
`Use Existing Workspace`	BSP image, source tree, and docs are already prepared	target setup, workspace verification, `/jetson-generate-kb` , optional `/jetson-derive-carrier` ; route to init skills only for missing prerequisites

Target setup means keep the active profile, switch via

/jetson-set-target

, or create one via

/jetson-init-target

不要在单独的提示中询问设置模式。将其作为核心快速启动问卷的第一个字段，按以下固定顺序展示选项：

```
Auto Setup
```
（自动设置）
```
Guided Setup
```
（引导式设置）
```
Use Existing Workspace
```
（使用现有工作区）

将

cancel

（取消）作为单独的退出操作提供，而非设置模式的选项。

模式	使用场景	规划调用的Skill
`Auto Setup`	全新工作区、网络可用	target setup（目标设置）、 `/jetson-download-bsp` 、 `/jetson-init-image` 、 `/jetson-init-source` 、 `/jetson-link-docs` 、 `/jetson-generate-kb` ，可选 `/jetson-derive-carrier`
`Guided Setup`	用户已有路径、仓库或归档文件	target setup、 `/jetson-init-image` 、 `/jetson-init-source` 、 `/jetson-link-docs` 、 `/jetson-generate-kb` ，可选 `/jetson-derive-carrier`
`Use Existing Workspace`	BSP镜像、源码树和文档已准备完成	target setup、工作区验证、 `/jetson-generate-kb` ，可选 `/jetson-derive-carrier` ；仅当缺少前置条件时才路由到初始化Skill

Target setup指保留当前活跃配置文件、通过

/jetson-set-target

切换配置，或通过

/jetson-init-target

创建新配置。

Procedure

流程

Print Disclaimer

打印免责声明

Before opening the core questionnaire or inspecting setup inputs, print this disclaimer block exactly once:

text

================================================================================
DISCLAIMER
These skills help automate Jetson BSP setup and customization, but they do not
replace NVIDIA official documentation or engineering review. Review generated
plans, commands, diffs, and commit messages before accepting them.

Flashing can erase device storage or leave a target temporarily unbootable.
Keep backups and verify the active target, BSP release, and hardware setup
before deploy steps.
================================================================================

在打开核心问卷或检查设置输入之前，必须准确打印一次以下免责声明块：

text

================================================================================
DISCLAIMER
These skills help automate Jetson BSP setup and customization, but they do not
replace NVIDIA official documentation or engineering review. Review generated
plans, commands, diffs, and commit messages before accepting them.

Flashing can erase device storage or leave a target temporarily unbootable.
Keep backups and verify the active target, BSP release, and hardware setup
before deploy steps.
================================================================================

Disclaimer Acceptance Gate

免责声明确认环节

Immediately after printing the disclaimer, open a separate one-question

AskUserQuestions

disclaimer form and wait for the user's submitted answer before doing anything else. Do not collect disclaimer acceptance with a plain-text chat reply, inferred default, prior run state, active profile, cached answer, or any other non-UI signal.

The form must contain exactly one question:

```
accept_disclaimer
```
— prompt: "Accept the disclaimer and continue quick-start?" Choices:
```
accept_disclaimer
```
and
```
cancel
```
.

Treat only a submitted

accept_disclaimer

choice as acceptance. The disclaimer form is separate from the core questionnaire and does not replace any of the four routing-critical core questions.

If the form cannot be opened, is unavailable, is cancelled, returns no submitted answer set, or returns any answer other than

accept_disclaimer

, stop immediately and report that quick-start cannot continue until the disclaimer is accepted through

AskUserQuestions

打印免责声明后，立即打开一个独立的单问题

AskUserQuestions

免责声明表单，等待用户提交答案后再进行其他操作。不得通过纯文本聊天回复、推断默认值、之前的运行状态、活跃配置文件、缓存答案或任何非UI信号来收集免责声明确认信息。

表单必须包含且仅包含一个问题：

```
accept_disclaimer
```
— 提示："Accept the disclaimer and continue quick-start?"（接受免责声明并继续快速启动？）选项：
```
accept_disclaimer
```
和
```
cancel
```
。

仅将提交的

accept_disclaimer

选项视为已确认。免责声明表单独立于核心问卷，不能替代四个路由关键核心问题中的任何一个。

如果无法打开表单、表单不可用、用户取消表单、未返回提交的答案集，或返回的答案不是

accept_disclaimer

，则立即停止操作，并提示用户必须通过

AskUserQuestions

接受免责声明才能继续快速启动。

Mandatory Questionnaire Gate

强制问卷环节

After the disclaimer has been accepted,

jetson-quick-start

MUST open the core

AskUserQuestions

questionnaire and wait for the user's submitted answers before doing any setup dispatch. If the questionnaire cannot be opened, is unavailable, is cancelled, or returns no submitted answer set, stop immediately and report that quick-start cannot continue without the questionnaire.

Do not continue by using existing active profiles, workspace state, tarball names, cached answers, release compatibility, or "obvious" defaults. Do not call downstream skills until this gate has a submitted

mode

answer and normalized

quick_start_prefill

用户确认免责声明后，

jetson-quick-start

必须打开核心

AskUserQuestions

问卷，等待用户提交答案后再进行任何设置调度。如果无法打开问卷、问卷不可用、用户取消问卷，或未返回提交的答案集，则立即停止操作，并提示用户必须完成问卷才能继续快速启动。

不得使用现有活跃配置文件、工作区状态、压缩包名称、缓存答案、版本兼容性或“明显的”默认值来继续流程。在获取提交的

mode

答案和标准化的

quick_start_prefill

之前，不得调用下游Skill。

Survey State

调查状态

Inspect

target-platform/active_target.yml

and existing

target-platform/*.yaml

profiles. If an active profile exists, show

reference_devkit.name

, optional

custom_carrier.name

, and active

flash_config

. Do not infer platform identity from tarballs, repo names, or document titles.

Read

../../references/bsp-platforms-catalogue.md

and parse every row in the product / chip / SKU / flash-config table. This catalogue is the source for the full

active_platform

questionnaire list. If the list is incomplete, update the catalogue; do not duplicate or patch the platform list inside quick-start. Do not read

jetson-init-target/SKILL.md

or run the init-target flow during quick-start preprocessing; downstream target creation remains owned by

jetson-init-target

Keep this survey lightweight so the core questionnaire appears quickly: read target profile pointers/summaries, perform cheap path existence checks when useful, and fetch only lightweight Jetson Linux release metadata from the official archive needed to populate

bsp_release

choices. Parse all current release sections, not only the section that appears to match the selected platform. Do not scan large BSP / source / document trees, inspect archives, generate KB content, or run setup tools before the user submits the core questionnaire. Prepare the possible plans for all three modes; choose the actual downstream plan only after the form is submitted.

检查

target-platform/active_target.yml

和现有

target-platform/*.yaml

配置文件。如果存在活跃配置文件，显示

reference_devkit.name

、可选的

custom_carrier.name

和当前的

flash_config

。不得从压缩包、仓库名称或文档标题推断平台标识。

读取

../../references/bsp-platforms-catalogue.md

并解析产品/芯片/SKU/flash-config表中的每一行。该目录是生成完整

active_platform

问卷列表的数据源。如果列表不完整，请更新目录；不要在快速启动中重复或修补平台列表。在快速启动预处理阶段，不得读取

jetson-init-target/SKILL.md

或运行init-target流程；下游目标创建仍由

jetson-init-target

负责。

保持调查轻量化，以便核心问卷快速显示：读取目标配置文件指针/摘要，在有用时执行简单的路径存在性检查，并仅从官方归档获取填充

bsp_release

选项所需的轻量级Jetson Linux版本元数据。解析所有当前版本部分，而不仅仅是看起来与所选平台匹配的部分。在用户提交核心问卷之前，不得扫描大型BSP/源/文档树、检查归档文件、生成KB内容或运行设置工具。为三种模式准备可能的计划；仅在表单提交后选择实际的下游计划。

Print Platform Reference List

打印平台参考列表

Before opening the

AskUserQuestions

UI, print the full platform list parsed from

bsp-platforms-catalogue.md

with stable numeric indexes for this run:

text

Available platforms:
T234 - Orin
  1. Jetson AGX Orin 64GB | CVM P3701-0005 | CVB P3737-0000 | jetson-agx-orin-devkit.conf
  ...
T264 - Thor
  N. Jetson AGX Thor T5000 | CVM P3834-0008 | CVB P4071-0000 | jetson-agx-thor-devkit.conf

Use these indexes only for the immediately following questionnaire. Do not auto-select an index, even when there is an active profile or a single obvious match.

在打开

AskUserQuestions

UI之前，打印从

bsp-platforms-catalogue.md

解析出的完整平台列表，并为本次运行分配稳定的数字索引：

text

Available platforms:
T234 - Orin
  1. Jetson AGX Orin 64GB | CVM P3701-0005 | CVB P3737-0000 | jetson-agx-orin-devkit.conf
  ...
T264 - Thor
  N. Jetson AGX Thor T5000 | CVM P3834-0008 | CVB P4071-0000 | jetson-agx-thor-devkit.conf

这些索引仅用于紧随其后的问卷。即使存在活跃配置文件或唯一明显匹配项，也不得自动选择索引。

Ask Core Questionnaire

发起核心问卷

Generate one click-to-select core questionnaire for the whole setup run using the

AskUserQuestions

UI. Do not collect quick-start answers with plain-text prompts, inline chat questions, inferred defaults, or manual summary confirmation.

This is a hard gate: do not skip it, do not use a one-profile shortcut, and do not auto-select

mode

active_platform

bsp_release

, or

custom_carrier

from

active_target.yml

, filenames, tarballs, repo names, release compatibility, workspace state, cached answers, or prior runs. An existing active profile may be shown as an option, but it is not selected until the user submits the

AskUserQuestions

form.

Because

AskUserQuestions

can ask at most four questions, the core form must contain only routing-critical fields:

mode

—

Auto Setup

Guided Setup

Use Existing Workspace

, or

cancel

```
active_platform
```
— use the printed full platform list; follow the active-platform question rules below.
```
bsp_release
```
— recent global concrete release candidate shortcuts generated from the official Jetson Linux archive for this run, sorted newest first by dotted numeric order, plus
```
skip
```
. Preserve each official release token exactly as listed; concrete tokens may have two or three numeric components, such as
```
38.2
```
,
```
38.2.1
```
,
```
38.4
```
, or
```
R36.4.4
```
. Do not normalize
```
38.2
```
to
```
38.2.0
```
, and do not infer a missing patch component. Do not hard-code or cache candidates. If metadata fetch is slow or fails, still show
```
skip
```
and a typed concrete release option. Do not platform-filter this list in quick-start; include at least the newest concrete row from each current major release line found in the archive. If parsing returns only one major release line, treat the release list as incomplete and fall back to
```
skip
```
plus typed input instead of showing a partial candidate list.

custom_carrier

— if the selected/active profile already has a custom carrier, offer

keep_existing_custom_carrier

no_custom_carrier

add_custom_carrier

, and

skip

; otherwise offer

no_custom_carrier

add_custom_carrier

, and

skip

The user submits this

AskUserQuestions

form once. Only after that submission may

mode

, active platform, BSP release, and custom-carrier intent decide which downstream skills run and which prefilled answers are consumed or ignored. If there is no submitted form result, stop; never continue with inferred answers.

add_custom_carrier

is only a routing intent; carrier name, ID, SKU, revision, and custom flash config remain downstream-owned.

Render the form using the shared

User input prompt style

and normalize submitted UI answers into

quick_start_prefill

. Follow the shared

quick_start_prefill

contract. Active-platform question rules:

Print the full indexed platform list before the questionnaire.
Explicit choices are only the first row from each chip-family group, labeled with full-list index and product name, for example
```
Index 1 — Jetson AGX Orin 64GB
```
.
For all other platforms, the user chooses
```
Type something
```
and enters the numeric index from the printed list.
```
Type something
```
must be the tool's built-in freeform row, not a custom explicit choice.
Prompt text: "Pick a platform shortcut, or choose Type something and enter the numeric index from the full platform list printed above. Type skip to skip platform selection and let downstream setup ask later."
Only platform shortcuts may be explicit choices. Do not add
```
skip
```
,
```
Other
```
, or custom manual-entry choices;
```
skip
```
must be typed through the built-in
```
Type something
```
path. Do not paraphrase
```
Type something
```
as
```
Other
```
in prompt text.
Do not resolve flash-config variants here; pass the selected catalogue row to
```
jetson-init-target
```
, which owns validation and flash-config selection.

Each non-

skip

answer must be explicit and directly consumable by the owning downstream skill; use

skip

for anything unknown. A BSP release answer must be a concrete version token with an optional leading

and two or three numeric components (for example

R38.4

38.2

38.2.1

, or

36.4.4

). Family placeholders such as

R38.x

or "pin a version later" are not acceptable; use

skip

instead. Preserve the user's/source token exactly when passing

quick_start_prefill.download.bsp_release

Image paths, source paths, document paths, carrier details, repository overrides, toolchain choices, and document bindings are non-core setup details. Leave them to the owning downstream skill. Downstream setup skills should use documented defaults without asking when safe, and ask only on conflicts, overwrites, incompatible releases, missing artifacts, or user-requested overrides.

For Auto Setup,

/jetson-download-bsp

owns listing supported BSP releases for the selected platform and warning on platform/BSP incompatibility. Quick-start may forward a requested global candidate or typed release, but it does not validate support or override compatibility decisions itself.

使用

AskUserQuestions

UI生成一个适用于整个设置流程的点选式核心问卷。不得通过纯文本提示、内联聊天问题、推断默认值或手动摘要确认来收集快速启动答案。

这是一个硬性要求：不得跳过此环节，不得使用单配置文件快捷方式，不得从

active_target.yml

、文件名、压缩包、仓库名称、版本兼容性、工作区状态、缓存答案或之前的运行记录中自动选择

mode

、

active_platform

、

bsp_release

或

custom_carrier

。现有活跃配置文件可作为选项展示，但必须等待用户提交

AskUserQuestions

表单后才会被选中。

由于

AskUserQuestions

最多可提出四个问题，核心表单必须仅包含路由关键字段：

mode

—

Auto Setup

、

Guided Setup

、

Use Existing Workspace

或

cancel

。

```
active_platform
```
— 使用打印的完整平台列表；遵循以下活跃平台问题规则。
```
bsp_release
```
— 从官方Jetson Linux归档生成的近期全局具体版本候选快捷方式，按点分数字顺序从新到旧排序，外加
```
skip
```
（跳过）。严格保留每个官方版本的原始标识；具体标识可能包含两到三个数字组件，例如
```
38.2
```
、
```
38.2.1
```
、
```
38.4
```
或
```
R36.4.4
```
。不得将
```
38.2
```
标准化为
```
38.2.0
```
，不得推断缺失的补丁组件。不得硬编码或缓存候选版本。如果元数据获取缓慢或失败，仍需显示
```
skip
```
和手动输入具体版本的选项。在快速启动中不得对该列表进行平台过滤；至少包含归档中每个当前主要版本系列的最新具体版本。如果解析仅返回一个主要版本系列，则认为版本列表不完整，退化为仅显示
```
skip
```
和手动输入选项，而非显示部分候选列表。
```
custom_carrier
```
— 如果所选/活跃配置文件已有自定义载体，提供
```
keep_existing_custom_carrier
```
（保留现有自定义载体）、
```
no_custom_carrier
```
（无自定义载体）、
```
add_custom_carrier
```
（添加自定义载体）和
```
skip
```
；否则提供
```
no_custom_carrier
```
、
```
add_custom_carrier
```
和
```
skip
```
。

用户提交一次

AskUserQuestions

表单。仅在提交后，

mode

、活跃平台、BSP版本和自定义载体意向才能决定运行哪些下游Skill以及使用或忽略哪些预填答案。如果没有提交的表单结果，则停止操作；绝不能使用推断的答案继续流程。

add_custom_carrier

仅为路由意向；载体名称、ID、SKU、版本和自定义flash配置仍由下游Skill负责。

使用共享的

User input prompt style

渲染表单，并将提交的UI答案标准化为

quick_start_prefill

。遵循共享的

quick_start_prefill

contract。

活跃平台问题规则：

在问卷前打印完整的索引平台列表。
仅将每个芯片系列组的第一行作为显式选项，标注完整列表索引和产品名称，例如
```
Index 1 — Jetson AGX Orin 64GB
```
。
对于所有其他平台，用户选择
```
Type something
```
（手动输入）并输入打印列表中的数字索引。
```
Type something
```
必须是工具内置的自由输入选项，而非自定义显式选项。
提示文本："Pick a platform shortcut, or choose Type something and enter the numeric index from the full platform list printed above. Type skip to skip platform selection and let downstream setup ask later."（选择平台快捷方式，或选择Type something并输入上方打印的完整平台列表中的数字索引。输入skip可跳过平台选择，由下游设置后续询问。）
仅平台快捷方式可作为显式选项。不得添加
```
skip
```
、
```
Other
```
（其他）或自定义手动输入选项；
```
skip
```
必须通过内置的
```
Type something
```
路径输入。不得在提示文本中将
```
Type something
```
改写为
```
Other
```
。
不得在此处解析flash-config变体；将所选目录行传递给
```
jetson-init-target
```
，由其负责验证和flash-config选择。

每个非

skip

答案必须明确且可直接被对应的下游Skill使用；对于未知内容使用

skip

。BSP版本答案必须是具体的版本标识，可选择性带有前缀

，包含两到三个数字组件（例如

R38.4

、

38.2

、

38.2.1

或

36.4.4

）。不接受

R38.x

等系列占位符或“稍后固定版本”；应使用

skip

替代。传递

quick_start_prefill.download.bsp_release

时，严格保留用户/源标识的原始格式。

镜像路径、源路径、文档路径、载体详情、仓库覆盖、工具链选择和文档绑定属于非核心设置细节。将这些留给对应的下游Skill处理。下游设置Skill应在安全情况下使用文档化的默认值，仅在冲突、覆盖、不兼容版本、缺失工件或用户请求覆盖时才询问。

对于Auto Setup模式，

/jetson-download-bsp

负责列出所选平台支持的BSP版本，并对平台/BSP不兼容情况发出警告。快速启动可转发用户请求的全局候选版本或手动输入的版本，但不负责验证支持情况或覆盖兼容性决策。

Build Prefill Bundle

构建预填包

Normalize only explicit non-

skip

answers and keep them in memory:

yaml

quick_start_prefill:
  mode: Auto Setup | Guided Setup | Use Existing Workspace
  target: { active_platform, custom_carrier }
  download: { bsp_release }

Omit any skipped field and omit owner subsets with no core answer. Validate only enough to avoid obvious misrouting, such as blank mode or a BSP placeholder. Downstream defaults are skill behavior, not prefill fields. Do not invent missing identity values and do not write profile blocks from quick-start.

仅标准化明确的非

skip

答案，并将其保存在内存中：

yaml

quick_start_prefill:
  mode: Auto Setup | Guided Setup | Use Existing Workspace
  target: { active_platform, custom_carrier }
  download: { bsp_release }

省略任何跳过的字段，以及没有核心答案的所有者子集。仅进行足够的验证以避免明显的路由错误，例如空白模式或BSP占位符。下游默认值属于Skill行为，而非预填字段。不得编造缺失的标识值，不得从快速启动写入配置文件块。

Invoke Downstream Skills

调用下游Skill

Build the downstream plan from

quick_start_prefill.mode

, target state, and prerequisite checks. Before invoking downstream skills, print a non-blocking execution plan summary with the selected mode, target platform intent, requested BSP release or downstream release-selection handoff, custom-carrier intent, planned downstream skills in order, and non-core details that downstream skills may still ask for. Do not ask to approve this summary; continue dispatching unless the user chose

cancel

in the core questionnaire. This does not bypass downstream blocking validation gates.

Pass each downstream skill its relevant

quick_start_prefill

subset plus the top-level

mode

. The downstream skill must use valid prefilled answers, ask again for missing, invalid, ambiguous, or incompatible required inputs, and own any mutation of its profile block:

reference_devkit:

custom_carrier:

bsp_image:

source:

, or

documents:

For

Use Existing Workspace

, verify:

<bsp_image.root_path or workspace/Image>/Linux_for_Tegra/

exists.

Linux_for_Tegra/rootfs/etc/nv_tegra_release

exists, proving

apply_binaries.sh

ran; otherwise route to

/jetson-init-image

<source.root_path or workspace/Source>/Linux_for_Tegra/

exists and is a git repo.

recorded
```
documents:
```
paths exist when present.

Finish with executed skills, skipped skills, remaining downstream questions, and whether the workspace is ready for

customize-*

根据

quick_start_prefill.mode

、目标状态和前置条件检查构建下游计划。在调用下游Skill之前，打印一个非阻塞的执行计划摘要，包含所选模式、目标平台意向、请求的BSP版本或下游版本选择移交、自定义载体意向、按顺序排列的计划调用下游Skill，以及下游Skill可能仍会询问的非核心细节。无需请求用户批准此摘要；除非用户在核心问卷中选择

cancel

，否则继续调度。这不会绕过下游的阻塞验证环节。

向每个下游Skill传递其相关的

quick_start_prefill

子集以及顶层

mode

。下游Skill必须使用有效的预填答案，对缺失、无效、模糊或不兼容的必填输入重新询问，并负责其配置文件块的任何修改：

reference_devkit:

、

custom_carrier:

、

bsp_image:

、

source:

或

documents:

。

对于

Use Existing Workspace

模式，验证：

<bsp_image.root_path or workspace/Image>/Linux_for_Tegra/

路径存在。

Linux_for_Tegra/rootfs/etc/nv_tegra_release

存在，证明已运行

apply_binaries.sh

；否则路由到

/jetson-init-image

。

<source.root_path or workspace/Source>/Linux_for_Tegra/

存在且为git仓库。

已记录的
```
documents:
```
路径（如果存在）均存在。

最后输出已执行的Skill、已跳过的Skill、剩余的下游问题，以及工作区是否已准备好进行

customize-*

操作。

Suggest I/O customization next steps

建议I/O定制后续步骤

After the dispatch summary, print a non-blocking "Next steps — I/O customization" list only when the active profile's
documents:
block has at least one carrier-board-related slot bound via
/jetson-link-docs
. The qualifying slots are:

```
documents.carrier_board_spec
```
```
documents.carrier_schematic
```
```
documents.ref_devkit_pinmux_xls
```
```
documents.custom_carrier_schematic
```
```
documents.custom_carrier_pinmux_xls
```

If none of those are bound, skip this step — the user has not yet provided the carrier-board files these skills depend on, and the right next step is

/jetson-link-docs

, not a customize-* skill. Say so in one line ("No carrier-board docs bound — run

/jetson-link-docs

to register the carrier schematic / pinmux xlsx before I/O customization") and stop.

When at least one qualifying slot is bound, print the list below. Adapting a board to its on-board peripherals typically starts with pinmux and UPHY, then branches per-controller:

/jetson-customize-pinmux

— per-pin SFIO / direction / pull state (consumes

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

/jetson-customize-uphy

— UPHY lane allocation via

ODMDATA

(consumes

documents.module_design_guide

and

documents.custom_carrier_schematic

documents.carrier_schematic

/jetson-customize-pcie

— per-controller PCIe wiring (consumes

documents.module_design_guide

documents.custom_carrier_schematic

documents.carrier_schematic

, and

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

/jetson-customize-usb

— USB2 / USB3 SS port enable / disable (consumes

documents.module_design_guide

documents.custom_carrier_schematic

documents.carrier_schematic

, and

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

/jetson-customize-mgbe

— Multi-Gigabit Ethernet PHY wiring (consumes

documents.module_design_guide

documents.custom_carrier_schematic

documents.carrier_schematic

, and

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

/jetson-customize-camera

— CSI / MIPI / GMSL sensor bring-up (consumes

documents.module_design_guide

and

documents.custom_carrier_schematic

documents.carrier_schematic

For each suggested skill, flag any required

documents.*

slot that is not yet bound as "run

/jetson-link-docs

first to bind <field>" rather than hiding the skill — the user may want to fix the binding and retry. Do not invoke the customize-* skills here; quick-start ends at the suggestion.

调度摘要完成后，仅当活跃配置文件的

documents:

块中至少有一个通过

/jetson-link-docs

绑定的载板相关插槽时，才打印非阻塞的“后续步骤 — I/O定制”列表。符合条件的插槽包括：

```
documents.carrier_board_spec
```
```
documents.carrier_schematic
```
```
documents.ref_devkit_pinmux_xls
```
```
documents.custom_carrier_schematic
```
```
documents.custom_carrier_pinmux_xls
```

如果没有绑定任何符合条件的插槽，则跳过此步骤 — 用户尚未提供这些Skill依赖的载板文件，正确的后续步骤是

/jetson-link-docs

而非customize-* Skill。用一行文字说明（"No carrier-board docs bound — run

/jetson-link-docs

to register the carrier schematic / pinmux xlsx before I/O customization"（未绑定载板文档 — 在进行I/O定制前运行

/jetson-link-docs

注册载板原理图/引脚复用表xlsx文件））并停止。

如果至少绑定了一个符合条件的插槽，则打印以下列表。将板适配到板载外设通常从引脚复用和UPHY开始，然后按控制器分支：

/jetson-customize-pinmux

— 逐引脚SFIO/方向/上拉状态配置（使用

documents.custom_carrier_pinmux_xls

或

documents.ref_devkit_pinmux_xls

）。

/jetson-customize-uphy

— 通过

ODMDATA

配置UPHY lane分配（使用

documents.module_design_guide

和

documents.custom_carrier_schematic

documents.carrier_schematic

）。

/jetson-customize-pcie

— 按控制器配置PCIe布线（使用

documents.module_design_guide

、

documents.custom_carrier_schematic

documents.carrier_schematic

和

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

）。

/jetson-customize-usb

— USB2/USB3 SS端口启用/禁用（使用

documents.module_design_guide

、

documents.custom_carrier_schematic

documents.carrier_schematic

和

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

）。

/jetson-customize-mgbe

— 多千兆以太网PHY布线配置（使用

documents.module_design_guide

、

documents.custom_carrier_schematic

documents.carrier_schematic

和

documents.custom_carrier_pinmux_xls

documents.ref_devkit_pinmux_xls

）。

/jetson-customize-camera

— CSI/MIPI/GMSL传感器启用（使用

documents.module_design_guide

和

documents.custom_carrier_schematic

documents.carrier_schematic

）。

对于每个建议的Skill，标记任何尚未绑定的必填

documents.*

插槽，提示“run

/jetson-link-docs

first to bind <field>”（先运行

/jetson-link-docs

绑定<字段>），而非隐藏该Skill — 用户可能希望修复绑定后重试。不得在此处调用customize-* Skill；快速启动在建议环节结束。

Purpose

目的

Single entrypoint that gathers the four routing-critical answers (

mode

active_platform

bsp_release

custom_carrier

) and dispatches the right downstream Setup skills. Not a one-stop installer — it never downloads, extracts, materializes, or binds anything on its own.

作为单一入口点，收集四个路由关键答案（

mode

、

active_platform

、

bsp_release

、

custom_carrier

）并调度合适的下游设置Skill。它不是一站式安装程序 — 本身从不执行下载、解压、生成或绑定任何内容。

Prerequisites

前置条件

```
bsp-platforms-catalogue.md
```
reachable (used to build the platform list).
Submitted
```
accept_disclaimer
```
answer from the disclaimer
```
AskUserQuestions
```
form.
```
AskUserQuestions
```
UI available — quick-start refuses to continue without submitted disclaimer and core questionnaire forms.
Network access only required for the Auto Setup branch (
```
/jetson-download-bsp
```
is the actual fetcher).

```
bsp-platforms-catalogue.md
```
可访问（用于构建平台列表）。
已从免责声明
```
AskUserQuestions
```
表单提交
```
accept_disclaimer
```
答案。
```
AskUserQuestions
```
UI可用 — 若未提交免责声明和核心问卷表单，快速启动将拒绝继续。
仅Auto Setup分支需要网络访问（
```
/jetson-download-bsp
```
是实际的下载工具）。

Limitations

限制

Asks at most four core questions; any non-core value (image paths, source paths, document paths, carrier IDs, toolchain) is left to the owning downstream skill.
Does not validate platform / BSP-release compatibility — that is
```
/jetson-download-bsp
```
's job.

Does not write to

target-platform/*.yaml

; profile mutation stays with

/jetson-init-target

/jetson-init-image

, etc.

最多提出四个核心问题；任何非核心值（镜像路径、源路径、文档路径、载体ID、工具链）均由对应的下游Skill处理。
不验证平台/BSP版本兼容性 — 这是
```
/jetson-download-bsp
```
的职责。

不写入

target-platform/*.yaml

；配置文件修改由

/jetson-init-target

、

/jetson-init-image

等Skill负责。

Troubleshooting

故障排除

"questionnaire cancelled" exit — the form must be submitted; rerun
```
/jetson-quick-start
```
and complete the four questions.
"disclaimer not accepted" exit — rerun
```
/jetson-quick-start
```
, read the disclaimer, and choose
```
accept_disclaimer
```
in the disclaimer form when ready to continue.
Active profile not auto-selected — by design; even with one matching profile, the user must pick it explicitly in the form.
Unknown
bsp_release
typed — pass it as-is;
```
/jetson-download-bsp
```
validates the release against the official archive.

"questionnaire cancelled"（问卷已取消）退出 — 必须提交表单；重新运行
```
/jetson-quick-start
```
并完成四个问题。
"disclaimer not accepted"（未接受免责声明）退出 — 重新运行
```
/jetson-quick-start
```
，阅读免责声明，准备好后在免责声明表单中选择
```
accept_disclaimer
```
。
活跃配置文件未自动选中 — 这是设计使然；即使只有一个匹配的配置文件，用户也必须在表单中明确选择。
手动输入了未知的
bsp_release
— 按原样传递；
```
/jetson-download-bsp
```
会根据官方归档验证该版本。

Gotchas

注意事项

Ask the core questionnaire once. Downstream skills ask for non-core values, blanks, invalid values, or ambiguous choices.
Keep
```
quick_start_prefill
```
in memory unless the user asks to save it.
Never construct NVIDIA artifact URLs here;
```
/jetson-download-bsp
```
follows links from the selected Jetson Linux archive release.
```
platform_template.yaml
```
has no User Guide / Release Notes slots. Store those files or URLs in the final summary or KB, not as invented profile fields.

核心问卷仅询问一次。下游Skill会询问非核心值、空白值、无效值或模糊选项。
除非用户要求保存，否则将
```
quick_start_prefill
```
保存在内存中。
不得在此处构造NVIDIA工件URL；
```
/jetson-download-bsp
```
会从所选Jetson Linux归档版本中获取链接。
```
platform_template.yaml
```
没有用户指南/发行说明插槽。将这些文件或URL存储在最终摘要或KB中，而非作为新增的配置文件字段。

References

参考资料

../../context/bsp-customization-workflow.md

../../references/bsp-platforms-catalogue.md

```
../../references/platform_template.yaml
```
```
../jetson-download-bsp/SKILL.md
```
Jetson Linux archive: https://developer.nvidia.com/embedded/jetson-linux-archive

../../context/bsp-customization-workflow.md

../../references/bsp-platforms-catalogue.md

```
../../references/platform_template.yaml
```
```
../jetson-download-bsp/SKILL.md
```
Jetson Linux archive: https://developer.nvidia.com/embedded/jetson-linux-archive