[ GPIO12/MTDI selects the SPI flash voltage on reset - LOW (default) is 3.3V, HIGH is 1.8V. This is overrideable via EFUSE as well, there will be a command line tool in esp-idf soon which can set this override. ESP32S modules appear to ship with a 3.3V SPI flash chip, however it must almost work at...

Aha! I'm glad you sorted this out. Do you mean it entered the ROM console while it was supposed to be flashing, or at some later time? It entered the ROM Console first and I tried to flash it then during the boot sequence. 8-( I suppose the boot priority should be program-mode first with GPIO0-Low,...

Hi derekali, The status bits that are being reported are QIE, LB2, LB3. (You can see in section 7 of the flash datasheet .) According to the datasheet, none of these status bits should be preventing writing to the flash. Also, the fact you get a different md5 each time implies that different data i...

Hi dereklai, Thanks for providing those details. A couple of things that should help: You don't need the bugfix branch of esptool.py any more, in fact that branch is out of date. I should have deleted it and removed the link from the post, my mistake. If you have the current esp-idf master branch t...

For each 'make flash', there is a different Flash md5. What's wrong? Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000)... esptool.py v2.0-dev Connecting... Uploading stub... Running stub... Stub running... Changing baud rate to 921600 Changed. Attaching SPI flash... Configuring f...

Hi dereklai, What's the output of 'esptool.py flash_id'? Thanks, Angus ~/esp/esp-idf/components/esptool_py/esptool$ ./esptool.py --port /dev/ttyUSB0 flash_id esptool.py v2.0-dev Connecting... Detecting chip type... ESP32 Uploading stub... Running stub... Stub running... Manufacturer: ef Device: 4016

The fix for this bug was merged into esp-idf yesterday, since revision f988dc9. Thanks everyone for the help diagnosing the issue and testing the fix. I have the MD5 not match problem today with two ESP32s boards. They can "read_flash_status" to be 0x3300. And after write_flash_status --nonvatile 0...