# Zymkey doesnt bind properly

**URL:** <https://community.zymbit.com/t/zymkey-doesnt-bind-properly/1633>\
**Category:** Uncategorized\
**Created:** [March 11, 2024, 5:49pm UTC](https://community.zymbit.com/t/zymkey-doesnt-bind-properly/1633 "2024-03-11T17:49:25Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Bob\_of\_Zymbit](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@Bob\_of\_Zymbit](https://community.zymbit.com/u/Bob_of_Zymbit)\
**Post date:** [March 14, 2024, 12:26am UTC](https://community.zymbit.com/t/zymkey-doesnt-bind-properly/1633/11 "2024-03-14T00:26:21Z")

</div>

@Mr123 It looks like bookworm was updated yesterday and the rpi-6.6.x kernel no longer overrides an upstream kernel decision to force the base number of the main GPIO controller to be global GPIO 0. The new numbering goes like this:

pi@bookworm64:~ $ head /sys/kernel/debug/gpio  
gpiochip0: GPIOs 512-569, parent: platform/fe200000.gpio, pinctrl-bcm2711:  
gpio-512 (ID\_SDA )  
gpio-513 (ID\_SCL )  
gpio-514 (GPIO2 )  
gpio-515 (GPIO3 )  
**gpio-516 (GPIO4 |sysfs ) in hi IRQ**  
gpio-517 (GPIO5 )  
gpio-518 (GPIO6 )  
gpio-519 (GPIO7 )  
gpio-520 (GPIO8 )  
pi@bookworm64:~ $

For the PI4, GPIO4(PIN7) now maps to 516.

Try and specify using 516 as our WAKE\_PIN and restart zkifc.

```auto
sudo su
echo "ZK_GPIO_WAKE_PIN=516" > /var/lib/zymbit/zkenv.conf
systemctl restart zkifc

```

Let me know if that works and I’ll fix our install script.

---

_[View the full topic](https://community.zymbit.com/t/zymkey-doesnt-bind-properly/1633)._