Able to build & flash blue pill, but no usb device when connected to PC about u2f-token HOT 6 CLOSED

Hi @Sklv ,

I've checked your binary and it doesn't work for me either. Are you by chance using Ubuntu 18.04 LTS? Apparently, there is a bug in newlib which causing any binary using newlib to crash. Here is the bug report https://bugs.launchpad.net/ubuntu/+source/gcc-arm-none-eabi/+bug/1767223 and one possible workaround is to install newer package bbcmicrobit/micropython#514 (comment)

from u2f-token.

Please write the command from which you are programming the device.
Most likely this is a bug of the program that loads the firmware. Try to repeat these commands several times, maybe the device has not been erased completely or protection has not disappeared, try switching the loader jumper and again these commands.

reset halt
stm32f1x unlock 0
reset halt

from u2f-token.

Use kali linux, its best os)))

from u2f-token.

I tried with the unlock commands enabled, and all configurations of the bootloader pins to get the same results as before.
I'm using gentoo with a toolchain built with crossdev -s4 -S --ex-gdb -t arm-none-eabi which i have been led to believe in the openocd irc, might be the cause of my issues.
I will try to non-self-built toolchain and see if it makes a difference.

from u2f-token.

I've seen this thread with similar issues on Gentoo caused by incorrect build flags.

from u2f-token.

I've verified that my toolchain is the issue, as I compiled with the toolchain from arm.com and everything is working. Thanks all for the prompt replies, advice and firmware :)

from u2f-token.