Controlling GPIO output pin via gpioset does not work in JP 6.x

[KevinFFF]

Hi ahans123,

Thanks for pointing out the GPIO control issue in JP6.

@ahans123

This page tells you to search for “Orin Series Pinmux” in the Jetson Download Center. However, doing so yields only one result, which is the AGX Orin one, not Nano! Searching for “nano series pinmux” gives the correct link. Note that a search just for “pin” gives a couple of pinmux results, but not the Orin Nano one. That explains why I had such a hard time finding that spreadsheet. Here is the complete link: https://developer.nvidia.com/downloads/jetson-orin-nx-and-orin-nano-series-pinmux-config-template

AGX Orin and Orin Nano/NX are from similar Orin platform(T234), but they are different modules and we have separate guide for them.
It is caused from that the adaptation guide you were referring is for AGX Orin( Jetson AGX Orin Platform Adaptation and Bring-Up — NVIDIA Jetson Linux Developer Guide 1 documentation)
If you are using Orin Nano, please refer to Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation.

@ahans123

Without this example, I would have had a very hard time finding out the address. “TRM” in point A is the Technical Reference Manual, which is then linked in point D. It’s the exact same document.

Yes, TRM is Technical Reference Manual and you can download it from Jetson Download Center.
For the PADCTL address, you can also refer to Calculating/Getting register adresses of gpio pins - #7 by jost38

@ahans123

So once I had the address, I was able to read the value using busybox devmem <address>. It was always giving me 0x0000005A. The documentation says that for an input, bits 4 and 6 are set, which they indeed are in 0x0000005A. Flipping those, I get 0x0000000A. Once I had written that value to the register, I was able to use the pin as output!

Let me take an example for PAC.06(SOC_GPIO59).
Once you find its pinmux address(0x02448030 = Base+offset = 0x02448000+0x30 ), you can run sudo busybox devmem 0x02448030 to get its value.
Bit 0:1 → Functions
Bit 2:3 → PULL
Bit 4 → TRISTATE
Bit 6 → ENABLE Input
Bit 10 → SFIO/GPIO
Above information should be included in TRM.

@ahans123

I agree with @bremen_matt and @tteuber in the aforementioned thread that changing the default behaviour without explicit note or a migration guide is not exactly customer friendly. On top of that we have @DaveYYY’s very inappropriate tone.

Sorry for the inconvenience and inappropriate response from us.
The most of pins are configured as GPIO Input by default, but you can configure them as Bi-directional in pinmux spreadsheet instead. We’ve also mentioned it in developer guide as following:

However, we have a known issue in both JP6.0(R36.3.0) and JP6.1(R36.4.0), which has been fixed in JP6.2(R36.4.3).

@ahans123

That spreadsheet only working with Excel on Windows really is the icing on the cake here!

About pinmux spreadsheet only works with Excel on Windows, it is caused that the macro features were designed there.
Actually, you can also modify the pinmux dtsi file directly if you are familiar with those attributes.
Normally, we would just suggest user using the pinmux spreasheet in case some attributes were not configured correctly.

Moreover, we’ve also discussed GPIO control issue in JP6 with internal.
We collected many feedbacks from forum.
The good news is that it seems Jetson-IO would support to configure pins on 40-pins header to use them as GPIO or specific functions in the next release.