- These are our current known issues on the zymkey 4.
- We will be doing our utmost to fix these issues in future patches and updates.
- If you don’t see your problem here, please refer to our FAQ topic here.
Issue: Cpu Scaling Governor
We have seen some issues with the scaling cpu governor on the raspberry pi interfere with the i2c bus. This sometimes causes the zymkey to be put into a odd state or return failures from operations that get optimized out by the governor.
Workaround Solution We Recommend!
The raspberry pi sets the scaling governor to be “ondemand” by default. We recommend switching this mode to “performance” to get the best out of the zymkey.
Be warned this will drain more battery power when switched to “performance”!
Set to performance but not persistent on reboot:
- Run as root: sudo su
- echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
Set performance to be persistent on reboot with a systemd service:
Create a .service file in /etc/systemd/system/
Write this code to .service file:
Description=Set scaling governor to performance
ExecStart=/bin/sh -c “echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor”
Enable the service: sudo systemctl enable yourservice
Start the service: sudo systemctl start yourservice
Issue: set_i2c_address is not working
The API function calls to set the i2c address to a different value currently do not change the address from the default of 0x30.
In the case of conflict with another device, change the address of the other device.