|
Technical Support TranscriptRadioMaster RP2 ExpressLRS Firmware Flashing & Connection Troubleshooting << Back |
Yes, you should use the "Erase Before Flash" option when flashing your RadioMaster RP2 ELRS receiver.
While not strictly mandatory for every single minor update, enabling this setting ensures a clean installation by completely wiping any corrupted data or conflicting configuration files from the receiver's flash memory before writing the new ExpressLRS firmware.
Because erasing wipes the memory completely, your previous binding phrase and custom settings will be lost. You must ensure that your correct binding phrase is entered into the ExpressLRS Configurator before flashing, or you will need to manually re-bind the receiver to your transmitter after the process completes.
A build error during RadioMaster RP2 firmware updates usually indicates local ExpressLRS Configurator issues, often resolved by clicking "Clear Cache" and "Reset PlatformIO" in the support tab. If the error persists, using the ExpressLRS Web Flasher to bypass the local compilation process provides a reliable alternative.
======== PASSTHROUGH INIT ======== Trying to initialize COM19 @ 420000 Attempting to detect FC UART configuration... ** Serial RX config detected: 'serial 2 64 115200 57600 0 115200' Enabling serial passthrough... CMD: 'serialpassthrough 2 420000' ======== PASSTHROUGH DONE ======== ======== RESET TO BOOTLOADER ======== * Using full duplex (CRSF) Cannot detect RX target, blindly flashing! esptool.py v4.2.1 Serial port COM19 WARNING: Pre-connection option "no_reset" was selected. Connection may fail if the chip is not in bootloader or flasher stub mode. Connecting...
No, this is not a healthy connection.
Your log shows that the software successfully initializes the Betaflight passthrough command (serialpassthrough 2 420000), but it completely fails to talk to your RadioMaster RP2 receiver right after.
The exact breakdown of why this log indicates a failed connection includes:
Cannot detect RX target, blindly flashing! – This means your flight controller is not receiving data back from the receiver. The Configurator cannot verify what chip it is talking to.Connecting... – When esptool.py hangs on "Connecting...", it is screaming into a void. A healthy flash will immediately transition from "Connecting..." to displaying the chip type (e.g., ESP8285), MAC address, and flash progress bar.The error happens because the receiver chip is either not powered up, not wired correctly, or failing to enter its internal bootloader mode. Work through these steps to fix it: