This tutorial saved my ESP32Cam, which was showing the same MD5 error mention in this thread:
https://www.youtube.com/watch?v=lthKBGacyVs
Win+R
cmd.exe
python -m esptool --port COM8 write_flash_status --non-volatile 0
(replace 8 with the number of you Port)
MD5 of file doas not match data in flash ( fatal error )
Re: MD5 of file doas not match data in flash ( fatal error )
The above works perfectly.
If you use Windows and have esptool as .exe installed somewhere, do the following:
WIN+R
cmd
Move to the directory of the esptool.exe.
Then type:
esptool --port COM8 write_flash_status --non-volatile 0
With the respective COM-port where the ESP is plugged.
Hit ENTER.
- you might need to push the BOOT-button on the ESP
- you should close any IDEs accessing the COMport
Afterwards you can upload a sketch like always.
If you use Windows and have esptool as .exe installed somewhere, do the following:
WIN+R
cmd
Move to the directory of the esptool.exe.
Then type:
esptool --port COM8 write_flash_status --non-volatile 0
With the respective COM-port where the ESP is plugged.
Hit ENTER.
- you might need to push the BOOT-button on the ESP
- you should close any IDEs accessing the COMport
Afterwards you can upload a sketch like always.
Re: MD5 of file doas not match data in flash ( fatal error )
Thank you!FBMinis wrote: ↑Wed Jun 14, 2023 4:32 pmThis tutorial saved my ESP32Cam, which was showing the same MD5 error mention in this thread:
https://www.youtube.com/watch?v=lthKBGacyVs
Win+R
cmd.exe
python -m esptool --port COM8 write_flash_status --non-volatile 0
(replace 8 with the number of you Port)
I've spended a couple of hours
before I finded your solution for my problem with MD5... after debugging with ESP-PROG
for macOS you can also use next command in zsh:
./esptool.py -c esp32 -p /dev/cu.usbserial-* -b 115200 write_flash_status --non-volatile 0
That will work if you have esptool.py file inside the folder
also if you added previusly esptool in the PATH variable you may use it as following:
esptool -c esp32 -p /dev/cu.usbserial-* -b 115200 write_flash_status --non-volatile 0
and also as:
esptool -c esp32 write_flash_status --non-volatile 0
Re: MD5 of file doas not match data in flash ( fatal error )
Here https://docs.espressif.com/projects/esp ... ash-status is some explanation about this interesting registers...FBMinis wrote: ↑Wed Jun 14, 2023 4:32 pmThis tutorial saved my ESP32Cam, which was showing the same MD5 error mention in this thread:
https://www.youtube.com/watch?v=lthKBGacyVs
Win+R
cmd.exe
python -m esptool --port COM8 write_flash_status --non-volatile 0
(replace 8 with the number of you Port)
Probably we're doing something like this mentioned:
This command is intended for use when debugging hardware flash chip-related problems. It allows sending WRSR, WRSR2 and/or WRSR3 commands to the flash chip to write the status register contents. This can be used to clear write protection bits, for example:
Code: Select all
esptool.py write_flash_status --bytes 2 --non-volatile 0
A second option --non-volatile can be used in order to send a WREN (06h) command before writing the status. This may allow non-volatile status register bits to be set or cleared.
Who is online
Users browsing this forum: No registered users and 8 guests