-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solid Red light #2
Comments
The Chopstx U2F program sets To get back into Toboot when that flag is set, take a pair of tweezers and short out the two outer pads as you plug it in. I'll leave this bug open for a little while, at least until we get some suggestions on where to document the flag better. |
Thanks @xobs I'm really glad my new Tomu isn't broken and there was an easy way to get it back to normal. As to where to document this, I'm not sure of one place, but in my case it would be great to have a "what's next" or "how to use" type section as part of the Chopstix In addition, it could be a section in either Quick Start or the Sample code, "Solid Red Light?, Here are some things to try." To add some more details (and perhaps this should be moved to Chopstix) I'm used to my Yubikeys and bought Tomu as a more open and affordable replacement. Thus I was expect a OTP to be sent upon touch in a text editor and for Google to recognize the key. When these things didn't happen and I had a solid red light I went to the worse case senerio, everything being broken. |
I think you have the same problem I had, the u2f links the wrong libc and the program fails. |
Hi,
I just got my Tomu's and after trying to load the chopstix/u2f bin I now get a solid red light. Does this mean the key is toast or is here a way to reset it?
When I run
dfu-util -l
I'm informed no devices are found. I have 9 other keys but want to make sure I don't break them too, and also learn what's going on.Thanks.
The text was updated successfully, but these errors were encountered: