Open thomastt123 opened 6 years ago
@thomastt123 Haha , I think you may need reflash the FC to BF 3.3. If so , you will want FC forced into DFU mode. So have you tried short the boot pin (pin44 of stm32f303) to vcc3v3?
I reflashed it to BF 3.3 but the com port doesn't show up. This is on mac os. any possibility to flash com port drivers on mac os?
I tried to get connection to the fc with windows 10.
I put the fc in dfu mode and reflashed it again to betaflight 3.3.0.
With zadig I put the bootloader driver to winusb.
In standard mode (non bootloader mode), there isn't a port coming up though.
In windows I can get it to assign to COM3 when I put the usb driver to serial connection when the fc is in bootloader mode.
The big problem seems to be that the fc doesn't put out a COM port connection signal.
Why I say this is because when connected in standard mode (not bootloader mode), in zadig there isn't a flightcontroller nor another "generic" usb device coming up.
All betaflight drivers for vcp and 210 are installed correctly
er.... have you check List All Devices
in Options menu of Zaidg? And even though, you still can not find the COM port of your FC?
By the way, there is another situation that will cause com port temporary disappear: gyro hardware error. You will need about 10~20 seconds to see the correct com port after fc finish it's initalize in this situation.
I checked LIST ALL DEVICES and it's not there. It also seems that the fc doesn't initialize like it normally should. I will count the beeps and post in a moment
haha , if the fc doesn't initialize like it normally should, then just wait for 10~20 seconds, then the com port will be founded~~ In this situation, there must be some hardware issue with gyro
It doesn't show up after waiting for a long time. I can flash it in DFU but when not in bootloader mode, there isn't a port showing up. The number of beeps when plugging in a battery are: 3. The 4th and 5th beep aren't there as should be.
er... then i don't know what happened to your FC. Maybe consider to buy another new one is a better way? Haha...
Try ImpulseRc driver fixer.
On Fri, 13 Jul 2018, 08:43 ProjectMockingbird, notifications@github.com wrote:
I JUST had that happen to mine when I was going from Betaflight 3.4 to the latest RC of Butterflight. Now Windows say USB device not recognized.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ButterFlight/butterflight/issues/175#issuecomment-404741706, or mute the thread https://github.com/notifications/unsubscribe-auth/AOLCySc81_ZGwimtY2UEHz3t9JUYkqAaks5uGEF7gaJpZM4Uhpfh .
I got a Crazybee F3 flightcontroller and flashed the firmware to spracingF3 version 3.5.0. After this done succesfully there is no connection possible anymore through usb. The connection port doesn't show up. This is in butterflight 10.4.2