esp-idf: Downloading the program occurs MD5 parity error (IDFGH-4188)

A few days ago can also be a normal download. This download error occurs after updating the firmware library `Flashing project app to 0x10000… esptool.py v2.0-dev Connecting… Uploading stub… Running stub… Stub running… Attaching SPI flash… Configuring flash size… Erasing flash… Unc size 4224 comp size 2635 comp blocks 3 Wrote 2635 bytes at 0x00001000 in 0.2 seconds (90.3 kbit/s)… File md5: b8a3654c3478dbe4ee99e418fac4c5b5 Flash md5: b846cfdf358a11fdf47a71901ec3cda1

A fatal error occurred: MD5 of file does not match data in flash! make: *** [C:/esp32_idf/esp-idf/components/esptool_py/Makefile.projbuild:28:flash] 错误 2`

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 22 (10 by maintainers)

Commits related to this issue

Most upvoted comments

Hi, I had the same problem with a esp32. Than I just disconect all the cables conected to the I/O pins and I tryied to upload again. It worked!

This is mentioned, for example, in ESP32 datasheet, section 2.4 “Strapping pins”. Note at the end of the section says that GPIO12 needs to have low logic level at startup. Alternatively, if you can not guarantee this, you can permanently set flash voltage to 3.3V, by burning efuses using espefuse.py tool. See https://github.com/espressif/esptool/wiki/espefuse#setting-flash-voltage-vdd_sdio for details. Once EFUSE is written, you don’t need to ensure any specific level of GPIO12 on reset.