Not able to output high from GPIO on Dev Kit Carrier board J12 JetPack 5.0 DP

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
,
#1

JetPack 5.0 DP was installed on Xavier NX (production version) + Dev Kit Carrier board using SDK manager without any modification.

There are two issues about GPIO in this DP version:

  • cat /sys/kernel/debug/gpio shows tegra194-gpio-aon starts at gpio-305 not gpio 248 as in JP4.6.1. tegra194-gpio starts at gpio-335 instead of gpio-288 as in JP4.6.1. Also the the gpio-line-names of all gpio are shows as the their SoC GPIO Port #, instead of the things specified in the sources/hardware/nvidia/platform/t19x/jakku/kernel-dts/common/tegra194-p3509-0000-a00.dtsi. Please find the attached output from gpio.
nvidia@ubuntu:~$ dmesg | grep GPIOs
[    3.386936] gpiochip0: registered GPIOs 504 to 511 on max77620-gpio
[    5.236837] gpiochip1: registered GPIOs 335 to 503 on tegra194-gpio
[    5.238638] gpiochip2: registered GPIOs 305 to 334 on tegra194-gpio-aon
  • GPIO doesn’t output high when I set the value. For example: pin29 of J12 always shows 0 V while doing:
root@ubuntu:/home/nvidia# echo 440 > /sys/class/gpio/export 
root@ubuntu:/home/nvidia# echo out > /sys/class/gpio/PQ.05/direction 
root@ubuntu:/home/nvidia# echo 1 > /sys/class/gpio/PQ.05/value

The same testes shows correct results on JP4.6.1.
gpio_jp5.txt (7.2 KB)

The GPIO pin works as expected if the direction is in(value is 1 if connect to high and 0 if connected to 0) in JP5.0 DP.

Please help me to check. Thanks!

#3

There is a known issue over K5.10 GPIO and we are still investigating it.

#4

Got it. Thanks for letting me know!
Is this related to issue 3499398 (GPIO configuration utility does not work as expected in Linux 5.10 kernel included in Jetpack 5.0 DP release.) in the release notes? Just want to keep a record to track it on my side. Thanks!

#5

Yes, that is issue 3499398.

#6

Thanks! Please let me if there is any temporary solution to output high from GPIO. It is kind of important for our project.

I also have problem with the jetson-io.py (flash terminal then no response) on this set of hardware (production Xavier NX + dev kit carrierboard). However jetson-io.py works (show options) on another set of hardware (dev kit Xavier NX + custom carrier board). I didn’t test functionality of the program.