#Help! Receiver stuck in bootloader mode

1 messages · Page 1 of 1 (latest)

cunning compass
#

Hello guys,
I was building my first drone and went to flash the receiver (happymodel ep1), but the LED was on and solid indicating it was stuck in bootloader mode.

I tried unplugging RX and TX and checking the boot pads but that didn't fix it so I tried to do the recovery process on the ELRS website. But every time I go through it I get: Connecting... then lots of lines of dots https://pastebin.com/v8k0eRM6

I have tried using multiple different UARTs and I am sure the receiver only turns on when plugged into the lipo. I also set Serial RX on on the right UART in betaflight and turned telemetry off.

The FC I am using is Speedybee F405 AIO v2

Any help would be greatly appreciated, Thanks in advance

sinful sandBOT
# cunning compass Hello guys, I was building my first drone and went to flash the receiver (happym...

✨AI-Generated response✨

Getting a receiver stuck in bootloader mode can often be resolved by re-checking your wiring or trying an alternate method. Since your receiver is an ESP-based Happymodel EP1, please follow these steps:

  1. Verify Wiring: Confirm your TX and RX wires are not swapped (Receiver RX to FC TX, Receiver TX to FC RX). Check the Happymodel EP wiring guide.
  2. UART Conflict: Some flight controllers pull RX pads LOW, which triggers bootloader mode intentionally. If the LED remains solid, try wiring to a different UART on your Speedybee F405 AIO.
  3. Passthrough: Ensure all configurators (Betaflight/INAV) are closed, then unplug and replug the USB cable to the FC to clear the port. When flashing via BetaflightPassthrough, ensure you have correctly triggered bootloader mode on the receiver (powering it while holding the boot button or bridging the boot pads).
  4. Alternative Method: If passthrough continues to fail, you may need to flash via a USB-to-UART (FTDI) adapter. Refer to the Happymodel EP updating via UART guide.
  5. Recovery: If the bootloader has become corrupted or the receiver is soft-bricked, follow the unbricking procedure carefully.

please follow up in #help-and-support or #general-quad-help

-# {'cause': 'thread creation'}