PM.00 K57 GPIO Output Failure

Robotics & Edge Computing Jetson Systems Jetson Thor
1

Hi, NVIDIA

I’m using Thor and JP7.1 with our floor
Configure pinmux as follows:
sudo cat /sys/kernel/debug/pinctrl/810c281000.pinmux/pinconf-groups
32 (gp_pwm9_pm0):
pull=0
tristate=0
enable-input=0
open-drain=0
io-reset=0
rcv-sel=0
io-hv=0
schmitt=0
pull-down-strength=8
pull-up-strength=8
drive-type=1
gpio-mode=1
function=gp_pwm9
I attempted to configure the output via gpioset and captured the peripheral using a logic analyzer, but observed neither pull-up nor pull-down.
gpioset -m wait gpiochip2 88=1

gpioset -m wait gpiochip2 88=0

Is there an error in my configuration? How should I troubleshoot this?

BR.

3

Hi Youke,

Are you using the devkit or custom board for Thor?

Could you use pinmux spreadsheet to configure the pinmux instead?
Please share the screenshot how do you configure the pin in pinmux spreadsheet.

To control PM.00, you can try running the following command.

# gpioset --mode=wait `gpiofind "PM.00"`=1
# gpioset --mode=wait `gpiofind "PM.00"`=0
4

Hi Kevin，

I am using a custom board.
The pinmux spreadsheet is as follows:

d5c4435e83b4372e550d5cf37015b9d8

I tested:

gpioset --mode=wait gpiofind “PM.00”=1

gpioset --mode=wait gpiofind “PM.00”=0

The output did not change (connected to a logic analyzer for capture).

5

Could you check if the default state of PM.00 is HIGH after you apply this configuration?

Please also check if the issue is specific to this pin. (i.e. would you hit similar issue if you control other pin?)

6

Hi Kevin,

Upon entering the system, I found that the default PM.00 pin is at a low level.

I tested other pins on the board: PP.04, PR.01, PB.07, and PV.00 can be configured using gpioset.

BR.

7

Do you mean the default state of PM.00 is LOW even if you have configured it as Output/Drive 1 in pinmux spreadsheet?

And the current issue is specific to PM.00?

8

Yes

I tested it and found that gpioset cannot be used to configure PE.03, PP.02, PZ.00, or PE.02 either.

11

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0422

Could you help to check if the issue is specific to your custom carrier board?
There’s test point (TP229) on the devkit for K57(PM.00).

Please also share the result of the following command for further check.

$ sudo busybox devmem 0x810c282040