may I know which Jetpack release version you’re using?
BTW,
where did you obtain 28?
[edit] revise the erroneous.
you may refer to tegra194-gpio.h for the port index for AON GPIO, which is 2.
so, the calculation formula of GPIO3_PCC.03 should be… (248 + (2 * 8) + 3) = 267
Your guessing is right. I’ve just guessed from Jetson Nano.
Anyway, I tried to access sysfs GPIO, but I failed.
When I run “echo 275 > /sys/class/gpio/export”, it showed below message.
-bash: echo: write error: Device or resource busy
If I checking gpiolist via “sudo cat /sys/kernel/debug/gpio”, I can’t find GPIO 275. Attached file is showing result for “sudo cat /sys/kernel/debug/gpio” gpiolist.txt (8.9 KB)
Jetpack Version is 4.6.1.
I want to access GPIO06 because GPIO06’s SODIMM number is 130 and our custom board is using this pin.
it mean this pin is occupied.
as you can see in pinmux spreadsheets, this sample usage is [Baseboard CAM MUX Sel].
for example, $public_sources/kernel_src/hardware/nvidia/platform/t19x/jakku/kernel-dts/common/tegra194-camera-jakku-rbpcv2-imx219.dtsi
#define CAM_I2C_MUX TEGRA194_AON_GPIO(CC, 3)
for your own product design and use-case,
please update the device tree accordingly to remove this pin definition.
thanks