v1.2.2 and v1.1.1 fails to bootup (Stuck in bootloader ? )

[echoGee]

Unable to see the pixracer wifi after flashing the firmware v1.2.2 or v1.1.1 . Steps to reproduce

1. Use the hardware: ESP8266EX along with USB-TTL convertor
2. Follow https://docs.px4.io/en/telemetry/esp8266_wifi_module.html#flashing-the-esp8266-firmware to upload the firmware.
   ESP is powered using a power supply rated for multiple amps of current
   Flash mode:
   CH_PD is pulled high
   GPIO0 is connected to ground
   Normal mode:
   Disconnect Ch_PD and GPIO0
3. Power cycle ESP8266 and check for wifi connections
4. Read the Serial output(at 78400 baud) to get the following output(ESP still in bootloader ?):

ets Jan 8 2013,rst cause:1, boot mode:(3,2)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v8b899c12
~ld

Any suggestions to solve this ?

[dogmaphobic]

Given the code hasn't changed in well over a year, my guess would a defective ESP8266 module? Have you tried flashing something else just to test it?

[echoGee]

@dogmaphobic : Yes I have and it did work. I also tried 3 different ESP8266 modules

[Bumerangas]

for me too not flashing, stuck at some point at mid with nodemcu-flasher-master tool.

i was able to flash it ~half year ago and now bricking my wifi module this FW and same situation with latest firmware-esp01_1m.bin after flash - module brick, especially via web interface

[Bumerangas]

this problem started after i updated my esp-01 module to this FW
http://firmware.ardupilot.org/Tools/MAVESP8266/2019-01-23/

[echoGee]

for me too not flashing, stuck at some point at mid with nodemcu-flasher-master tool.

i was able to flash it ~half year ago and now bricking my wifi module this FW and same situation with latest firmware-esp01_1m.bin after flash - module brick, especially via web interface

This was not the issue I had though

[Bumerangas]

Solved after changing FTDI adapter 5V to 3.3V.