Trying to update a new Solo2 to the latest firmware for the key-length bug fix, windows 10 x64 pro, and I get this:
Warning: This is is major update and it could risk breaking any current credentials on your key.
Check latest release notes here to double check: https://github.com/solokeys/solo2/releases
If you haven't used your key for anything yet, you can ignore this.
✔ Continue? · yes
Continuing
Tap button on key...
Waiting for key to enter bootloader mode...
thread 'main' panicked at 'success: HidApi(IncompleteSendError { sent: 60, all: 36 })', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\lpc55-0.1.0-alpha.7\src\bootloader\protocol.rs:110:76
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
It did put it into bootloader mode, and the driver did end up getting installed and the light goes off, but it doesn't actually update it. If I run the update again while it's already in bootloader, I still get the same panic.
I'm using the 0.0.6 release binary for the tool.
(It does work on Linux with the tool installed with cargo install solo2 after updating that config file for ccid)
Trying to update a new Solo2 to the latest firmware for the key-length bug fix, windows 10 x64 pro, and I get this:
It did put it into bootloader mode, and the driver did end up getting installed and the light goes off, but it doesn't actually update it. If I run the update again while it's already in bootloader, I still get the same panic.
I'm using the 0.0.6 release binary for the tool.
(It does work on Linux with the tool installed with
cargo install solo2after updating that config file for ccid)