jetson-customize-uphy

Configure UPHY lane allocation on NVIDIA Jetson custom carriers using ODMDATA tokens.

46|7|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/NVIDIA-AI-IOT/jetson-bsp-skills --skill jetson-customize-uphy-nvidia-ai-iot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetson-customize-uphy
Source: https://github.com/NVIDIA-AI-IOT/jetson-bsp-skills/tree/main/skills/jetson-customize-uphy
Command: npx skills add https://github.com/NVIDIA-AI-IOT/jetson-bsp-skills --skill jetson-customize-uphy-nvidia-ai-iot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps configure UPHY lane allocation on NVIDIA Jetson custom carriers, allowing for the remapping of PCIe, MGBE, USB3, or UFS controllers.

Core Features & Use Cases

  • UPHY Lane Allocation: Select and configure UPHY lane allocation for custom carriers.
  • Controller Remapping: Remap PCIe, MGBE, USB3, or UFS controllers using ODMDATA tokens.
  • Use Case: When setting up a custom carrier board, this Skill can be used to allocate UPHY lanes for PCIe, MGBE, USB3, or UFS controllers, ensuring proper functionality.

Quick Start

Use the jetson-customize-uphy skill to configure UPHY lane allocation for your custom carrier board.

Frequently Asked Questions about jetson-customize-uphy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure UPHY lane allocation on a Jetson custom carrier board?

Configure UPHY lane allocation on a Jetson custom carrier by remapping PCIe, MGBE, USB3, or UFS controllers using ODMDATA tokens. This requires an active target-platform profile, a custom carrier, a source-tree git, and a forked carrier conf.

What is UPHY lane remapping used for on NVIDIA Jetson devices?

UPHY lane remapping is used to reallocate lanes for PCIe, MGBE, USB3, or UFS controllers on Jetson custom carriers. It ensures proper controller functionality and hardware interface availability during custom carrier board setup.

Do I need a forked carrier conf to remap PCIe or USB3 controllers on Jetson?

Yes, remapping PCIe, MGBE, USB3, or UFS controllers using ODMDATA tokens requires a forked carrier conf. You also need an active target-platform profile and source-tree git to apply the UPHY lane allocation changes.

How do I use ODMDATA tokens to remap UFS or MGBE controllers on Jetson?

Use ODMDATA tokens to remap UFS or MGBE controllers by applying them within your custom carrier configuration. This process modifies UPHY lane allocation on the Jetson platform to correctly route the desired hardware controllers.

What are the limitations of using ODMDATA tokens for Jetson UPHY controller remapping?

ODMDATA token remapping is limited to PCIe, MGBE, USB3, and UFS controllers on custom carriers. It strictly requires a source-tree git, an active target-platform profile, and a forked carrier conf to successfully allocate UPHY lanes.