Posts: 125 Threads: 12 Likes Received: 86 in 45 posts Likes Given: 52 Joined: Jan 2017 Reputation: 8 Hey people,
as you can read in the title I bricked my Matek F405 that worked perfectly fine when I tried to flash Betaflight 3.2
So right now I've gone through all the tutorials I could find to flash it with Betaflight 3.1.7 but nothing worked.
Here are the Facts:
- I can boot into DFU Mode and it's displayed in the Betaflight Configurator
- I've installed winUSB using ZADIG 2.3
- I've installed the Virtual COM Port driver for my Windows 7 64Bit OS
What's happening:
- I can see it as DFU connection and i can try to flash it and i get
[color=rgba(255, 255, 255, 0.6)]2017-07-26 @ 13:32:51 -- Running - OS: Windows, Chrome: 59.0.3071.115, Configurator: 3.1.1[/color]
[color=rgba(255, 255, 255, 0.6)]2017-07-26 @ 13:33:01 -- Loaded release information from GitHub.[/color]
[color=rgba(255, 255, 255, 0.6)]2017-07-26 @ 13:33:12 -- USB device successfully opened with ID: 1[/color]
[color=rgba(255, 255, 255, 0.6)]2017-07-26 @ 13:33:12 -- Detected device with total flash size 1024 kiB[/color]
[color=rgba(255, 255, 255, 0.6)]2017-07-26 @ 13:33:12 -- Read protection not active[/color]
[color=rgba(255, 255, 255, 0.6)]2017-07-26 @ 13:33:28 -- USB device successfully closed[/color]
- I can clearly see the "Erase" process going on, taking a few seconds and then the progressbar is at 100% in Yellow with the Text "Flashing..." and that's it. Nothing happens.
- The Virtual COM Port driver doesn't seem to work, I don't get any Virtual COMs no Matter in which Mode I boot the FC.
I have yet to try a different computer to test this out I like turtles ![[-]](https://intofpv.com/images/collapse.png) • Posts: 15 Threads: 3 Likes Received: 3 in 3 posts Likes Given: 0 Joined: Apr 2017 Reputation: 0 Hi
I was given this program when I was having the same
problem with a different board but it worked for me
give it try I hope I can attach the file I may need your email
to send it I tried to attach the file it's too big, give me your email
and I'll send it to you the file it's called impulse RC Driver Fixer
just in case you already tried it
Jim • Posts: 125 Threads: 12 Likes Received: 86 in 45 posts Likes Given: 52 Joined: Jan 2017 Reputation: 8 (26-Jul-2017, 12:58 PM)jep4755 Wrote: Hi
I was given this program when I was having the same
problem with a different board but it worked for me
give it try I hope I can attach the file I may need your email
to send it I tried to attach the file it's too big, give me your email
and I'll send it to you the file it's called impulse RC Driver Fixer
just in case you already tried it
Jim Sadly i already used that one and it didn't do the job. It only fixes the Bootloader drive which has no problems. The problem seems to be the Virtual COM Port driver I like turtles • Posts: 125 Threads: 12 Likes Received: 86 in 45 posts Likes Given: 52 Joined: Jan 2017 Reputation: 8 ... i found the issue... It didn't work when i set "full chip erase".... what the hell I like turtles Posts: 5,315 Threads: 672 Likes Received: 3,155 in 1,743 posts Likes Given: 2,030 Joined: Jan 2016 Reputation: 139 only just saw your problem..
Yea I still haven't got to the bottom of it... some of the boards just have this issue with "full chip erase" selected.
However you could "erase settings" in CLI after flashing firmware. just type "Default". • Posts: 1,773 Threads: 30 Likes Received: 1,199 in 755 posts Likes Given: 714 Joined: Oct 2016 Reputation: 45 For me, it seems to be only F4 boards that have issues with "Full Chip Erase" selected • Posts: 4 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2019 Reputation: 0 (26-Jul-2017, 02:47 PM)Apicalis Wrote: ... i found the issue... It didn't work when i set "full chip erase".... what the hell Sorry. I know this is an old thread. Were you able to fix the issue? I'm having the same problem. Thanks! • Posts: 21,152 Threads: 580 Likes Received: 8,913 in 6,593 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (01-Jan-2019, 02:25 PM)bluecoat97 Wrote: Sorry. I know this is an old thread. Were you able to fix the issue? I'm having the same problem. Thanks! Did you actually try flashing Betaflight firmware with the "Full chip erase" option switched OFF as was suggested, or did that not work? • Posts: 4 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2019 Reputation: 0 I initially missed that part of the initial thread. Unfortunately, I tried it tonight and still nothing. I'm able to get the bootloader/ DFU mode and even flash the firmware (with chip erase on and off). But once it's done and the board reboots I'm not able to connect. (tried disconnected... closing beta flight etc) • Posts: 21,152 Threads: 580 Likes Received: 8,913 in 6,593 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (03-Jan-2019, 03:48 AM)bluecoat97 Wrote: I initially missed that part of the initial thread. Unfortunately, I tried it tonight and still nothing. I'm able to get the bootloader/ DFU mode and even flash the firmware (with chip erase on and off). But once it's done and the board reboots I'm not able to connect. (tried disconnected... closing beta flight etc) It sounds like the VCP circuitry inside the STM32F405 microcontroller chip could be fried unfortunately. Connecting in DFU mode uses a different protocol which is why connection and flashing in boot mode probably works fine, and why connection is then lost when the FC boots up in VCP mode. There is no real solution to this other than replacing the STM32F405 microcontroller chip on the board, or just writing off the board and getting a complete new replacement board. • Posts: 12,099 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 (03-Jan-2019, 03:48 AM)bluecoat97 Wrote: I initially missed that part of the initial thread. Unfortunately, I tried it tonight and still nothing. I'm able to get the bootloader/ DFU mode and even flash the firmware (with chip erase on and off). But once it's done and the board reboots I'm not able to connect. (tried disconnected... closing beta flight etc) Do anything populates in device manager when you plug in the FC? • Posts: 4 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2019 Reputation: 0 06-Jan-2019, 06:38 PM (This post was last modified: 06-Jan-2019, 06:39 PM by bluecoat97.) (04-Jan-2019, 02:25 PM)voodoo614 Wrote: Do anything populates in device manager when you plug in the FC? Thanks a bunch for replying! Figured out the issue because of your question. I was able to find the Matek F405 listed in device manager as a USb device (but it was not using the stm32 drivers. I'm guessing this is because I had installed the stm32 and vcp drivers more than once. So once I opened the device and selected to update drivers, I chose the stm32 drivers. And voila! It worked
(04-Jan-2019, 01:45 PM)SnowLeopardFPV Wrote: It sounds like the VCP circuitry inside the STM32F405 microcontroller chip could be fried unfortunately. Connecting in DFU mode uses a different protocol which is why connection and flashing in boot mode probably works fine, and why connection is then lost when the FC boots up in VCP mode. There is no real solution to this other than replacing the STM32F405 microcontroller chip on the board, or just writing off the board and getting a complete new replacement board. Thanks for getting back to me! Figured out the issue. • Posts: 21,152 Threads: 580 Likes Received: 8,913 in 6,593 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Glad you got it working without binning a perfectly good FC. Sorry - I completely forgot it could be to do with driver related issues. It's a good job Voodoo piped up with that suggestion  • Posts: 4 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2019 Reputation: 0 Oh..and one of the biggest clues was that I was able to connect to the FC using the Speedy Bee app. It's crazy to think that it's easier to connect to a FC using an OTG connector and the speedy bee app than it is to use a PC.... • Posts: 12,099 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 06-Jan-2019, 07:04 PM (This post was last modified: 06-Jan-2019, 07:10 PM by voodoo614.) (06-Jan-2019, 06:45 PM)bluecoat97 Wrote: Oh..and one of the biggest clues was that I was able to connect to the FC using the Speedy Bee app. It's crazy to think that it's easier to connect to a FC using an OTG connector and the speedy bee app than it is to use a PC.... Good. I am glad I didn't have to go through the process of installing the correct drivers. Yes, Speedybee is made especially for the FC, so it has the correct drivers. Windows does not, therefore it is a pain. Once you have it installed correctly for one FC, then all future FC also works. Unless you have a FC with cp210x driver. I don't understand why understand some of these guys using Impulserc fixer every time. • |
