GPIOs on kernel 5.19.3-bone7 don't work

Hello,

I’m using the kernel 5.19.3-bone7 taken from Robert C Nelson repo. I Build it and use it on my BBB industrial. Everything is fine except the GPIOs I try to lit a led as I always did with other kernel version with:

echo “60” > /sys/class/GPIO/export
echo “out” > /sys/class/GPIO/GPIO60/direction
echo “1” > /sys/class/GPIO/GPIO60/value

But nothing change. The same commands on same beagle with old kernel (4.x) works.
I used the am335x-boneblack-uboot-univ.dtb device tree provided in the kernel source.

Is there some changes in the new kernel for the GPIO control?

Thanks for the help.

P.S.
Below the details of the boot:
U-Boot 2019.04-00002-g31a8ae0206 (May 13 2020 - 09:26:17 -0500), Build: jenkins-github_Bootloader-Builder-139

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver ‘omap_hsmmc’
No match for driver ‘omap_hsmmc’
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4… Card did not respond to voltage select!
Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
Model: BeagleBone Black Industrial:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] …
board_rev=[EIA0] …
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
2237 bytes read in 12 ms (181.6 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-5.19.3-bone7 …
9908736 bytes read in 644 ms (14.7 MiB/s)
debug: [enable_uboot_overlays=1] …
debug: [enable_uboot_cape_universal=] …
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot.dtb] …
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] …
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb …
loading /boot/dtbs/5.19.3-bone7/am335x-boneblack-uboot.dtb …
96097 bytes read in 34 ms (2.7 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] …
uboot_overlays: uboot loading of [/lib/firmware/BB-ADC-00A0.dtbo] disabled by /boot/uEnv.txt [disable_uboot_overlay_adc=1]…
uboot_overlays: loading /lib/firmware/BB-UART1-00A0.dtbo …
1022 bytes read in 205 ms (3.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-I2C1-00A0.dtbo …
1102 bytes read in 145 ms (6.8 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo …
1614 bytes read in 231 ms (5.9 KiB/s)
uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo] disabled by /boot/uEnv.txt [disable_uboot_overlay_video=1]…
loading /boot/initrd.img-5.19.3-bone7 …
5953785 bytes read in 396 ms (14.3 MiB/s)
debug: [console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 root=/dev/mmcblk1p1 rootwait rw] …
debug: [bootz 0x82000000 0x88080000:5ad8f9 88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fa52000, end 8ffff8f9 … OK
Loading Device Tree to 8f9d7000, end 8fa51fff … OK

Starting kernel …

Hello,

I am most likely incorrect b/c I know too little about what is going on w/ the 5.19.x Bone Kernels but…

There was recently a listing in /dev/bone/. I am not quite sure if the /dev/bone/ files hold gpio pins or not but I will check. I am still using 5.10.x kernels now. Have you tried the ti version of the kernel build yet?

Seth

I didn’t try the TI version and I dont0 have the folder /dev/bone, anyway I downloaded compiled and used the kernel 5.4.209-bone65 and with this kernel every GPIO is working properly, so maybe the kernel 5.19 has some bugs…
I’ll use the 5.4.209-bone65 in my project.
Thanks