Controlling WP_GPIO_1 / GPIO22 problem


#1

Hello

I try to control gpio22 (WP_GPIO_2 on the mangoh Red, pin13 on PI header) but I get a warning when starting the app:

-WRN- | gpioService[789]/sysfsGpio T=main | gpioSysfsUtils.c gpioSysfs_SessionOpenHandlerFunc() 1112 | Unable to export GPIO gpio22 for use - stopping session

Changing to gpio21 and the app works fine.
Any tips to get gpio22 working?

image


#2

The pin on the Raspberry Pi header labeled WP_GPIO_1_lvl corresponds to GPIO22 on the outer ring of the CF3 socket. WP_GPIO_2_lvl corresponds to GPIO23 on the outer ring of the CF3 socket.

Lets try to isolate whether this is a Linux problem or a GpioService problem. On my mangOH Red with wp85, I was able to do the following:

# cd /sys/class/gpio
# echo 22 > export
# cd gpio22
# cat direction
in

Now I connect Raspberry Pi header pin 11 (WP_GPIO_1_lvl) to pin 25 (ground)

# cat value
0

Now I connect Raspberry Pi header pin 11 (WP_GPIO_1_lvl) to pin 1 (3.3V)

# cat value
1

The sysfs interface to the GPIO seems to be working. Can you check and see if it works for you?


#3

Sorry, ment WP_GPIO_1. WP_GPIO_2 works.

root@swi-mdm9x15:/sys/class/gpio# echo 22 > export
sh: write error: Device or resource busy

:thinking:


#4

Can you confirm that there isn’t already a /sys/class/gpio/gpio22/ directory before running the echo command?

Please also supply the output of lsmod


#5

Can confirm there is no gpio22 folder. See screenshot below:


#6

Thank you @nilsarve for reporting this problem. There was a bug in a kernel driver which meant that GPIO22 was being taken by the kernel when it shouldn’t have been.

Fixed in this commit


#7

Ok, glad you fixed it. :clap:

I have updated the 2 files.
How do I update my kernel driver?


Cannot get Heartbeat app to work
#8

Assuming you are building the mangOH Red system, then all you need to do is:

$ cd location/of/mangOH
$ git pull
$ git submodule update
$ make clean
$ make red_wp85
$ update mangOH_Red.wp85.update 192.168.2.2

#9

Got it working! Thank you! :+1: