Ololo. Girls and boys. I have such receivers connected to the Ardupilot or a new receiver that I can solder to the UART-USB adapter. And there is another one who lives in FC Happymodel F405 Crazy. Which of them will we torture?

Thanks guys!

@lyoha: Lol. You don't need to go torturing anything on my behalf. Thank you though. I figure "something" must be wrong with the image I compiled. I ordered a new ep1 tcxo, just in case. I would, however, like to sort out the receiver in the brand new AIO.

@V-22: Many thanks. I guess I hadn't really thought of them as being "bricked". I will read through the link and see where that approach gets me...

Progress! The AIO re-flashed correctly after holding down the boot button and works fine. Thank you again V-22 for pointing me in the right direction.

The external ep1 however refuses to work correctly. I pulled the 5V and shorted the boot pad to ground. It comes up in bootloader mode with a solid led and, after applying 5V at the correct time, it flashes successfully.  It then resets and the rx light goes *out*. I clear the boot pad and restart... The rx light never comes on and wifi becomes available almost immediately. The wifi interface works normally. I'm basically back in the failure mode I started with. I did this a couple times with 3.3.1 and once with 3.2.1. I think it's possessed or something.

One thing I noticed: I am unable to use the erase before flashing option. Is this supposed to work?



If I get a chance tomorrow I think I'll swap in the other ep1 I purchased at the same time... If that one doesn't flash correctly I'll install the ep1 tcxo I just picked up.  Thanks again guys.

Meh. I swapped out the the EP1 and this one works fine... There was definitely something wrong with my elrs image that caused that configuration page in my first post... Why did the AIO reflash just fine and the EP1 did not? Maybe because I saved on EP1's empty config page? Maybe it's just a coincidence that I ended up with a bad image, affecting two units *and* the EP1 just went bad. Whatever the case, it does not seem to work correctly now.

I'm calling this one solved.

(09-Dec-2023, 05:44 AM)drumgod Wrote: Progress! The AIO re-flashed correctly after holding down the boot button and works fine. Thank you again V-22 for pointing me in the right direction.

The external ep1 however refuses to work correctly. I pulled the 5V and shorted the boot pad to ground. It comes up in bootloader mode with a solid led and, after applying 5V at the correct time, it flashes successfully.  It then resets and the rx light goes *out*. I clear the boot pad and restart... The rx light never comes on and wifi becomes available almost immediately. The wifi interface works normally. I'm basically back in the failure mode I started with. I did this a couple times with 3.3.1 and once with 3.2.1. I think it's possessed or something.

One thing I noticed: I am unable to use the erase before flashing option. Is this supposed to work?

Code:

 ** Searching flight controllers **
     > FC found from '/dev/ttyUSB0'

Detected the following serial ports on this system:
 /dev/ttyUSB0

======== PASSTHROUGH INIT ========
 Trying to initialize /dev/ttyUSB0 @ 420000


Attempting to detect FC UART configuration...

   ** Serial RX config detected: 'serial 1 64 115200 57600 0 115200'
Enabling serial passthrough...
 CMD: 'serialpassthrough 1 420000'

======== PASSTHROUGH DONE ========
======== RESET TO BOOTLOADER ========

 * Using full duplex (CRSF)

Cannot detect RX target, blindly flashing!

esptool.py v4.2.1
Serial port /dev/ttyUSB0
WARNING: Pre-connection option "no_reset" was selected. Connection may fail if the chip is not in bootloader or flasher stub mode.
Connecting...
.

Chip is ESP8285H16
Features: WiFi, Embedded Flash
Crystal is 26MHz
MAC: 70:03:9f:1c:e1:82
Enabling default SPI flash mode...
Configuring flash size...
Erasing flash (this may take a while)...

If I get a chance tomorrow I think I'll swap in the other ep1 I purchased at the same time... If that one doesn't flash correctly I'll install the ep1 tcxo I just picked up.  Thanks again guys.

That erase before flash error is normal, as the flash gets erased on the ESP8266 but it never returns a "complete" status so the Configurator hangs and eventually errors out. After that happens, you just need to flash again without "erase flashed" checked to complete the process.

Hey,
I just had the same problem, but solved it differently.
I was stuck on 3.3.2 with the same symptoms - directly going into WiFi, LED solid on but dimmer than usual, missing config file. Happened with two RXs, one flashed via Betaflight Passthrough, the other one via Wifi.
Fix:
-went to a different PC (I think something during the build process might have gone wrong)
-flashed 2.5.2 via WiFi (after saving the non-existing config in this weird submenu on the Wifi page)
-flashed 3.2.0 via WiFi
-optional: flashed 3.3.2 via WiFi