MD5 of file does not match data in flash! (But works for the code that already running)

[lucasventurasc]

Hardware:

Board: M5Stack with ESP32D0WDQ6
Core Installation/update date: latest
IDE name: Arduino IDE
Flash Frequency: ?40Mhz?
PSRAM enabled: ?no?
Upload Speed: ?921600?
Computer OS: ?Linux Mint?

Description:

Hi, after upload sketchs serveral times for ESP32 module (M5 Stack), I've started to receive an error message when I'm trying to upload:

A fatal error occurred: MD5 of file does not match data in flash!

A interesting thing is if I upload the same code (same that is already running inside of the ESP32) the upload is completed, when I change just a character on the code I receive that error again.

I already tried with all frequencies, all upload speeds and all flash modes, I don't know what to do now.
I read several articles on web and issues on GitHub and most of times it seems something related to "Power Issues". But I'm using the USB-C cable connected to a notebook.

After I've started to receive this error I've uploaded a different codes more than 50 times.

Even a Hello World couldn't be uploaded.

Arduino IDE LOG:

Sketch uses 1023466 bytes (78%) of program storage space. Maximum is 1310720 bytes.
Global variables use 43644 bytes (13%) of dynamic memory, leaving 284036 bytes for local variables. Maximum is 327680 bytes.
python /home/ventura/.arduino15/packages/esp32/tools/esptool/2.3.1/esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0xe000 /home/ventura/.arduino15/packages/esp32/hardware/esp32/1.0.0/tools/partitions/boot_app0.bin 0x1000 /home/ventura/.arduino15/packages/esp32/hardware/esp32/1.0.0/tools/sdk/bin/bootloader_qio_80m.bin 0x10000 /tmp/arduino_build_306541/mp3withnewurl.ino.bin 0x8000 /tmp/arduino_build_306541/mp3withnewurl.ino.partitions.bin
esptool.py v2.3.1
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 8192 bytes to 47...

Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.0 seconds (effective 41978.9 kbit/s)...
Hash of data verified.
Compressed 15072 bytes to 9733...

Writing at 0x00001000... (100 %)
Wrote 15072 bytes (9733 compressed) at 0x00001000 in 0.1 seconds (effective 931.7 kbit/s)...
Hash of data verified.
Compressed 1023600 bytes to 578016...

Writing at 0x00010000... (2 %)
Writing at 0x00014000... (5 %)
Writing at 0x00018000... (8 %)
Writing at 0x0001c000... (11 %)
Writing at 0x00020000... (13 %)
Writing at 0x00024000... (16 %)
Writing at 0x00028000... (19 %)
Writing at 0x0002c000... (22 %)
Writing at 0x00030000... (25 %)
Writing at 0x00034000... (27 %)
Writing at 0x00038000... (30 %)
Writing at 0x0003c000... (33 %)
Writing at 0x00040000... (36 %)
Writing at 0x00044000... (38 %)
Writing at 0x00048000... (41 %)
Writing at 0x0004c000... (44 %)
Writing at 0x00050000... (47 %)
Writing at 0x00054000... (50 %)
Writing at 0x00058000... (52 %)
Writing at 0x0005c000... (55 %)
Writing at 0x00060000... (58 %)
Writing at 0x00064000... (61 %)
Writing at 0x00068000... (63 %)
Writing at 0x0006c000... (66 %)
Writing at 0x00070000... (69 %)
Writing at 0x00074000... (72 %)
Writing at 0x00078000... (75 %)
Writing at 0x0007c000... (77 %)
Writing at 0x00080000... (80 %)
Writing at 0x00084000... (83 %)
Writing at 0x00088000... (86 %)
Writing at 0x0008c000... (88 %)
Writing at 0x00090000... (91 %)
Writing at 0x00094000... (94 %)
Writing at 0x00098000... (97 %)
Writing at 0x0009c000... (100 %)
Wrote 1023600 bytes (578016 compressed) at 0x00010000 in 7.8 seconds (effective 1046.9 kbit/s)...
File md5: 90d74b744eb2a8acade99136e4d7ea55
Flash md5: fe0949ec4dd4af242ed642e2781c707d
MD5 of 0xFF is 36ed8c0cd10f63f644ac82d112d814ef

A fatal error occurred: MD5 of file does not match data in flash!
A fatal error occurred: MD5 of file does not match data in flash!

Thank you for your attention.

[copercini]

Olá Lucas!

I usually get this due bad flashing, like bad quality or too long USB cables, or when there are more things sharing the power supply...
Another tip, try with baud 115200 instead 921600

[lucasventurasc]

Hi @copercini, thank you for reply, I'm using the M5Stack original USB C Cable, which have almost 10 centimeters I think.

I've already tried all disponible bounds, more than 100 times hehe, and the error message is the same always.

There is a way to reset all flash content? like factory defaults?

Thanks

[copercini]

There is a way to reset all flash content? like factory defaults?

Yes, using esptool.py erase_flash

[lucasventurasc]

There is a way to reset all flash content? like factory defaults?

Yes, using esptool.py erase_flash

I think I've already tried that but the old application has not erased (when I've turned up the same application was loaded).

I will try it again, this approach should work for any situation?

[pchidley]

Did you find a resolution?
I have a brand new M5Stack Fire that worked for about 30 minutes.
Then "unable to auto-detect flash".
Tech support said erase the flash. (but didn't say how)
So I erased the flash.
Now I get your "A fatal error occurred: MD5 of file does not match data in flash!"

Any answers?

[samguyer]

I had the same problem, and I discovered that I had my power wires backwards on part of my Arduino circuit. Once I fixed the circuit, the upload went perfectly.

[pchidley]

M5Stack Fire is a preassembled board. So not the power wires.

[pchidley]

Anyone? My M5Stack Fire worked for about 20 minutes when I got it. Nothing but errors since.

[Gabriel-Gardin]

Anyone found a solution? Same problem here, but in my case i faced this error since the first time using the board...

[elf128]

Got the same issue after switching versions of ESP_IDF. Dont really remember exact order.
But effectively, it was switch from some old version to 3.1.2 ( which failed, cause I didn't clean flash and NVS was wrong ).
Then I tried to fix it, but run into MD5 issue.
After switch to 3.2 the issue stays.

The fix for me, was to switch back to my old IDF with esptool v.2.3.1.
Rebuild the project. make flash, now it flashed fine.
Then switching straight to v3.2.

make menuconfig 
make flash

It will rebuild everything again.
And then, flashing works fine.

Don't ask me, how IDF version is relevant, it doesn't make any sense to me, but there we are.
My guess is it has something to do with compatibility of esptool and bootloader.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[chegewara]

Got the same issue after switching versions of ESP_IDF. Dont really remember exact order.
But effectively, it was switch from some old version to 3.1.2 ( which failed, cause I didn't clean flash and NVS was wrong ).
Then I tried to fix it, but run into MD5 issue.
After switch to 3.2 the issue stays.

The fix for me, was to switch back to my old IDF with esptool v.2.3.1.
Rebuild the project. make flash, now it flashed fine.
Then switching straight to v3.2.

make menuconfig 
make flash

It will rebuild everything again.
And then, flashing works fine.

Don't ask me, how IDF version is relevant, it doesn't make any sense to me, but there we are.
My guess is it has something to do with compatibility of esptool and bootloader.

Im having the same issue with m5stack fire and esp-idf 3.1.3. I cant flash it or even erase it.
I know its arduino board, but issue has not been solved.

[pchidley]

I have never figured out what went wrong with my first M5Stack Fire.
However I eventually got it replaced and no problems with the new one.
Probably defective hardware?