My issue is that I am trying to set both these pins as outputs, SODIUM pin 124 which maps to in GPIO02 signal in spreadsheet and then GPIO03_PP.06 in customer usage column and then SODIMM pin 127 which maps gpio04 signal name and to GPIO3_PCC01 in customer usage column. However, Once I go into the Orin and try to toggle these pins they are stuck at 0v which we confirmed physically on an oscilloscope. Is there anything special we are missing to toggle these pins? Other pins such as GPIO9, GPIO1 and GPIO14 we have been able to toggle just fine.
Hi aespinoza1,
Are you using the devkit or custom board for Orin NX?
What’s the Jetpack version in use?
The current pinmux configuration for GPIO02/GPIO04 looks good to me.
Do you run the following commands to toggle them?
# gpioset --mode=wait `gpiofind "PP.06"`=1
# gpioset --mode=wait `gpiofind "PP.06"`=0
# gpioset --mode=wait `gpiofind "PCC.01"`=1
# gpioset --mode=wait `gpiofind "PCC.01"`=0
We are using a custom board for the Orin NX.
Jetpack 6.2.1
l4t 36.4.4
We were using this command are these equivalents? We were able to toggle other pins on the board such as SODIMM pin 230 and 118 using this command
sudo gpioset --mode=signal gpiochip0 98=1
sudo gpioset --mode=signal gpiochip0 98=0
Yeah, you’re good to go as long as you’ve verified the GPIO controller and pin number via gpioinfo.
gpiofind is basically just a double-check to make sure you got the right pin.
We have verified that we are toggling the right pin but still no physical output. What is the next trouble shooting steps from here?
Please apply the patch from the following thread since you are using JP6.2.1(r36.4.4) which does not include this fix.
40hdr - SPI1 gpio padctl register bit[10] effect by gpiod tools in JP6 - #20 by KevinFFF
The pins we are trying to toggle aren’t in the 40 pin header would this still fix the issue?
That patch covers all GPIOs in the pinctrl-tegra driver, not just the 40-pin header.