Could someone please fill in the blanks please:
Attempt 1: Follow the manual at: https://docs.solokeys.io/solo/building/#programming
Attach a vanilla STM32L432KC board to the usb port.
cd targets/stm32L432make build-hackersolo program aux enter-bootloaderAttempt 2:
cd targets/stm32l432make build-hackersolo key versionAttempt 3:
cd targets/stm32l432make build-hackersolo key versionExpected result: The STM32L432 behaves like a solo-key-hacker on the usb plug that is on the board.
Please help, what am I missing here? Do I need an additional USB cable connected to the STM32L432KC and what pinson the board do I have to connect to the cable ?
Or do I need to set different settings in the programmer so it starts to act like a Solo key after flashing.
And can this info please get incorporated into the Documentation. I think setting up contributors by guiding them through the steps from 0 to hero with the STM32L432KC board is very helpful. I like to dive into the code not getting hold back by the lack of my knowledge about the development hardware used. Getting a simple step by step how to get it flashed and setup that it behaves like a Solo hacker would be very helpful.
Many thanks in advance for filling in the blanks.
JWR
One piece is solved. You have to connect an USB cable as follow:
On this USB cable to solo key will appear:
solo key info works!solo key version (does not work, don't know what wires are the button...)Questions remain:
FYI, a while ago we received this PR https://github.com/solokeys/solo/pull/65
I don't have a board to validate, but when working we can likely merge into our docs.
Yes! I can confirm that this works on the STM32L432KC as described in PR #65
I was able to build the Solo key and do a successful authentication with it on a test website on FIDO2 including the button press by shorting wire A0 with gnd for a button press.
Think merging it would be helpful. Thank you for the link!
I'll update it with OsX details when it's merged.
Issue can be closed :-)
Awesome - @nickray given it's confirmed we should prob merge, thoughts?
We're just waiting on @szszszsz to remove the explicit copyright injection.
oh I see, hope he does.
For now I'm not able to get the debugger stream flowing in OsX since it lacks udev. It is connecting but nothing comes through yet. Will have a look into that
@nickray Copyright has been removed by szszszsz 馃憤
There is some merge 'code quality' problem which is odd since we're only dealing with a readme. Rest I think its ready to merge :-)
HowTo has been merged:
closing this issue.
Most helpful comment
We're just waiting on @szszszsz to remove the explicit copyright injection.