Jetson 36.4.4 jetson-io.py is missing gpio configs

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

The dev manual shows the gpio pins are exposed when running the script, however with 36.4.4 the gpio options are missing.

jetson-io
jetson-io754×464 80.8 KB

This is what is on our system, no options for gpio.

jetson-2
jetson-2673×758 53.8 KB

jetson3
jetson3691×507 28 KB

2

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

Based on the provided context, it appears that you are experiencing an issue with GPIO pins not being exposed on the Jetson Orin Nano module when running a specific script. The script is supposed to expose the GPIO pins, but instead, you are seeing a different output.

To troubleshoot this issue, let’s break down the information provided:

  1. The dev manual shows that the GPIO pins are exposed when running the script. This suggests that the script is designed to enable GPIO functionality on the Jetson Orin Nano module.
  2. However, when you run the script on your system, the GPIO options are missing. This indicates that the script is not functioning as expected.
  3. You provided the output of the jetsonio command, which shows that there are no options for GPIO. This further confirms that the GPIO functionality is not being enabled.

To resolve this issue, let’s compare the output of the jetsonio command on your system with the expected output:

  • On your system, the output of jetsonio is:
    • jetsonio 754464 808 KB
    • jetson2 673758 538 KB
    • jetson3 691507 28 KB
  • In contrast, the expected output should show GPIO options, similar to the output on the Jetson AGX Orin module:
    • gpio-356 (PB.00)

The difference in output suggests that the script is not correctly enabling GPIO functionality on the Jetson Orin Nano module.

To further investigate, let’s examine the pinmux configuration on the Jetson Orin Nano module:

  • The pinmux configuration for the Jetson Orin NX and Nano modules is different from the Jetson AGX Orin module.
  • The can0_din and can0_dout pinmux settings are the same on both modules, but the can1_din and can1_dout settings are only present on the Jetson AGX Orin module.

Given these differences, it’s possible that the script is not correctly configured for the Jetson Orin Nano module. To resolve the issue, you may need to modify the script to correctly enable GPIO functionality on the Jetson Orin Nano module.

Additionally, you can try verifying the pinmux configuration on your system using the pinmux command. This may help identify any discrepancies between the expected and actual pinmux settings.

In summary, the issue appears to be related to the script not correctly enabling GPIO functionality on the Jetson Orin Nano module. By comparing the output of the jetsonio command and examining the pinmux configuration, you may be able to identify the root cause of the issue and modify the script accordingly.

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

4

?? What is jetsonio

6

Hi foxsquirrel1,

Are you using the devkit or custom board for Orin Nano?

It seems the new feature we added for the upcoming Jetpack release.

I’ve checked it is not supported in current R36.4.4 release.
If you want to use the pin as GPIO, please use pinmux spreadsheet instead.

7

Hi Kevin,

It is the dev kit, we did use the spreadsheet on the previous board and that was just way too time consuming.

That was not documented very well so it was a time burner. Just need to respond to configuration changes in a much faster way, jetson-io.py would be that tool.

8

Okay, we know using the pinmux spreadsheet to configure the pin may take time so that we add that feature in Jetson-IO for user.
I’ve checked with internal that this feature will be included in next JP6 release.

9

Thank you @KevinFFF

11

Hi @KevinFFF,

Do you know when this next JP6 release will be out? Are we looking at the first half of 2026, as outlined here?: Jetson Roadmap | NVIDIA Developer. Is it possible to release just the Jetson IO tool independently of the whole jetpack release? It would be nice to have that added functionality sooner rather than later.

12

@KevinFFF This should not be marked solved! The feature is documented here: Configuring the Jetson Expansion Headers — NVIDIA Jetson Linux Developer Guide for use on JP6.2+ and it is not there. Please correct the official documentation. I wasted hours yesterday trying to modify the dtb using the pinmux spreadsheet. I would appreciate a link to how to use the pinumx spreadsheet, as I am struggling to implement the 3 .dtsi files that it creates.

13

Hi all,

As it has been mentioned in Jetpack 6.2.1 (L4T r36.4.4) document, please let me share the Debian package as following:
nvidia-l4t-jetson-io_36.4.4-20250923173102_arm64.deb (40.0 KB)

You can simply put it into your device and run the following command to install.

$ sudo dpkg -i nvidia-l4t-jetson-io_36.4.4-20250923173102_arm64.deb
14

Thank you @KevinFFF, greatly appreciated by us.