Betaflight Said “No Compatible Devices”. Here’s What It Means
Quick Answer
If Betaflight cannot see your flight controller, prove USB before touching firmware. Use a known data cable, connect directly, then check Windows 11 Device Manager, macOS System Information or Linux lsusb. Normal serial and DFU modes need different fixes.
Match the Symptom Before Installing Anything
“No compatible devices found”, “failed to open serial port” and “STM32 BOOTLOADER” are different faults. If the operating system cannot see a new device, Betaflight cannot fix it. Start with the matching row.
| What you see | Likely fault | Next check |
|---|---|---|
| No LEDs and no new operating-system device | No USB power, damaged socket or cable | Try a proven data cable and another direct USB port. Inspect the socket for movement. |
| LEDs light, but the computer detects nothing | Charge-only cable or failed USB data path | Use a cable that transfers files. Remove hubs, magnetic adapters and docks while testing. |
| Windows 11 shows a COM port | Normal serial mode is present | Select that port in Betaflight. If it will not open, close software that may already own it. |
| Windows shows STM32 BOOTLOADER, or Betaflight shows DFU | The controller is in firmware-upgrade mode | Use Firmware Flasher. Repair the DFU driver only if the app cannot access the device. |
| Unknown USB Device or Device Descriptor Request Failed | Enumeration failed before Betaflight | Change cable and port first; inspect the socket. Disconnect peripherals before retrying DFU. |
Fix “No Compatible Devices Found” in the Web App
The browser version needs a browser that supports Web Serial. Use Chrome, Edge or another Chromium-based browser, open Betaflight’s port menu and grant the controller when the browser displays its device picker. Firefox does not provide Web Serial support, so changing an STM32 driver will not make its picker work.
If the picker is empty, unplug and reconnect the board while watching the operating system. No change points to the cable, adapter, port or flight-controller socket. A lit board proves only that USB power arrived, whether it is a SpeedyBee F405 V5 stack or an Axisflying Argus ECO stack.
Windows 11: COM Port, DFU or Unknown Device?
Open Device Manager before connecting the controller, then watch which section changes. A COM port is the normal connection; STM32 BOOTLOADER is DFU. An unknown-device warning means Windows could not enumerate the hardware, so reinstalling Betaflight is unlikely to help.
Windows 10 and 11 normally provide the serial driver for a direct STM32 virtual COM connection. CP210x and CH340 drivers apply only to hardware that contains those bridge chips; an F405 processor name does not prove either is needed.
Repair DFU Without Breaking the COM Driver
DFU is a flashing connection, not the port used for the Setup and Ports tabs. Enter it by holding BOOT while plugging in USB. Seeing DFU does not mean the firmware has been erased.
If Windows lists STM32 BOOTLOADER but the app cannot use it, try ImpulseRC Driver Fixer. In Zadig, the manual fallback, select STM32 BOOTLOADER and replace only that device’s driver with WinUSB—not the normal COM port. Then follow our flashing walkthrough and select the board’s exact target.
Fix “Failed to Open Serial Port”
If the port exists but will not open, close other Betaflight tabs, Arduino IDE, serial terminals and ESC configurators, then reconnect. On Linux, serial access commonly needs dialout membership; log out and back in after adding it. A device that immediately disappears can indicate ModemManager interference.
What We Would Do
- Remove propellers, disconnect the LiPo and connect USB to the flight controller—not the VTX or radio.
- Try a proven data cable and watch for a new operating-system device.
- Use Chromium for the web app and grant the device in the browser picker.
- Identify normal COM, DFU or unknown-device state before changing a driver.
- Close software that may own the port; check Linux permissions where relevant.
- Only then enter DFU, repair its driver if needed and flash the exact target.
This protects working firmware from an unnecessary flash. After connecting, use our flight-controller setup guide. Browse the flight-controller collection only when the cable, socket and USB state point to failed hardware.
FAQ
Why does Betaflight say “No compatible devices found”?
The browser has no supported serial device to offer or has not been granted access. Use Chromium and its device picker. If the picker is empty, check whether the operating system detects the controller.
Does STM32 BOOTLOADER mean my firmware is gone?
No. It means the controller is in DFU mode. Flash only when you intend to update or recover firmware, and use the board’s exact target.
Why does Betaflight fail to open a visible serial port?
Another program may have claimed it, or Linux permissions may block access. Close serial software, reconnect the board and check dialout membership before reflashing.