Open Opticulex opened 6 years ago
I have the same issue here. After reflashing to betaflight 3.2.0 and putting the bootloader drivers (with zadig) to winusb. I managed to get it to connect through usb but I don't find a suitable driver to get the flightcontroller "recognised" by windows.
Do you know where I can find the microsoft usb serial device driver? It's not in my driver list on windows, others also don't work.
I don't know about that driver. I had the STM32, Silabs CP2102 and WinUSB drivers and it registered the flight controller in Butterflight on COM3 but refused to connect/communicate or flash. I tried everything I could but assume the board is completely bricked. Sorry I couldn't help but this is a big issue so there should be some warning on it before flashing..
Boot pins?
No its completely bricked.
Definitely you should be able to access STM32 chip directly via pinouts.
Hi everyone, we will look into the issue as soon as possible, for the time being, if you have an STLINK, or you care to buy one for around 10$, you can re-flash the firmware using the data pins on your FC.
This tutorial will help you do that: [(https://www.youtube.com/watch?v=Om6teCbJM4U)]
Basically, the STLINK will power up your FC (you need to bridge the boot pins or press the boot button when connecting it) and you can directly flash the FC using the data pin (apply the hex) without the configurator.
The STLINK is an all-around useful tool to have, so I highly recommend it.
But all that said, we won't take any responsibility if you kill your FC by soldering to a bad pin, or doing something wrong. This is not an easy task, so only recommended if you have some confidence and knowledge in this area.
We will keep you guys posted on the progress of the fix, please be patient though :)
Brotip: if you are ordering stlink then also take some pin-clamper / headers, no need to solder anything :)
On Mon, 9 Jul 2018 at 10:09, LexioTech notifications@github.com wrote:
Hi everyone, we will look into the issue as soon as possible, for the time being, if you have an STLINK, or you care to buy one for around 10$, you can re-flash the firmware using the data pins on your FC.
This tutorial will help you do that: [(https://www.youtube.com/watch?v=Om6teCbJM4U)]
Basically, the STLINK will power up your FC (you need to bridge the boot pins or press the boot button when connecting it) and you can directly flash the FC using the data pin (apply the hex) without the configurator.
The STLINK is an all-around useful tool to have, so I highly recommend it.
But all that said, we won't take any responsibility if you kill your FC by soldering to a bad pin, or doing something wrong. This is not an easy task, so only recommended if you have some confidence and knowledge in this area.
We will keep you guys posted on the progress of the fix, please be patient though :)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ButterFlight/butterflight/issues/177#issuecomment-403381352, or mute the thread https://github.com/notifications/unsubscribe-auth/AOgDyH17WAo6DLRlTm0sWnxsyzdT3oIlks5uEwG0gaJpZM4Ui8lv .
The SPRacing F3 is incomaptible with 3.5.1-RC2 and, while still functioning, will potentially mute your flight controller from any USB communication with no fix. I've tried this on 2 old SPF3's and both of them have become unresponsive through USB and no amount of fixing will help. A big warning for SPF3 boards for the next RC would be good in case there are more issues.