ESP32 Forum

Hi all,

New to this forum. Initially, I believe the FW on my ESP8266 module was like 1.7.5. All worked fine, when it powered-up, it displayed a bunch of garbage characters followed by "READY" after which I was able to issue AT commands to check the version or list available networks etc.

I decided to upgrade the FW to the most recent which appears to be 2.2.1.0 which I got off the Espressif website along with the ESP8266 flash download tool 3.9.5.

After launching the flash tool, I loaded the following files with the following addresses as per the included doanload.config file with the FW update:

--flash_mode dio --flash_freq 80m --flash_size 2MB

0x8000 partition_table/partition-table.bin
0x9000 ota_data_initial.bin
0x0 bootloader/bootloader.bin
0x10000 esp-at.bin
0xF0000 at_customize.bin
0xFC000 customized_partitions/client_ca.bin
0x106000 customized_partitions/mqtt_key.bin
0x104000 customized_partitions/mqtt_cert.bin
0x108000 customized_partitions/mqtt_ca.bin
0xF1000 customized_partitions/factory_param.bin
0xF8000 customized_partitions/client_cert.bin
0xFA000 customized_partitions/client_key.bin

I made sure all had a checkmark next to them, everything was green then I hit the START button and FW update appears to have gone through. The output of the command prompt window displayed the following after the update:

Uploading stub...
Running stub...
Stub running...
Changing baud rate to 115200
Changed.
NO XMC flash detected!
crc_efuse_4bit: 0
crc_calc_4bit: 4
Flash will be erased from 0x00000000 to 0x00002fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x00009000 to 0x0000afff...
Flash will be erased from 0x00010000 to 0x000d1fff...
Flash will be erased from 0x000f0000 to 0x000f0fff...
Flash will be erased from 0x000f1000 to 0x000f1fff...
Flash will be erased from 0x000f8000 to 0x000f8fff...
Flash will be erased from 0x000fa000 to 0x000fafff...
Flash will be erased from 0x000fc000 to 0x000fcfff...
Flash will be erased from 0x00104000 to 0x00104fff...
Flash will be erased from 0x00106000 to 0x00106fff...
Flash will be erased from 0x00108000 to 0x00108fff...
Compressed 10480 bytes to 6920...
Compressed 3072 bytes to 129...
Compressed 8192 bytes to 31...
Compressed 793664 bytes to 506377...
Compressed 3072 bytes to 204...
Compressed 4096 bytes to 46...
Compressed 2344 bytes to 1487...
Compressed 3368 bytes to 2527...
Compressed 2344 bytes to 1499...
Compressed 1168 bytes to 895...
Compressed 1692 bytes to 1323...
Compressed 1172 bytes to 914...

is stub and send flash finish

The download progress displayed FINISHED in blue so I hit STOP and closed the app. Then I re-opened my terminal program to monitor the ESP8266 and when I hit the reboot button, it displays its traditional garbage (at 115200 bps) but no longer displays READY. Sending AT commands to it does not return anything. I tied a logic analyzer to the data lines and it doesn't show the READY message either so I know that something is wrong and/or missing. I tried all 4 versions on the website and even tried much older versions and they all behave the same and don't display "READY" after booting and showing the garbage characters.

The ESP is on one of those tiny PCBs with integrated trace antenna and the PCB says "AI cloud inside".

Any help is appreciated to get it back to a running state.

Thanks!

Ben
Canada

Hi.
I am user of esp8266-devkitc-v1 and when I followed the procedures, it worked as expected.
However, if I used esp-wroom-02d, the result was the same as the previous post.
I wonder if any solution was found to fix the issue.
I appreciate if you can post a new one with solution.

Best regards
Joon

Hi, I have the the Mega Arduino with the integrated ESP (Arduino Mega RobotDyn) and exact the same Problem.
I found instructions with the download tool V3.6.6 on the internet. I used V3.9.5. Could it have something to do with that?
Anyone with a solution?

Your 'Garbage characters' are messages generated by the ESP's boot ROM at 74880.

Why 74880? See this post:- viewtopic.php?f=50&t=37181

These boot messages may give you information as to why your software is not responding.

The messages are in the form of:-
I hope this helps.

Here is an interesting bit of information 'the uploaded ESP-AT switches the serial peripheral (UART0) to different I/O pins'!!!!!

This was gleaned from here:-https://sigmdel.ca/michel/ha/esp8266/ES ... .html#v221
It is a long article, to find the relevant part search it for 'I/O pins'