Failed to set gpioset for GPIO

update JetPack6.1
need set PH.06 gpio output and value =1

eg:
busybox devmem 0x02434008 w 0x004
gpioset PH.06=1

log:
gpioset: at least one GPIO line offset to value mapping must be specified

Hi,
On Jetson platforms, we support using peripherals like CAN, SPI, I2C, UART… etc. for the user.
For CAN usage:
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/HR/ControllerAreaNetworkCan.html
For the connection of peripheral on the devkit, please refer to expansion-headers guide and carrier board specification:
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/HR/ConfiguringTheJetsonExpansionHeaders.html

For pin configuration, please refer to pinmux spreadsheet:
https://developer.nvidia.com/embedded/secure/jetson/agx_orin/jetson_agx_orin_pinmux_config_template.xlsm

By default, the configuration is used for the devkit. If you are using the custom carrier board, please configure it according to your custom board design.

There are also several examples which have been verified from us, please check
https://elinux.org/Jetson/L4T/peripheral/
Please share the full dmesg and device tree for us to check your status in detail.

Thanks!

请问jetpack6.2版本为什么没有 /sys/class/gpio 目录了
在之前的版本里,可以通过类似如下的方式:
cd /sys/class/gpio
echo 428 > export
echo 1 > value
来修改IO电平,
现在为何不支持了?
我使用的内核版本如下
Linux tegra-ubuntu 5.15.148-tegra #1 SMP PREEMPT Fri Feb 7 17:12:15 CST 2025 aarch64 aarch64 aarch64 GNU/Linux

Hi JiaZW,

Please run the following command instead.

# gpioset --mode=wait `gpiofind "PH.06"`=1

Hi 809656875,
The method of using sysfs to control GPIO has been deprecated in JP6.x.
It is from the upstream kernel (K5.15.x).
Please use gpio character device interface instead.
You can also find more details in gpioset(1) — gpiod — Debian experimental — Debian Manpages

 gpioset --mode=wait `gpiofind "PH.06"`=1

Still failed to configure

log:
gpioset: at least one GPIO line offset to value mapping must be specified

PH.03 and PH.06 are already occupied

How do you configure high and low levels in this case?

It seems camera driver is using these 2 pins.
Please try to remove them from device tree if you want to control them manually.

I did not add these two GPIO configurations in the dts overlay I wrote myself

Are these two GPIO configurations occupied in the official driver dts itself??

Yes, they may be enabled by default.

Please remove camera-control-output-low section in gpio@2200000 node.