Flash Erase completed but without effect

[Pommesfreak2]

Hello fellow programmers, when I tried to upload a new programm to my ESP32 WROOM DA-Module via Arduino-IDE I did receive following error:

Code: Select all

Error while writing flash: MD5 of file does not match data in flash!

Found a possible solution: erasing the ESP's Flash via esptool.
So I installed esptool tried many different commands like

Code: Select all

python -m esptool --chip esp32 erase_flash

All of them detected the boards and seems to work as they give me following like code in response:

Code: Select all

Connecting.........
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c0:49:ef:cd:bd:b8
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 0.0s
Hard resetting via RTS pin...

Even though it seems to worked the Error when trying to write the flash keeps the same.
Furthermore the programm that was on the flash before the erase is still there. So there was no real erase.

I also tried an online version: https://espressif.github.io/esptool-js/

It's interesting that erasing the flash is that fast - most videos I saw had a time about 2 seconds. Maybe a part of the problem.

I'm using a Windows 10 64x PC and a ESP32 Wroom-Da-Module. Please tell me if you need something in addition to these information, I'm not very experienced in things like these

[Sprite]

This tends to be an issue with GPIO12 connected to the wrong voltage level. Do you have that pin connected to anything?

[Pommesfreak2]

This tends to be an issue with GPIO12 connected to the wrong voltage level. Do you have that pin connected to anything?

No, GPIO12 is not connected to anything.

[corz.org]

How is this a "Showcase"?

[Sprite]

How is this a "Showcase"?

It's not, moving it to another forums. Thanks for noticing, but next time please report the topic rather than replying, it's a cleaner solution.

[rsimpsonbusa]

I had that problem with a module. I actually changed the internal flash and that error message disappeared. just my 5 cents