In recent weeks we have learned that some developers are experiencing difficulties when binding zymkey to their host/application. Also some have seen loss of connection to the Zymkey in a soft shutdown/reboot situation. Not all users have experienced this issue.
Solution in New Code Release
After digging into the symptoms and various use cases, we believe we have now identified the root issue, which relates to how I2C is managed under Stretch and the existence of certain edge/system conditions. The problem is more apparent on RPi 3B+, for a variety of reasons.
Our dev team has a working solution that is being run through production testing and should be available in a new release within 48 hours. The new release will contain more details and context.
Thanks to all who have helped us identify the root issue and build a solution.
We’ll update you when the release is available.
Ok…the new release is here!
For those of you doing an install on a fresh system, just follow the instructions in our “Getting Started” guide.
For those of you doing an upgrade from a previous installation, just run:
sudo apt update
sudo apt -y install --only-upgrade libzk libzymkeyssl zkbootrtc zkifc zkapputilslib zksaapps
sudo pip install zku --upgrade (use
pip3 for python3 support)
For those of you that have an installation that predates Oct. 2018, you may need to update the GPG key for the zymbit repo before running the above:
curl -L "https://zk-sw-repo.s3.amazonaws.com/apt-zymkey-pubkey.gpg" 2> /dev/null | apt-key add - &>/dev/null
A new release which addresses more timing issues was just issued this morning. The instructions are the same as in the previous update.
Debian package version numbers for this release are: