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.
Loading
Go to esp32
A fatal error occurred: MD5 of file does not match data in flash esp32
I have come across this thread in search of some advice. I have seen some related threads but still haven’t cracked the nod on my case.
I am using an ESP32 PICO KIT V4 and code involves dht22 and ultrasonic sensors (x2).
I am using a source code obtained from Instructables to determine the volume of water as a percentage. However, my value differ from the code and when I try and manipulate the calculations regarding determining the distance and compile I get the following error:
A fatal error occurred: MD5 of file does not match data in flash esp32
If the values remain the same the code compiles perfectly. I have gained a few hints on how to resolve the problem but non seem to work/relate. Some advice was to take the 5V and connect to 3,3V?? Is this true and would this need to be done whilst compiling? Some advice was based on the pins; I am using GPIO 22 and 23 for trig1 and echo1 and GPIO 12 and 13 for trig2 and echo2. Since the code runs fine if no alterations arre made I assume it is not the pins. I have also tried changing the value to a multiple of 4 (byte) with no success.
Any advice and direction would be appreciated like ice in the desert.
У компании есть проект, который использует Wi-Fi, и я сразу подумал о esp8266 и ESP32. Esp32 — очень хороший чип, но информации о проблемах слишком мало, и большинство из них на английском языке. Это действительно сложно для новичков. решить проблемы.
Я не знаю, как запустить make flash, и он не работает, но make app-flash может быть успешным. Я думал, что это проблема проекта, и проект был перенастроен, но все равно не удалось.
Сначала подумал, что это программная ошибка, поэтому стер все данные во флеш-памяти.Это нормально.Если нет загрузки, esp32 станет кирпичом. Baidu посмотрел, но нет никаких связанных проблем, и нет статей по углубленному анализу esp32. Я могу только Google. Мой уровень английского ограничен. После долгих поисков я нашел решение, когда я собирался выбросить эту доску., я попробовал, и я пошел!
Пробовал: просто выполните esptool.py —port <соответствующий номер порта> write_flash_status —non-volatile 0
Потом сделай прошить и реши проблему
Ощущение: esp32 — действительно очень мощный чип, но действительно мало подходящих учебных материалов, и все еще существуют пороговые значения для людей, которые использовали keil для компиляции микроконтроллеров.
Если вы используете Arduino для программирования, сложность уменьшается, но для тех, кто планирует использовать esp32 в реальных проектах, ограничения arduino по-прежнему очевидны.
esp по-прежнему очень популярен за рубежом, и я искренне надеюсь, что Espressif запустит план для студентов колледжей и так далее, который будет популяризирован в Китае.
Hello.
I am currently using the esp32-wrover-E product. And I am using version 4.1.1 of esp-idf which is published on Github.
I want to update the firmware of esp32-wrover-E.
However, when I run idf.py -p COM30 flash, the following error occurs.
Code: Select all
[1/4] cmd.exe /C "cd /D C:UsersrobocareDesktopinteractive_tool_ws007lcd_sd_test_2020_10_14_001_030buildesp-idfpartition_table && C:Usersrobocare.espressiftoolscmake3.13.4bincmake.exe -E echo "Partition table binary generated. Contents:" && C:Usersrobocare.espressiftoolscmake3.13.4bincmake.exe -E echo ******************************************************************************* && python C:/Users/robocare/Desktop/esp-idf-4/components/partition_table/gen_esp32part.py -q --offset 0x8000 --flash-size 4MB C:/Users/robocare/Desktop/interactive_tool_ws007/lcd_sd_test_2020_10_14_001_030/build/partition_table/partition-table.bin && C:Usersrobocare.espressiftoolscmake3.13.4bincmake.exe -E echo *******************************************************************************"
Partition table binary generated. Contents:
*******************************************************************************
# Espressif ESP32 Partition Table
# Name, Type, SubType, Offset, Size, Flags
nvs,data,nvs,0x9000,24K,
phy_init,data,phy,0xf000,4K,
factory,app,factory,0x10000,3800K,
*******************************************************************************
[2/4] Performing build step for 'bootloader'
ninja: no work to do.
esptool.py -p COM36 -b 460800 --before default_reset --after hard_reset --chip esp32 write_flash --flash_mode dio --flash_freq 40m --flash_size 4MB 0x8000 partition_table/partition-table.bin 0x1000 bootloader/bootloader.bin 0x10000 spi_master.bin
esptool.py v2.9-dev
Serial port COM36
Connecting....
Chip is ESP32D0WDQ5 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 24:d7:eb:67:5a:1c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Compressed 3072 bytes to 105...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (105 compressed) at 0x00008000 in 0.0 seconds (effective 4109.7 kbit/s)...
File md5: 375c2c5c520586874726174d1bb2faee
Flash md5: 988a096f6bee866b744ec2be0247ba9e
MD5 of 0xFF is 988a096f6bee866b744ec2be0247ba9e
A fatal error occurred: MD5 of file does not match data in flash!
Adding "flash"'s dependency "all" to list of commands with default set of options.
Executing action: all (aliases: build)
Running ninja in directory c:usersrobocaredesktopinteractive_tool_ws007lcd_sd_test_2020_10_14_001_030build
Executing "ninja all"...
Executing action: flash
Running esptool.py in directory c:usersrobocaredesktopinteractive_tool_ws007lcd_sd_test_2020_10_14_001_030build
Executing "C:Usersrobocare.espressifpython_envidf4.1_py3.8_envScriptspython.exe C:/Users/robocare/Desktop/esp-idf-4/components/esptool_py/esptool/esptool.py -p COM36 -b 460800 --before default_reset --after hard_reset --chip esp32 write_flash @flash_project_args"...
esptool.py failed with exit code 2When the above error occurred, the method I tried was to enter the following command in the command window, and the following result was obtained.
Code: Select all
esptool.py v3.2
Serial port COM30
Connecting.....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 24:d7:eb:67:5a:1c
Uploading stub...
Running stub...
Stub running...
Initial flash status: 0x0200
Setting flash status: 0x0000
After flash status: 0x0200
Hard resetting via RTS pin...Another strange thing is that when the following command is entered in the command window, the following phenomenon does not occur for Manufacturer: 20(Device :4017, Detected flash size : 8MB), only Manufacturer: C8(Device :4017, Detected flash size : 8MB).
If you know a solution, please help.
Thank you.