Solid Red light about tomu-quickstart HOT 3 OPEN

The Chopstx U2F program sets TOBOOT_CONFIG_FLAG_AUTORUN, which causes Chopstx to always run at poweron by default, under the theory that you wanted to use Tomu as a U2F key rather than developing software for it. This flag is documented on the Tomu Bootloader page, but it probably should be made much clearer. Any suggestions where it should be written?

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.

from tomu-quickstart.

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 ReadMe.md I'd be happy to help write some docs and submit a PR once I figure things out myself :D

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.

from tomu-quickstart.

I think you have the same problem I had, the u2f links the wrong libc and the program fails.
See this: https://groups.google.com/forum/#!topic/tomu-discuss/HtlArkEWhCo
Seems to be an issue with Ubuntu 18.04 based distros(bionic):
bbcmicrobit/micropython#514 (comment)
You need to install those 2 debs linked there.

from tomu-quickstart.