Orin nx use JD6.2.1，The gpioset command setting is invalid。

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

After referring to the patch and generating an Image to replace the Image in the boot folder, the gpioset command still does not work. 40hdr - SPI1 gpio padctl register bit[10] effect by gpiod tools in JP6 - #20 by KevinFFF
gpioset --mode=time --sec=50 0 105=1

root@baidu-desktop:/# gpioinfo | grep -i “PQ.05”
line 105: “PQ.05” unused output active-high
root@baidu-desktop:/home/baidu# gpioget gpiochip0 105
0

image
image1158×293 9.88 KB

May I ask how to solve this problem？

2

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

Based on the provided context, it appears that you are experiencing issues with the gpioset command not working on your Jetson Orin NX device, specifically with the SPI1 GPIO pad control register bit 10 being affected by gpiod tools.

To solve this problem, I would recommend the following steps:

  1. Verify the GPIO configuration: Ensure that the GPIO configuration is correct and matches the expected behavior. You can use the gpioinfo command to verify the GPIO settings.
  2. Check the kernel version: Make sure that you are running the latest kernel version. You can check the kernel version using the uname -r command.
  3. Update the device tree: If you are using a custom device tree, ensure that it is updated to reflect the changes made to the GPIO configuration.
  4. Rebuild the kernel: If you have made changes to the kernel configuration, rebuild the kernel to ensure that the changes are applied.
  5. Verify the GPIO pin numbering: Ensure that the GPIO pin numbering is correct. You can use the gpioinfo command to verify the GPIO pin numbering.
  6. Check for conflicts with other GPIO tools: Ensure that there are no conflicts with other GPIO tools, such as gpiod, that may be affecting the behavior of the gpioset command.
  7. Try using a different GPIO tool: If the gpioset command is not working, try using a different GPIO tool, such as gpioget or gpiod, to see if the issue is specific to the gpioset command.

In your case, the output of the gpioinfo command suggests that the PQ05 line is unused and configured as an output with active-high logic. However, the gpioset command is not working as expected.

To troubleshoot this issue, I would recommend trying the following:

  • Verify that the PQ05 line is not being used by any other GPIO tool or application.
  • Try using a different GPIO tool, such as gpioget or gpiod, to see if the issue is specific to the gpioset command.
  • Check the kernel logs to see if there are any error messages related to the GPIO configuration or the gpioset command.
  • Try rebuilding the kernel with the latest configuration to ensure that the changes are applied.

If none of these steps resolve the issue, please provide more information about your setup, including the kernel version, device tree configuration, and any custom changes made to the GPIO configuration.

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

5

Hi 1712127445,

Are you using the devkit or custom board for Orin NX?
What’s the Jetpack version in use?

Have you configured the pinmux for PQ.05 as following before use?
image
If so, please try running the following command to control it.

# gpioset --mode=wait `gpiofind "PQ.05"`=0
# gpioset --mode=wait `gpiofind "PQ.05"`=1

If you still hit the issue, please run the following command to check its pinmux register.

$ sudo busybox devmem 0x02430068
6

image

image
image932×278 29.9 KB

image
image808×157 13.9 KB

I burned Orin orin jetson-orin-nx-pinmux.dtsi and Orin orin jetson-orin-nx-gpio-default.dtsi into the file using the ‘./flash. sh - r - k A_MB1_BCT jetson-orin-nano-devkit external’ command, but pin PQ.05 still cannot control the output high level

7

Could you also try using the following command to flash QSPI only to apply the change?

$ sudo ./flash.sh -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal