Jetson Customize Usb
NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The jetson-customize-usb skill enables, disables, or modifies the role of USB2 and USB3 SuperSpeed (SS) ports on Jetson Thor and Orin platforms. It ensures that port configurations—including wiring, VBUS-EN, OC, CC GPIOs, and UPHY lane assignments—are correctly reflected in the kernel device tree. The skill enforces a strict three-place lockstep update pattern (lane status, port status, and host xHCI phys-list) to prevent host controller crashes and ensures that all modifications are rendered as a self-contained kernel-DT overlay within the BSP source repository.
What it does
- Enables or disables USB2 and USB3 SS ports via kernel-DT overlays.
- Configures port roles, VBUS-EN, OC, and CC GPIOs based on carrier schematics.
- Maintains a three-place lockstep update for lane, port, and host xHCI controller bindings.
- Resolves companion links between USB2 and USB3 SS ports to prevent driver errors.
- Validates configurations against carrier pinmaps and schematic documentation.
- Generates a commit-ready kernel-DT overlay for the BSP source repository.
When to use it
- When you need to enable or disable USB ports on a custom Jetson carrier board.
- When a USB receptacle fails to enumerate after flashing the device.
- When you need to configure USB roles or wiring for specific carrier hardware.
- After running jetson-customize-uphy to ensure USB3 SS port settings align with new lane allocations.
Advantages
- Prevents common host xHCI controller crashes through strict lockstep enforcement.
- Ensures hardware-software alignment by requiring carrier schematic and pinmap verification.
- Automates complex device tree fragment generation for USB port topology.
- Maintains system stability by preventing invalid port or lane configurations.
Usage examples
- “Enable the USB3 SS port 2 on my custom carrier board.”
- The agent will verify the carrier schematic, check the UPHY lane allocation, and generate a kernel-DT overlay that correctly enables the lane, port, and xHCI phys-list.
- “Disable the USB hub connected to the carrier.”
- The agent will identify the associated USB2 and USB3 SS ports, perform the companion cascade, and update the device tree to safely disable the entire hub topology.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/jetson-customize-usb/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-customize-usb.zip -d .agents/skills
Documentation by Jetson Team
Customize USB (per-port enable / disable / role)
Purpose
Enable, disable, or change the role of USB2 / USB3 SS ports on a
Jetson Thor (Tegra264) or Orin (Tegra234) custom carrier. Captures
per-port wiring (role, max speed, VBUS-EN / OC GPIOs, CC1/CC2 GPIOs
for Type-C, USB3 SS UPHY lane), resolves the SS to USB2 companion
graph from the in-tree DTB, then renders a self-contained kernel-DT
overlay that flips every port action in three places in lockstep
(lane status, port status, host xHCI phys + phy-names).
UPHY lane allocation belongs to jetson-customize-uphy. No ODMDATA
edit. Output is one commit to the composite custom overlay .dts in
the bsp_sources/ hardware repo.
Prerequisites
Active profile with
reference_devkit:+custom_carrier:blocks.<source.root_path>/Linux_for_Tegra/.gitexists (/jetson-init-source)./jetson-derive-carrierhas run — carrier flash-conf fork in the overlay tracker./jetson-customize-uphyhas run when any enabled USB3 SS port needs a non-stock UPHY lane allocation. Its JSON sidecar at<workspace>/target-platform/<profile-stem>.jetson-customize-uphy.jsonis consulted for SS lane allocation.Source-of-truth docs: Adaptation Guide §"Port the Universal Serial Bus", Module Design Guide §USB, SoC TRM (xusb block).
When
custom_carrier:is present, bothdocuments.custom_carrier_schematicANDdocuments.custom_carrier_pinmux_xlsare REQUIRED. Refuse the run if either is missing — per-port routing (VBUS-EN / OC / CC GPIOs, SS lane wiring, hub fan-out) on a custom carrier cannot be guessed. Reference-devkit-only profiles skip this check.dtc,fdtoverlayon PATH.
Overview
USB on Tegra spans three IP surfaces: the xusb_padctl block (USB2
OTG + USB3 SS PHYs), the tegra-xusb xHCI host controller, and an
optional tegra-xudc device controller attached to the single
OTG-capable USB2 port (usb2-0).
A per-port flip MUST touch three kernel-DT places in lockstep.
Anything less crashes the host xHCI probe and leaves lsusb empty
on every port (collateral damage to stock-okay ports):
| # | Place | Path | What it controls |
|---|---|---|---|
| 1 | Lane (PHY provider) | xusb_padctl/pads/usb<2|3>/lanes/usb<2|3>-N | SS / OTG PHY hardware-binding. status="disabled" then lane stops providing a PHY. |
| 2 | Port (controller-binding) | xusb_padctl/ports/usb<2|3>-N | Per-port mode (host/device/otg), companion link, VBUS / OC / CC pin refs. status="disabled" then port removed from user-facing topology. |
| 3 | Host xHCI phys-list | bus@0/usb@<addr>.phys + .phy-names | Array of phandles + names the xHCI driver iterates. A ref to a disabled PHY returns -ENODEV and aborts the whole host probe. |
NVIDIA's stock-disabled usb3-3 in the Thor base DTB is the canonical
pattern — all three places flipped in lockstep.
Two extra rules ride on top of the three-place pattern:
Rule A — lane + port pairing. Lane (place 1) and matching port (place 2) MUST flip together.
Rule B — companion cascade.
xusb_padctl/ports/usb3-N.nvidia,usb2-companionreferences a USB2 port phandle. Disabling that USB2 without cascading to its SS companion thentegra-xusb: failed to enable PHYs: -19.
Agentic, not table-driven — every port, controller, lane,
companion link, phandle, and __symbols__ lookup is resolved at
runtime from docs + DTB + carrier pinmap + schematic.
When to invoke
The user says "enable USB", "disable USB hub", "configure USB3 SS", "set USB role", "wire VBUS-EN", "tegra-xusb / xudc / dr_mode", or asks to bring up / take down a USB controller on a custom carrier.
A USB receptacle on the carrier doesn't enumerate after flash, OR collateral USB damage (
lsusbempty after a previous jetson-customize-usb attempt) needs to be fixed.jetson-customize-uphyre-allocated UPHY lanes affecting USB3 SS ports and per-port DT now needs to follow.
Procedure (summary)
The full step-by-step procedure lives in references/procedure.md.
Step 1 — resolve active target + open source-of-truth docs.
Step 2 — build the USB topology + companion graph from the in-tree DTB.
Step 3 —
AskUserQuestionfor port(s) to enable / disable; surface companion cascade + on-carrier hub fan-out explicitly.Step 4 — per-port verify (module + carrier + UPHY lane) and capture wiring (VBUS-EN / OC / CC GPIOs via
pin_verifier.py).Step 5 — render the kernel-DT overlay using the three-place pattern, append fragments (
usb:padctl,usb:xhci, optionalusb:xudc) to the composite custom overlay.dts, runfdtoverlay+ the three post-merge invariants, commit tobsp_sources/.Step 6 — write run-state JSON sidecar (shape in
references/run-state-sidecar.md), emit headline, then drive the downstream next-step chain via sequentialAskUserQuestionprompts perreferences/procedure.mdStep 6. Never substitute a printed "Next step: …" line for the prompts.
See references/gotchas.md for the load-bearing failure modes.
Limitations
Owns kernel-DT overlay only. ODMDATA does not expose a per-port USB
statusknob; do not edit it.Does NOT allocate UPHY lanes —
jetson-customize-uphyowns that. Refuse to commit an SS-enable until uphy run-state shows the lane allocated.Does NOT directly patch the pinmux DTSI — routes SFIO mismatches to
/jetson-customize-pinmux set-pin.Does NOT compile the
.dtboor registerOVERLAY_DTB_FILE+=—/jetson-build-sourceowns build + flash-conf registration.Tegra platform invariant: only
usb2-0is OTG-capable;xudcattaches there only. All other USB2 ports and all USB3 SS ports are host-only.
Troubleshooting
Empty
lsusbon every port, USB-eth at 192.168.55.1 still up: host xHCI bailed; three-place lockstep was broken. Inspect merged DTB; verify post-merge invariants inreferences/procedure.mdStep 5d.tegra-xusb: failed to enable PHYs: -19: companion cascade (Rule B) violated — a USB2 was disabled without its SS companion.no port foundorRequested PHY is disabled: Rule A violated — lane status and port status are mismatched.FDT_ERR_NOTFOUNDfromfdtoverlay: a fragment usedtarget = <&label>for a node whose label is not in__symbols__(typical for host xHCI /tegra-xudc). Switch totarget-path = "/bus@0/usb@<addr>".dtc warning
phys_property: cell 0 is not a phandle reference: benign; expected when using raw integer phandles in the host phys override.Port boots but VBUS never asserts:
vbus-supplyreferences a regulator parent node that does not exist. Ensure the fixed regulator node is present before referencing it.xHCI binds the wrong port at boot: host
physelement order was not preserved. Only elide disabled entries; never reorder kept ones.
References
references/procedure.md— full step-by-step procedure.references/gotchas.md— load-bearing failure modes.references/run-state-sidecar.md— run-state JSON shape.references/usb-architecture.md— Tegra USB IP architecture notes (xusb_padctl,tegra-xusb,xudc).references/usb-dt-bindings.md— USB DT binding cheatsheet (lane / port / phys-list shapes).../../scripts/pin_verifier.py— shared HSIO pin verifier.../../references/platform_template.yaml—documents:block consumed by Step 1.../../context/bsp-customization-workflow.md— overlay edit protocol.../../references/bsp-customization-kernel-dtb.md— composite overlay append protocol.../jetson-customize-uphy/SKILL.md— sibling skill that owns UPHY lane allocation.../jetson-customize-pinmux/SKILL.md— sibling skill for VBUS-EN / OC / CC SFIO fixes.../jetson-derive-carrier/SKILL.md— must run first.../jetson-init-source/SKILL.md— produces the overlay trackerbsp_sourcesrepo.
Files
- ATTRIBUTION.mdAdded by AutoGineer923 B
- BENCHMARK.md3.7 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md8.2 KiB
- evals/evals.json4.3 KiB
- references/README.md664 B
- references/gotchas.md2.1 KiB
- references/procedure.md15.0 KiB
- references/run-state-sidecar.md1.3 KiB
- references/usb-architecture.md3.5 KiB
- references/usb-dt-bindings.md1.8 KiB
- skill-card.md3.6 KiB
- skill.oms.sig5.9 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Names Claude Code tools, Needs Node.js
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Jetson Team
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/jetson-customize-usb · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Jetson Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-customize-usb.zip