I’m trying to blink an LED using the GPIO on the 40-pin header (Pin 7) of the Jetson Orin NX Dev Kit, but the LED doesn’t respond at all — even though gpioinfo reports the line as unused and active-high.
I now have a multimeter connected to pin 6(GND) and pin 7(GPIO) on the 40 header pin section.
I ran:
gpioset gpiochip0 144=1
sleep 1
gpioset gpiochip0 144=0
and no voltage change happens, Ive looked at other forum post on this topic and nothing that is being suggested has changed the result of my problem.
*** Please note that this reply is generated by LLM automatically ***
I’d be happy to help you troubleshoot the issue with blinking an LED using the GPIO on the 40-pin header of the Jetson Orin NX Dev Kit.
First, let’s break down the information you’ve provided:
You’re trying to blink an LED connected to Pin 7 (GPIO) of the 40-pin header.
You’ve checked the GPIO status using gpioinfo and it reports the line as unused and active-high.
You’ve tried setting the GPIO pin high and low using gpioset commands, but there’s no voltage change on the pin.
Based on the context, here are a few potential issues that might be causing the problem:
GPIO pin configuration: Make sure that the GPIO pin is properly configured as an output. You can check the GPIO configuration using gpioinfo and verify that the pin is set as an output. If it’s not, you can try setting it as an output using gpioconfig.
GPIO pin numbering: Double-check that you’re using the correct GPIO pin number. The Jetson Orin NX Dev Kit uses a different GPIO pin numbering scheme than some other boards. You can refer to the Jetson Orin NX Dev Kit documentation or the NVIDIA Jetson GPIO documentation to ensure you’re using the correct pin number.
GPIO pin voltage: Verify that the GPIO pin is capable of producing the required voltage to drive the LED. The Jetson Orin NX Dev Kit GPIO pins are 3.3V, so if your LED requires a higher voltage, you may need to use a level shifter or a different GPIO pin.
LED connection: Ensure that the LED is properly connected to the GPIO pin and a ground pin (Pin 6, GND). Check that the LED is not damaged and that the connections are secure.
Software configuration: Make sure that the GPIO pin is not being used by another process or driver. You can try using gpioinfo to check if the pin is being used by another process.
To further troubleshoot the issue, you can try the following:
Use a multimeter to measure the voltage on the GPIO pin when you set it high and low using gpioset. This will help you determine if the issue is with the GPIO pin or the LED connection.
Try using a different GPIO pin to rule out any issues with the specific pin you’re using.
Check the Jetson Orin NX Dev Kit documentation and the NVIDIA Jetson GPIO documentation for any specific requirements or restrictions on using GPIO pins.
In comparison to other forum posts on this topic, it’s possible that the issue is specific to the Jetson Orin NX Dev Kit or the GPIO pin you’re using. However, by following the troubleshooting steps above, you should be able to identify and resolve the issue.
If you’re still having trouble, feel free to provide more information or clarification on the issue, and I’ll do my best to help you resolve it.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
When running `$ gpioset --mode=wait gpiochip0 144=1’, no change happens.
Anything else I can try, I have been trying to follow this video also:
And I am running into an issue when I run ‘dtc -O dtb -o pin7_as_gpio.dts’, in the video it creates a new line, while for me it does nothing, it seems to be loading the command for a very long time, after a while nothing happens and I have to Ctrl+C to get a new line.
It tells me pin 211 is the GPIO09 that goes out to header pin 7, and Im following that document due to the response in this forum.
So when I try gpioinfo, line 211 isnt there so I do gpioinfo gpiochip0 | grep PAC.06 and find it connected to line 144 and use that but still no change to the voltage on the pin.
according to TRM,
PADCTL_G7_SOC_GPIO59_0, Offset: 0x30
G7 PAD Control Registers are collectively called PADCTL_A24 in the System Address Map, which is.. 0x02448000
here’s bit-10 for GPIO_SF_SEL, it looks this bit has toggled as 1; whereas, 0 = GPIO, 1 = SFIO
for example,
$ sudo busybox devmem 0x02448030
0x00000408
please try it another try with changing pinmux configuration.
for instance,
step-1) Generate device tree files and name them as pinmux.dtsi and gpio.dtsi (remember to modify the #include in pinmux.dtsi for gpio.dtsi)
step-2) Put pinmux/gpio device trees to correct path
pinmux.dtsi in <Linux_for_Tegra>/bootloader/generic/BCT/
gpio.dtsi & padvoltage in <Linux_for_Tegra>/bootloader/
step-3) Modify the following line in <Linux_for_Tegra>/p3701.conf.common - PINMUX_CONFIG="tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi"; + PINMUX_CONFIG="pinmux.dtsi";
step-4) Flash the board to apply the change
there’s bit-10 for GPIO_SF_SEL, (1 = SFIO) Jetson-IO does not have capability to change it.
so far, please have pinmux configuration update to change this pin as GPIO output.
When flashing the board, it would just take me back to square one, where pin 7 is marked as unused. I tried doing everything you asked above on changing the pinmux configuration but the steps you asked me to do were not in my file explorer and was not able to locate them.
If you cold help guide me a bit more on the pinmux configuration steps that would help me a lot.
