jetson-customize-pinmux

Generate pinmux, GPIO, and padvoltage DTSI files from a pinmux XLSM spreadsheet for Jetson Orin and Thor carrier boards.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-customize-pinmux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetson-customize-pinmux
Source: https://github.com/JORDAN0615/bsp_factory/tree/main/skills/jetson-customize-pinmux
Command: npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-customize-pinmux

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Configuring pinmux settings for Jetson Orin and Thor custom carrier boards traditionally requires manually editing device tree include files or using Excel macros, which is error-prone and difficult to reproduce across carrier designs. This skill automates the generation of the three required BCT DTSI files directly from the authoritative pinmux XLSM spreadsheet.

Core Features & Use Cases

  • XLSM-Driven Generation: Parses the Tegra pinmux spreadsheet to produce pinmux, GPIO default-state, and padvoltage DTSI files.
  • Per-Pin Interactive Configuration: Guides users through Q1 to Q6 questions for each pin's SFIO, direction, initial state, pull, drive type, and open-drain settings.
  • Carrier Integration: Emits DTSIs into the overlay tracker with correct carrier-key naming so they are picked up at flash time via the carrier configuration.

Quick Start

Use the jetson-customize-pinmux skill to configure pin settings for your custom Jetson carrier board by providing the pinmux XLSM spreadsheet and answering the per-pin configuration prompts.

Frequently Asked Questions about jetson-customize-pinmux

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

FAQPage Schema
How do I generate pinmux DTSI files for a custom Jetson carrier board from an XLSM spreadsheet?

Generate pinmux DTSI files from an XLSM spreadsheet by parsing the Tegra pinmux configuration to automatically produce flash-ready pinmux, GPIO default-state, and padvoltage device tree include files for custom Jetson carrier boards.

Can I configure per-pin SFIO functions and electrical attributes for Jetson Orin without manually editing device tree files?

Configure per-pin SFIO functions, directions, initial states, pull, drive type, and open-drain settings interactively, eliminating manual device tree editing by generating the required BCT DTSI files directly from the authoritative pinmux XLSM spreadsheet.

What do I need to set up before generating device tree include files for Jetson Thor custom carrier boards?

Generating device tree include files for Jetson Thor requires an active target profile with a custom carrier, a parsed pinmux XLSM, and the Jetson derive-carrier and init-source prerequisites to emit BCT DTSIs into the Linux_for_Tegra overlay tracker.

How does the generated pinmux DTSI integrate with the Jetson flash process?

The generated pinmux DTSI integrates with the Jetson flash process by emitting device tree include files into the overlay tracker with correct carrier-key naming, ensuring they are automatically picked up at flash time via the carrier configuration.

What's the best way to avoid errors when configuring padvoltage and GPIO default states across multiple Jetson carrier designs?

Avoid errors across multiple Jetson carrier designs by automating the generation of padvoltage and GPIO default-state DTSI files from the XLSM spreadsheet, replacing error-prone manual device tree editing and Excel macros with a reproducible process.

Does this pinmux generation approach work with both Jetson Orin and Thor platforms?

This pinmux generation approach works with both Jetson Orin and Thor custom carrier boards, parsing the pinmux XLSM spreadsheet to emit the three required BCT DTSI files into the Linux_for_Tegra overlay tracker for either platform.