I am new to Jetson orin nano . Here is my configuration . Ubuntu 22.04.5 LTS /5.15.148-tegra /R36 (release), REVISION: 4.7 . My jetson-io.py util is messed up. It doesn’t show the option to manually configure the pin. I am trying to access the GPIO pins. I tried to use the gpiod . I am not able set anything to HIGH.
*** Please note that this reply is generated by LLM automatically ***
It seems like you’re having trouble with accessing GPIO pins on your Jetson Orin Nano device. You’re using Ubuntu 22.04.5 LTS with the 515.48-tegra kernel and R36 release, revision 47.
Firstly, let’s address the issue with jetson-io utility. This utility is used to configure the pinmux and GPIO settings on Jetson devices. If you’re not seeing the option to manually configure the pin, it’s possible that the utility is not properly installed or configured.
To resolve this, you can try reinstalling the jetson-io utility by running the following command:
sudo apt-get install jetson-io
Once installed, you can try running the utility again to see if the issue persists.
Regarding the GPIO access issue, you’re trying to use the gpiod command to set a GPIO pin to HIGH. However, you’re not able to do so.
Here are a few things you can try to resolve this issue:
- Check the GPIO pin number: Make sure you’re using the correct GPIO pin number. You can check the pinout diagram for your Jetson Orin Nano device to ensure you’re using the correct pin.
- Check the GPIO pin direction: Use the
gpiodcommand to check the direction of the GPIO pin. If the pin is set as an input, you won’t be able to set it to HIGH. You can use the following command to check the direction:
gpiod get <gpio-pin-number>
Replace <gpio-pin-number> with the actual GPIO pin number you’re trying to access.
- Set the GPIO pin direction: If the GPIO pin is set as an input, you can use the
gpiodcommand to set it as an output. Use the following command:
gpiod set <gpio-pin-number> output
Replace <gpio-pin-number> with the actual GPIO pin number you’re trying to access.
- Set the GPIO pin value: Once the GPIO pin is set as an output, you can use the
gpiodcommand to set its value to HIGH. Use the following command:
gpiod set <gpio-pin-number> 1
Replace <gpio-pin-number> with the actual GPIO pin number you’re trying to access.
If you’re still having trouble accessing the GPIO pins, you can try using the sysfs interface to access the GPIO pins. This involves using the file system to access the GPIO pins.
Here’s an example of how you can use the sysfs interface to set a GPIO pin to HIGH:
echo 1 > /sys/class/gpio/gpio<gpio-pin-number>/value
Replace <gpio-pin-number> with the actual GPIO pin number you’re trying to access.
Note that you’ll need to have the necessary permissions to access the GPIO pins using the sysfs interface.
In comparison to other Jetson devices, the GPIO access on Jetson Orin Nano is similar to other devices in the Jetson family. However, the specific GPIO pin numbers and configurations may vary depending on the device.
If you’re still having trouble accessing the GPIO pins, I recommend checking the Jetson Orin Nano documentation and the NVIDIA forums for more information and troubleshooting tips.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
3.3V ( 1) .. ( 2) 5V |
| NA ( 3) .. ( 4) 5V |
| NA ( 5) .. ( 6) GND |
| GND ( 9) .. ( 10) NA |
| NA ( 13) .. ( 14) GND |
| 3.3V ( 17) .. ( 18) NA |
| NA ( 19) .. ( 20) GND |
| GND ( 25) .. ( 26) NA |
| NA ( 29) .. ( 30) GND |
| NA ( 33) .. ( 34) GND |
| GND ( 39) .. ( 40) NA |
| |
| |
| Jetson 40pin Header: |
| |
| Configure for compatible hardware |
| Back
I dont see the option for manually configuring the pin
Hi KURMATT,
Are you using the devkit or custom board for Orin Nano?
If you want to control the GPIO as output in R36.4 or previous R36.x release, you have to apply the following patch manually.
40hdr - SPI1 gpio padctl register bit[10] effect by gpiod tools in JP6 - #20 by KevinFFF
Or, you can simply update the R36.5 to verify.
1 Like
I am using dev kit. With no program running , I can measure 3.3 v between pins (1,6) and 5 v between (2,6). My guess is the board is still good. I will try to apply the patch KevinFFF mentioned. But need to figure out how to apply the same.
I was able to follow KevinFFF’s advise and get the options back. I am still working on the LED issue. The issue has been resolved.
I was getting a tristate=1 previously and after configuring the pins - it was set back to 0
sudo grep -A 5 “pq5” /sys/kernel/debug/pinctrl/2430000.pinmux/pinconf-groups