ESP01S flashing returns scrambled console log

Hello WLED community,

I have Issues flashing my ESP01S boards with a ch340 flasher board.
I have tried the WLED online flashing, the inofficial online flasher, the homeesp flasher with the downloaded binary (see screenshot) and the “flash download tool” all with no success.

Although flashing progress is stated as successful, an WLED-AP is showing up but no connection is possible (adress http://4.3.2.1 not reachable by browser or the app).

In the console or in the putty serial monitor hyroghlyphes are shown.

Do I have faulty boards (from aliexpress) or did I do some other mistake you could point out?

Thanks and Regards, Dolomito

I would try using the esptool, instructions are in the KB: Installing

It may be helpful to make sure and fully erase the chip before you attempt an install.

Hello divsys,

unfortunately I couldnt achieve any other outcome when explicitly erasing the chip before flashing.

Ive tried the wled flasher, recommended by the tutorial you linked and I got the same outcome.

Regards, Dolomito

What you posted looks like the esptool (inside ESP-flasher) flashing the ESP.
That’s a good thing, it shows you’ve got the correct serial port configured to reach the ESP.

Try to run esptool directly, that way you can see what commands are being sent to the software rather than ESP-flasher getting in front of things. It will also give you access to a bunch of other commands in esptool (like flash_id, which can give you the mfg make of the chip on your board)

Next thing to look at is what version of WLED you’re trying to load.
Where did you get the .bin file you’re loading?
I also noticed that esptool thinks that chip has only 1MB of flash.
You’ll have to pick a bin file that’s designed for that size of chip.
You could try to go back to something older (V0.13.2?) to see if it makes any difference.

Lastly, I found an old thread on this topic that may or may not help… ESP01 flashing

I do not use esp01 in production as it is very slow for me but just testing for you ,as you see in the pic on old unit as well as on latest (I used WLED_0.15.0-rc1_ESP01.bin ) there is some garbage output same as you got but unit seems fine after flashing the same way you did in your 2nd pic and I can see the ap and connect as usual . If you are facing issues still then the practical thing is to use debug build and look at serial for hints but I would not rule out damaged HW as I had some multiple times and all had issues with wifi due to abuse from our side when testing

Try to change flash speed to 115200 it helps sometime.

We will try but there seem to be an issue with the build WLED_0.15.0-rc1_ESP01.bin as also reported by someone on discord in beta testing channel

We are trying WLED_0.15.0-rc1_ESP01_compat.bin and it is much more reliable

Rc1 from recent repo?

Yes WLED_0.15.0-rc1_ESP01.bin is having the issues

Thank you divsys, for the thread link, I’ve tried the DIO flash mode with no success.

I also tried compiling manually in vscode with the arduino core version set to 2_7_4 instead of 3_2_0 but I had major issues with dependencies when trying to compile with platform IO. (I gave up on that end as it is way too deep into programming for me)

I have tried several versions, all with the same problem and I get the binary files from github directrly.

Thank you ALDIY for your take.
Do you mean the PIO debugger as debug build?
With the rc1 version (ESP01 and ESP01_compat) the AP was showing up but it statet wrong password although using “wled1234”. Really wierd behavior.

I guess I have to use yet another uC supplier.

Regards, Dolomito

OMG, I was able to make it connect.

I used the CH340 flashing board to power the ESP01S when testing but i guess it automaticly puts the uC in bootloader mode.
When powering it discretely with a power supply I finally got it to work. (Currently running the 0.15.0-rc1_ESP01_compat.bin)

I’ll test it further and thank you guys!