Order #731297 - Goku F405 Hd 1-2s 12a Elrs 2.4g Aio V2 (Icm42688) - Flywoo AIO wont connect on USB

Help Unmanned Tech
1

Order Number: 731297
Product Name: Goku F405 Hd 1-2s 12a Elrs 2.4g Aio V2 (Icm42688)
Brand: flywoo
When connecting to a computer nothing shows up as a com port and it cannot be reached by Betaflight. When powered by the USB lead it shows a blinking green LED and a constant red LED.
I have tried to fix it as a driver issue, i have been through the steps i can understand to try and make it visable and update its firmware, I have used Zadig, Impulse RC and STM Cube and 1 more i cant remember, It never appears as a COM port or a USB device. I have tried to flash it and boot into that mode but nothing about it has changed so i doubt it worked. Strangely you can connect to it via ELRS wifi when powered by a USB lead. But i dont think there is a way to update the FC firmware and only the ELRS

Image Description
Image Description2160Ă—3840 1.44 MB

Image Description
Image Description3840Ă—2160 1.5 MB

2

I understand you’re having trouble connecting your Flywoo Goku F405 HD AIO. The fact ELRS WiFi works confirms power but doesn’t help with Betaflight connection. Let’s re-check systematically:

  • Try multiple different USB data cables (not just charging ones).

  • Try different USB ports on your computer, ideally rear ports.

  • Try putting the board into DFU mode: Disconnect, press and hold the small boot button on the board, plug in USB while holding, then release the button.

  • Uninstall all the current STM32 drivers as sometimes these can cause a conflict, so remove all the STM32/VCP drivers, reboot your PC and try again

  • Check Device Manager: In normal mode, look for “STM Virtual COM Port” under Ports. In DFU mode, look for “STM32 BOOTLOADER” under Universal Serial Bus devices.

  • Run ImpulseRC Driver Fixer: Try running it first with the board plugged in normally, and again if while the board is successfully in DFU mode (as they both use different drivers).

  • Betaflight Firmware Flasher: Only attempt flashing after you confirm the board is seen as “DFU” in Betaflight or as “STM32 BOOTLOADER” in Device Manager. Select the FLYWOOF405HD target.

  • Try another computer: This helps rule out issues with your main PC’s setup.

If none of these steps work, especially if it fails on a second computer, then perhaps there is something else going on that we will need to investigate further.

Kind Regards

Alex

Unmanned Tech Support

How would you rate our customer service?

3

Fixed but tried all these steps, solution at bottom; thank you for putting me on the right track :slight_smile:

I’ll work through the steps, used a dozen wires connected to both USB and USB-C… i showed in the video using the exact cable that worked with my SpeedyAIO caused nothing to be detected.

Ive used ports on both the Motherboard and front panel of my PC, ive tried with and without hub.

Ive put it into DFU mode and it makes no difference except the red LED is on constantly. It never shows in device manager as anything. I have added and removed drivers, restarted and nothing changes.

I have also tried this on a laptop and it doesnt show up there either; it powers up, the LED’s flash regardless of computer and its always showing on wifi ELRS.

  1. make sure you are pressing the right button, rx boot isnt dfu. Even then nothing showed up
    2.Device manager, view, show hidden devices
  2. Remove all instances of STM32 DFU devices and on the last one uninstall the driver as well.
  3. Reconnect pressing the right button and it then shows up in Device manager, betaflight cant autodetect the board, and you want to install FLYWOOF405S_AIO firmware, there is no pro version
4

Thank you so much for getting back to us and for the detailed follow-up! We’re really glad to hear you were able to get your Flywoo Goku F405 AIO connected and working.

We especially appreciate you sharing the specific solution and the correct firmware target (FLYWOOF405S_AIO). That’s very helpful feedback, and we’ll make sure to keep that in mind for future reference and to help other customers who might encounter similar issues. It sounds like getting the correct DFU mode sequence and cleaning up the old drivers was key.

Thanks again for your patience in working through the steps and for sharing the outcome. Please don’t hesitate to reach out if you have any more questions or need further assistance.

Kind Regards

Alex

Unmanned Tech Support

Join our community at dronetrest.com, or on Discord.

1 Like