Pinmux configuration for Jetson orin nano

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi, I rereferred Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation developer guide for pinmux changes.

generated

pinmux.dtsi

  • gpio.dtsi

  • padvoltage.dtsi

the for the instruction,

Copy the padvoltage.dtsi and pinmux.dtsi files to the <l4t_top>/bootloader/generic/BCT/ directory and copy the gpio.dtsi file to the <l4t_top>/bootloader/ directory.

  • however with what file I need to replace these files if I want to retain the original files and replace it?

  • a. Copy pinmux.dtsi and padvoltage.dtsi to /Linux_for_Tegra/bootloader/generic/BCT/
    b. Copy gpio.dtsi to Linux_for_Tegra/bootloader/

    Then,
    Pinmux file:
    #PINMUX_CONFIG=“tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi”;
    Comment above line and add below line or replace with below line
    PINMUX_CONFIG=“pinmux.dtsi”;
    Pmc config:
    #PMC_CONFIG=“tegra234-mb1-bct-padvoltage-p3767-dp-a03.dtsi”;
    Comment above line and add below line or replace with below line
    PMC_CONFIG=“padvoltage.dtsi”;

Which are the equivalent files for these pinmux.dtsi gpio.dtsi padvoltage.dtsi for orin nano devkit with L4T 36.4.4 ? especially for gpio.dtsi

2

gpio.dtsi is included as part of the pinmux dtsi file. You could read your pinmux dtsi file and you will notice that.

3

*** Please note that this reply is generated by LLM automatically ***

To answer your question, I’ll provide a detailed explanation of the pinmux changes for the Jetson Orin Nano Devkit with L4T 36.4.4.

Pinmux changes for Jetson Orin NX and Nano Series

The NVIDIA Jetson Linux Developer Guide provides documentation on pinmux changes for the Jetson Orin NX and Nano Series. To make pinmux changes, you need to generate the pinmux.dtsi, gpio.dtsi, and padvoltage.dtsi files.

Equivalent files for Jetson Orin Nano Devkit with L4T 36.4.4

For the Jetson Orin Nano Devkit with L4T 36.4.4, the equivalent files are:

  • pinmux.dtsi: tegra234-mb1-bct-pinmux-p3767-0000-a04.dtsi
  • gpio.dtsi: tegra234-mb1-bct-gpio-p3767-0000-a04.dtsi
  • padvoltage.dtsi: tegra234-mb1-bct-padvoltage-p3767-0000-a04.dtsi

Replacing the original files

To retain the original files and replace them with the new ones, you need to copy the generated pinmux.dtsi, gpio.dtsi, and padvoltage.dtsi files to the following directories:

  • Copy pinmux.dtsi and padvoltage.dtsi to Linux_for_Tegra/bootloader/generic/BCT/
  • Copy gpio.dtsi to Linux_for_Tegra/bootloader/

Then, update the PINMUX_CONFIG and PMC_CONFIG lines in the tegra234-mb1-bct-pinmux-p3767-0000-a04.dtsi file to point to the new pinmux.dtsi and padvoltage.dtsi files, respectively.

Example

Comment out the original lines and add the new lines:

- PINMUX_CONFIG = tegra234-mb1-bct-pinmux-p3767-0000-a04.dtsi;
+ PINMUX_CONFIG = pinmux.dtsi;

- PMC_CONFIG = tegra234-mb1-bct-padvoltage-p3767-0000-a04.dtsi;
+ PMC_CONFIG = padvoltage.dtsi;

Note that you should replace the pinmux.dtsi and padvoltage.dtsi files with the actual file names generated by the pinmux tool.

I hope this helps! Let me know if you have any further questions.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

6

I am sorry, can you specify or give an example? So no need to worry about gpio.dtsi. If I include and make related changes for those 2 files, should be enough right?

7

These modifications look good to me to apply the change for pinmux.
You can simply check the full flash log to confirm if they’ve been use correctly.

May I know what’s the current issue here?

8

Hi, there is no issues now. However, while generating the dts files from the spreadsheet, it generates 3 files. If I give custom names to these 3 files, I am checking what I need to change for gpio.dtsi. I got the replacement for other 2 files in case I change the file names.

9

gpio.dtsi will be included by pinmux.dtsi. Please just check your pinmux dtsi has included it correctly.