Can't export gpio

[Robin_faith]

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
[*] other

Target Operating System
[*] Linux
QNX
other

Hardware Platform
[*] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.9.1.10844
[*] other

Host Machine Version
[*] native Ubuntu 18.04
other

hello
I want to control SOC_GPIO32(GPIO3_PS.07), echo 439 > export return is busy ,
cat /sys/kernel/debug/gpio didn’t find gpio439 be used.
pinmux pinmux.0x02431008 = 0x00000044; # soc_gpio32_ps7: rsvd0, pull-down, tristate-disable, input-enable, lpdr-disable。

Thanks for your support！

[Robin_faith]

[Robin_faith]

new usrer only could post one picture so i post here

[VickNV]

Could you please explain why you need to control SOC_GPIO32 (GPIO3_PS.07)? Additionally, could you provide the source of the image you shared? Specifically, which Excel file is it from? Also, please share your DRIVE OS version by running the following command:

$ cat /etc/nvidia/version-ubuntu-rootfs.txt

[Robin_faith]

1. we use this gpio communicate to TC397

3. DRIVE OS version
   5.2.0.0-23067027

[VickNV]

How did you determine that the pin is connected to the TC397? What documentation are you referring to?

Please note that Pinmux/GPIO configuration is only supported for PDK. This forum provides support for SDK only.

[Robin_faith]

It’s in our hardware manual。
I found that there are some similar GPIO problems in our forum but not same as my case ，I’m not sure it’s pinmux error or something else，Can you give me some idea of what to look for。
thanks ！

[VickNV]

Is the hardware manual from NVIDIA? If so, could you specify which manual you’re referring to? Were the GPIO problems you mentioned discussed in this forum? If yes, could you provide the links to those topics?

For issues related to pinmux or other hardware configurations within the PDK scope, it’s best to reach out to your NVIDIA representative to ensure you’re directed to the appropriate support channels.

[Robin_faith]

Hi Vick
This is a case I’ve seen with other developers：

Xavier industrial gpio device or resource busy

Our customized carrier board use 4 x gpio, two of which are occupied,but I did not use these GPIOs for other functions. [image] Calculate the GPIO number from the Pinmux table GPIO4- 290; GPIO5 -503;GPIO20 -291;GPIO21-288 gpiochip2: GPIOs 240-247, parent: platform/max77620-gpio, max77620-gpio, can sleep: gpio-246 ( |gpio_default ) out hi gpio-247 ( |gpio_default ) out hi gpiochip1: GPIOs 248-287, parent: platform/c2f0000.gpio, tegra-gp…

After using echo 56> /sys/class/gpio/export command to control GPIO, it prompts that the device is busy

We calculated the mapping address of GPIO3_PI.00 as 56 (group=0, bank=8, offset=0) according to the guidance in the forum But when I input echo 56> /sys/class/gpio/export, it prompts that the device is busy. What is the reason? How to solve it? Thank you

Are the pin definitions for SDK and PDK the same with same soc?

I’m not sure if SDK is mean Nvidia hardware design , and PDK is customers modify based on NVIDIA solutions？

[VickNV]

What is the reason you need to control the pin?

[Robin_faith]

Hi VIck

 This pin is connected to 397, so I want to control this pin high/low as a heartbeat pin.

[VickNV]

As mentioned earlier, if you have PDK access, please contact your Nvidia representative for the appropriate support channel.

[Robin_faith]

ok
That’s the end of the question