[问答]

ESP32-WROOM-32D无法写入flash，MD5检验错误：MD5 of file does not match data in flash怎么解决？

问答对人有帮助，内容完整，我也想知道答案 0 模组：ESP32-WROOM-32D ESP-IDF版本：4.3.1 尝试编译烧写example/hello_world实例，正常编译无法烧写：日志如下: Serial port COM10 Connecting.... Chip is ESP32-D0WD (revision 1) Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None Crystal is 40MHz MAC: 4c:75:25:57:0f:64 Uploading stub... Running stub... Stub running... Changing baud rate to 460800 Changed. Configuring flash size... Flash will be erased from 0x00001000 to 0x00007fff... Flash will be erased from 0x00010000 to 0x00039fff... Flash will be erased from 0x00008000 to 0x00008fff... Compressed 25440 bytes to 15871... Writing at 0x00001000... (100 %) Wrote 25440 bytes (15871 compressed) at 0x00001000 in 0.4 seconds (effective 466.9 kbit/s)... File md5: b181f1484c264652f0f20d506db35eca Flash md5: 4c03feeb3298a10ad0ea93ed8c09925b MD5 of 0xFF is 281039d6031a5a11af6c530e21de18d6 A fatal error occurred: MD5 of file does not match data in flash! CMake Error at run_serial_tool.cmake:56 (message): C:/Users/legen/.espressif/python_env/idf4.4_py3.8_env/Scripts/python.exe F:/cv/Esp32Dev/ESP/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32 failed FAILED: CMakeFiles/flash cmd.exe /C "cd /D F:cvEsp32DevESPesp-idfcomponentsesptool_py && C:Userslegen.espressiftoolscmake3.20.3bincmake.exe -D IDF_PATH="F:/cv/Esp32Dev/ESP/esp-idf" -D SERIAL_TOOL="C:/Users/legen/.espressif/python_env/idf4.4_py3.8_env/Scripts/python.exe F:/cv/Esp32Dev/ESP/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32" -D SERIAL_TOOL_ARGS="--before=default_reset --after=hard_reset write_flash @flash_args" -D WORKING_DIRECTORY="F:/WorkFlow/raspiberry/Mods/Esp32/hello_world/build" -P F:/cv/Esp32Dev/ESP/esp-idf/components/esptool_py/run_serial_tool.cmake" ninja: build stopped: subcommand failed. ninja failed with exit code 1 尝试运行python esptool.py --port COM10 write_flash_status --non-volatile 0发现无法设置flash状态 esptool.py v3.2-dev Serial port COM10 Connecting... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting... Detecting chip type... ESP32 Chip is ESP32-D0WD (revision 1) Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None Crystal is 40MHz MAC: 4c:75:25:57:0f:64 Uploading stub... Running stub... Stub running... Initial flash status: 0x0200 Setting flash status: 0x0000 After flash status: 0x0200 Hard resetting via RTS pin... 使用 python espefuse.py --chip esp32 --port COM10 summary，信息如下 Connecting...... espefuse.py v3.2-dev ---------------------------------------------------------------------------------------- Calibration fuses: BLK3_PART_RESERVE (BLOCK0): BLOCK3 partially served for ADC calibration data = False R/W (0b0) ADC_VREF (BLOCK0): Voltage reference calibration = 1114 R/W (0b00010) Config fuses: XPD_SDIO_FORCE (BLOCK0): Ignore MTDI pin (GPIO12) for VDD_SDIO on reset = False R/W (0b0) XPD_SDIO_REG (BLOCK0): If XPD_SDIO_FORCE, enable VDD_SDIO reg on reset = False R/W (0b0) XPD_SDIO_TIEH (BLOCK0): If XPD_SDIO_FORCE & XPD_SDIO_REG = 1.8V R/W (0b0) CLK8M_FREQ (BLOCK0): 8MHz clock freq override = 55 R/W (0x37) SPI_PAD_CONFIG_CLK (BLOCK0): Override SD_CLK pad (GPIO6/SPICLK) = 0 R/W (0b00000) SPI_PAD_CONFIG_Q (BLOCK0): Override SD_DATA_0 pad (GPIO7/SPIQ) = 0 R/W (0b00000) SPI_PAD_CONFIG_D (BLOCK0): Override SD_DATA_1 pad (GPIO8/SPID) = 0 R/W (0b00000) SPI_PAD_CONFIG_HD (BLOCK0): Override SD_DATA_2 pad (GPIO9/SPIHD) = 0 R/W (0b00000) SPI_PAD_CONFIG_CS0 (BLOCK0): Override SD_CMD pad (GPIO11/SPICS0) = 0 R/W (0b00000) DISABLE_SDIO_HOST (BLOCK0): Disable SDIO host = False R/W (0b0) Efuse fuses: WR_DIS (BLOCK0): Efuse write disable mask = 0 R/W (0x0000) RD_DIS (BLOCK0): Efuse read disable mask = 0 R/W (0x0) = NONE (BLK1-3 len=256 bits) R/W (0b00) KEY_STATUS (BLOCK0): Usage of efuse block 3 (reserved) = False R/W (0b0) Identity fuses: MAC (BLOCK0): Factory MAC Address = 4c:75:25:57:0f:64 (CRC 0x5b OK) R/W MAC_CRC (BLOCK0): CRC8 for factory MAC address = 91 R/W (0x5b) CHIP_VER_REV1 (BLOCK0): Silicon Revision 1 = True R/W (0b1) CHIP_VER_REV2 (BLOCK0): Silicon Revision 2 = False R/W (0b0) CHIP_VERSION (BLOCK0): Reserved for future chip versions = 2 R/W (0b10) CHIP_PACKAGE (BLOCK0): Chip package identifier = 1 R/W (0b001) MAC_VERSION (BLOCK3): Version of the MAC field = 0 R/W (0x00) Security fuses: FLASH_CRYPT_CNT (BLOCK0): Flash encryption mode counter = 0 R/W (0b0000000) UART_DOWNLOAD_DIS (BLOCK0): Disable UART download mode (ESP32 rev3 only) = False R/W (0b0) FLASH_CRYPT_CONFIG (BLOCK0): Flash encryption config (key tweak bits) = 0 R/W (0x0) CONSOLE_DEBUG_DISABLE (BLOCK0): Disable ROM BASIC interpreter fallback = True R/W (0b1) ABS_DONE_0 (BLOCK0): Secure boot V1 is enabled for bootloader image = False R/W (0b0) ABS_DONE_1 (BLOCK0): Secure boot V2 is enabled for bootloader image = False R/W (0b0) JTAG_DISABLE (BLOCK0): Disable JTAG = False R/W (0b0) DISABLE_DL_ENCRYPT (BLOCK0): Disable flash encryption in UART bootloader = False R/W (0b0) DISABLE_DL_DECRYPT (BLOCK0): Disable flash decryption in UART bootloader = False R/W (0b0) DISABLE_DL_CACHE (BLOCK0): Disable flash cache in UART bootloader = False R/W (0b0) BLOCK1 (BLOCK1): Flash encryption key = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W BLOCK2 (BLOCK2): Secure boot key = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W BLOCK3 (BLOCK3): Variable Block 3 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W Flash voltage (VDD_SDIO) determined by GPIO12 on reset (High for 1.8V, Low/NC for 3.3V). 0 本主题由 Harmony技术专家于 2024-6-20 14:26 审核通过
2024-6-20 07:14:35　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 38 个回答。邀请回答 hgimtk 该类别下有 38 个回答。邀请回答新星之火12138 该类别下有 33 个回答。邀请回答 chm5 该类别下有 32 个回答。邀请回答 zyh34997 该类别下有 32 个回答。邀请回答就好国dd 该类别下有 32 个回答。邀请回答 zaichenxi 该类别下有 31 个回答。邀请回答 heks 该类别下有 31 个回答。邀请回答四川赵赵该类别下有 29 个回答。邀请回答 flowerddd 该类别下有 29 个回答。邀请回答 muwersddg 该类别下有 29 个回答。邀请回答 caosurround 该类别下有 28 个回答。邀请回答 vinww特烦恼该类别下有 28 个回答。邀请回答星星公交站该类别下有 28 个回答。邀请回答 h1654155143.8331 该类别下有 27 个回答。邀请回答 lkjflksjfsa 该类别下有 27 个回答。邀请回答 723662364d 该类别下有 27 个回答。邀请回答 overheat 该类别下有 27 个回答。邀请回答 gvjhvbc 该类别下有 27 个回答。邀请回答安德森大该类别下有 27 个回答。邀请回答举报吴湛相关推荐 • esp32烧录flash时md5验证错误，导致不能烧录要怎么处理？ 329 • esp32如何先将OAT下来的固件进行sha256或者MD5校验，再写入相应的flash区域？ 350 • 无法写入flash，MD5检验错误：MD5 of file does not match data in flash的原因？ 985 • ESP32-Sense Kit idf4.3下载固件md5报错如何解决？ 258 • MD5计算hex文件的过程是什么 2973 • 如何使用KEIL5对MD5算法进行编译？ 1984 • 安装Labview2020版本的模块NI-SCOPE出错MD5检验错误，哪个大侠知道这个问题？ 3529 • 请问哪里可以找到MPLAB∈XC Compiler的MD5安装程序文件 1363 • 有没有人用过RTT的MD5文件校验呢？ 585 • 用flash_download_tool_3.9.2擦除esp32提示错误2或5的原因？ 463 1个回答

答案对人有帮助，有参考价值 0 以下是一些建议来解决这个问题： 1. 确保您使用的是正确的烧录工具和固件。请检查您的烧录器和固件是否与您的ESP32-WROOM-32D模块兼容。 2. 检查您的烧录器连接是否稳定。如果连接不稳定，可能会导致数据传输错误。 3. 尝试使用不同的烧录速度。在某些情况下，降低烧录速度可以提高烧录成功率。 4. 确保您的ESP32模块没有硬件问题。如果模块存在硬件故障，可能会导致烧录失败。 5. 尝试使用其他版本的ESP-IDF。您当前使用的是4.3.1版本，可以尝试升级到最新版本或降级到其他稳定版本。 6. 在烧录之前，确保您的ESP32模块已经完全擦除。可以使用以下命令来擦除整个Flash： ``` esptool.py --port COM10 erase_flash ``` 7. 在烧录过程中，确保没有其他程序干扰。关闭可能影响烧录的程序，如杀毒软件或其他串口通信程序。

2024-6-20 17:24:44 评论举报李星童