Page 2 of 2

Re: [SOLVED] rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT) flash read err, 1000

Posted: Fri Feb 12, 2021 6:09 am
by segankuz
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371

I am getting this error in my esp32 devkit v1
How to solve it?
I am using arduino IDE for programming the esp32.
This error went away after I changed esptool.py params to start writing the flash at 0x1000:
A:\> esptool.py.exe --port COM7 --baud 512000 write_flash --flash_size=detect 0x1000 .\Downloads\esp32-idf3-20210202-v1.14.bin

Re: [SOLVED] rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT) flash read err, 1000

Posted: Sat Jul 17, 2021 11:17 am
by redradist
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371

I am getting this error in my esp32 devkit v1
How to solve it?
I am using arduino IDE for programming the esp32.
This error went away after I changed esptool.py params to start writing the flash at 0x1000:
A:\> esptool.py.exe --port COM7 --baud 512000 write_flash --flash_size=detect 0x1000 .\Downloads\esp32-idf3-20210202-v1.14.bin
Did not quite get where you get `.\Downloads\esp32-idf3-20210202-v1.14.bin` file ?
I've similar issue https://www.esp32.com/viewtopic.php?f=1 ... 271#p80271, but cannot figure out how to disable such behavior ...

Re: [SOLVED] rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT) flash read err, 1000

Posted: Sat Dec 25, 2021 8:29 pm
by WalnutYatzi
Was anyone able to solve the above issue?

Re: [SOLVED] rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT) flash read err, 1000

Posted: Mon Dec 27, 2021 3:35 am
by LJH
Which flash do you use? I notice that boot number is 33 which means VDD_SDIO is 1.8 V, could you make sure this level corresponds to your flash?

Re: [SOLVED] rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT) flash read err, 1000

Posted: Mon Oct 14, 2024 2:03 pm
by rocotocloc
I had this problem but it was just a corrupt state after a bad flashing process. I reflashed and it was fixed.