Pinmux and GPIO assignments

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi,

I have a question about what pointers needed to be updated to point to the files generated from the excel spreadsheet. After generating the pinmux and gpio dtsi files from the excel spreadsheet.
In the nvidia documentation it states:
Copy the pinmux.dtsi file to the <l4t_top>/bootloader/t186ref/BCT/ directory, and copy the gpio.dtsi file to the <l4t_top>/bootloader/ directory.

You do not need to copy the padvoltage.dtsi file.

After copying the files, ensure that you point these files to the new board.conf

When it says point these files to the board.conf file. I am using the config file:

jetson-agx-orin-devkit.conf

In that file there is a PINMUX_CONFIG=

There is also the file p3701.conf.common, which also contains:

PINMUX_CONFIG=

They point to different files.

What pointer should be changed for the pinmux and gpio files generated by the excel file?

Thanks,

Malcolm

2

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

To update the pointers to point to the files generated from the Excel spreadsheet, you need to modify the PINMUXCONFIG and GPIOCONFIG pointers in the configuration files.

Based on the NVIDIA documentation, you are using the jetsonagxorindevkit.conf file, which contains the PINMUXCONFIG pointer. Additionally, you have the p3701-0000.conf.common file, which also contains the PINMUXCONFIG pointer, but points to a different file.

To update the pointers, you should modify the PINMUXCONFIG pointer in the jetsonagxorindevkit.conf file to point to the pinmux file generated from the Excel spreadsheet. Similarly, you should update the GPIOCONFIG pointer to point to the gpio dtsi file generated from the Excel spreadsheet.

Here’s a step-by-step guide to update the pointers:

  1. Open the jetsonagxorindevkit.conf file in a text editor.
  2. Locate the PINMUXCONFIG pointer and update it to point to the pinmux file generated from the Excel spreadsheet. For example:

PINMUXCONFIG=/path/to/pinmux_file.dtsi

3. Locate the `GPIOCONFIG` pointer and update it to point to the gpio dtsi file generated from the Excel spreadsheet. For example:
   ```bash
GPIOCONFIG=/path/to/gpio_file.dtsi
  1. Save the changes to the jetsonagxorindevkit.conf file.

As for the p3701-0000.conf.common file, you can either update the PINMUXCONFIG pointer in this file to point to the same pinmux file generated from the Excel spreadsheet or remove this file altogether, as it seems to be a common configuration file that is not specific to your board.

However, if you decide to update the PINMUXCONFIG pointer in the p3701-0000.conf.common file, make sure to update it to point to the same pinmux file generated from the Excel spreadsheet. For example:

PINMUXCONFIG=/path/to/pinmux_file.dtsi
  1. Save the changes to the p3701-0000.conf.common file, if you decide to update it.

After updating the pointers, you should be able to use the pinmux and gpio files generated from the Excel spreadsheet in your Jetson AGX Orin development kit.

In summary, you should update the PINMUXCONFIG and GPIOCONFIG pointers in the jetsonagxorindevkit.conf file to point to the pinmux and gpio files generated from the Excel spreadsheet, respectively. You can either update the PINMUXCONFIG pointer in the p3701-0000.conf.common file to point to the same pinmux file or remove this file altogether.

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

4

Hi malcolm12,

Are you using the devkit or custom board for AGX Orin?
What’s the Jetpack version in use? JP5.x?

jetson-agx-orin-devkit.conf is the main board config you used.
p3701.conf.common will be included by jetson-agx-orin-devkit.conf.

Please note that subsequent definitions will overwrite previous ones.
You can verify the configuration or check the flash logs to ensure the correct pinmux config is applied.

5

Hi KevinFFF,

I am currently using a AGX Orin devkit.

When I look at the flash logs. I see tegra234-mb1-bct–pinmux-p3701-0000-a04.dtb.

The file that I have been updating is tegra234-mb1-bct–pinmux-p3701-0000.dtsi

I also don’t see where the gpio file generated by the excel spreadsheet is used/assigned.

I would like to understand how these "pointers " are assigned for the pinmux and gpio.

Thanks for you guidance.

Malcolm

6

Could you share the full flash log for further check?

gpio dtsi should be included by pinmux dtsi.

7

Hi KevinFFF,

Attached is the flash log.

Thanks,

Malcolm

flashdump.zip (47.6 KB)

8 
copying pinmux_config(/home/stl/Projects/NewJP622/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi)... done.

You can refer to the above line in the log you shared.
The actual pinmux device tree used in your case is tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.
Please confirm you have updated this dtsi correctly.

9

Hi KevinFFF,

No, but I will update tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.

Thanks

Malcolm

10

Okay, please let us know if your pinmux configuration is loaded correctly after updating the correct device tree file.(i.e. <Linux_for_Tegra>/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi), or you have further question on pinmux/gpio dtsi.

11

Is this still an issue to support? Any result can be shared?

12

All good. Thanks for your help.

Malcolm