Custom board gpio-348 is busy

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

we use GPIO04, GPIO05, GPIO20, GPIO21，but only GPIO04（GPIO_PA.02） can be controlled, GPIO21(GPIO3_PA.00), GPIO05(GPIO3_PA.01), GPIO20(GPIO3_PA.03) are used by null，
how could i fix this problem？

image
image625×371 8.48 KB

hardware design:

image
image953×123 10.3 KB

pinmux:
image

3

Hi 735038964,

It seems you are using the custom carrier board.
What’s the Jetpack version in use?

Do you want to use these 4 pins as Output?
How do you configure them in pinmux spreadsheet?
Have you checked if any driver may requested those pins?

4

1、we use jetpack 5.1.3

2、We are using pin B58 as input, which works fine. We use other pins as output, but they are occupied by (null), so we can not control them

3、pinmux changes:
image

4、there is no driver request those pins

5

these pin are used as p3737_vdd_3v3_sd、p3737_vdd_12v_pcie、p3737_vdd_dp，which are defined in tegra234-p3711-fixed-regulator.dtsi

6

Please share this dtsi for further check.

Have you tried to remove them from here?

# cat /sys/kernel/debug/gpio |grep PA.0
 gpio-348 (PA.00               |fixed-regulators:reg) out lo 
 gpio-349 (PA.01               |fixed-regulators:reg) out hi ACTIVE LOW
 gpio-350 (PA.02               )
 gpio-351 (PA.03               |fixed-regulators:reg) out hi 
 gpio-352 (PA.04               )
 gpio-353 (PA.05               )
 gpio-354 (PA.06               )
 gpio-355 (PA.07               )

I’ve just checked on the devkit, it seems default occupied by fixed-regulators, please try to remove them from regulator@110, regulator@111, regulator@114