MD5 mismatch causes download failure Problem

[YouJungChoi]

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:\Users\robocare\Desktop\interactive_tool_ws007\lcd_sd_test_2020_10_14_001_030\build\esp-idf\partition_table && C:\Users\robocare\.espressif\tools\cmake\3.13.4\bin\cmake.exe -E echo "Partition table binary generated. Contents:" && C:\Users\robocare\.espressif\tools\cmake\3.13.4\bin\cmake.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:\Users\robocare\.espressif\tools\cmake\3.13.4\bin\cmake.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:\users\robocare\desktop\interactive_tool_ws007\lcd_sd_test_2020_10_14_001_030\build
Executing "ninja all"...
Executing action: flash
Running esptool.py in directory c:\users\robocare\desktop\interactive_tool_ws007\lcd_sd_test_2020_10_14_001_030\build
Executing "C:\Users\robocare\.espressif\python_env\idf4.1_py3.8_env\Scripts\python.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 2

When 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.

[ESP_Sprite]

What does the hardware around that module look like? Any bootstrap or flash pins that are connected to anything else?

[YouJungChoi]

There are no bootstrap and flash pins connected to anything else.
Additionally, the hardware with Manufacturer: 20 (Device:4017, Detected flash size: 8MB) and Manufacturer: C8 (Device:4017, Detected flash size: 8MB) have the same configuration. The name of the ESP32 module I am using is ESP32-Wrover-E.
And there is an error that the download cannot be done
MD5 of 0xFF is repeating as 988a096f6bee866b744ec2be0247ba9e.

[ESP_Sprite]

Can you share a pic of the hardware, preferably the schematic, just so we can make sure nothing odd is going on there? Any chance you can update esp-idf (or even only esptool) to a more recent version and retry?

[YouJungChoi]

We're sorry, but we can't make the schematics public.

The current version of esptool.py is 3.2. Is this the latest version?

Additionally, when firmware update of ESP32 module with Flash tool provided by Espressif site,
Modules that cannot download firmware have the following characteristics in common.
flash vendor:
C8h: GD
flash devID:
4017h
QUAD;64Mbit
crystal:
40 Mhz
And the modules that can be downloaded firmware have the following characteristics in common.
flash vendor:
20h : N/A
flash devID:
4017h
QUAD;64Mbit
crystal:
40 Mhz