Hi ,
My esp32 module has started throwing this error :
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)<\r><\n>
flash read err, 1000<\r><\n>
Falling back to built-in command interpreter.<\r><\n>
OK<\r><\n>
>ets Jun 8 2016 00:22:57<\r><\n>
Nothing connected to any of the special pins - the unit is just powered via the usb connector.
It just so happened that it only happened after I erased the whole flash using the "make erase_flash" and loaded the default no ota partition table. Before that it was working fine.
Is this h/w failure ? Ive tried various things like "make clean" "make erase_flash flash" etc
flash read err, 1000
Re: flash read err, 1000
Not set to QIO mode by mistake? Didn't enable flash encryption by mistake? Nothing connected to gpio 6-12?
Re: flash read err, 1000
To add to WiFive's comment, this error implies that the ROM bootloader can't find the software bootloader at offset 0x1000.
This should be fixed via "make flash". The only time it won't is if flash encryption is accidentally enabled, or if secure boot is enabled (because this option means "make flash" won't flash the bootloader).
What's the full output of "make flash" when you run this? Do you see the bootloader being flashed at offset 0x1000?
It could also imply a power problem, if the SPI flash chip is browning out (either because MTDI pin has selected 1.8V mode, or because the 3.3V rail is drooping.)
Angus
This should be fixed via "make flash". The only time it won't is if flash encryption is accidentally enabled, or if secure boot is enabled (because this option means "make flash" won't flash the bootloader).
What's the full output of "make flash" when you run this? Do you see the bootloader being flashed at offset 0x1000?
It could also imply a power problem, if the SPI flash chip is browning out (either because MTDI pin has selected 1.8V mode, or because the 3.3V rail is drooping.)
Angus
Re: flash read err, 1000
Thanks,
Attached is the make output - dont see anything going in at 0x1000 , but I have changed anything in my menuconfig ... what should I be looking for - How is the encryption enabled?
Attached is the make output - dont see anything going in at 0x1000 , but I have changed anything in my menuconfig ... what should I be looking for - How is the encryption enabled?
Flashing binaries to serial port COM3 (app at offset 0x10000)...
esptool.py v2.0-beta1
Connecting....
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Attaching SPI flash...
Configuring flash size...
Auto-detected Flash size: 4MB
Wrote 524288 bytes at 0x00010000 in 8.3 seconds (505.4 kbit/s)...
Hash of data verified.
Wrote 16384 bytes at 0x00008000 in 0.2 seconds (548.4 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting...
Re: flash read err, 1000
Im really sorry to waste your time , I know whats happening. I deleted the bootloader component from IDF and had it in my own project. But not in a different project .....
Re: flash read err, 1000
OK, glad you figured that out!imtiaz wrote:Im really sorry to waste your time , I know whats happening. I deleted the bootloader component from IDF and had it in my own project. But not in a different project .....
For the record, you shouldn't need to delete the bootloader component inside IDF. If a component of the same name exists in the components directory of the project, it will override the one in IDF. (At least, this is the design - if you're finding that you have to delete the old component then this is a bug.)
Angus
Re: flash read err, 1000
Hi Angus ,
No the component override works perfectly - I just deleted it to test .
Thanks
Imtiaz
No the component override works perfectly - I just deleted it to test .
Thanks
Imtiaz
Re: flash read err, 1000
Hi,
I experiment the same issue.Using idf v2.0 with a WROOM-32 module.
Here are the logs when waking up from deep sleep:
I have a data set to RTC memory, and it gets reinit each time the device is woke up...
I checked, and I don't have encryption activated...
Any idea on how to fix this issue?
Cheers,
Eric T.
I experiment the same issue.Using idf v2.0 with a WROOM-32 module.
Here are the logs when waking up from deep sleep:
Code: Select all
Going to DEEP_SLEEP, good night
D (10746) deepsleep: RTC_PERIPH: ON, RTC_SLOW_MEM: ON, RTC_FAST_MEM: ON
ets Jun 8 2016 00:22:57
rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
Falling back to built-in command interpreter.
OK
>ets Jun 8 2016 00:22:57
rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:4836
load:0x40078000,len:8648
load:0x40080000,len:252
entry 0x40080034
I (44) boot: ESP-IDF v2.0 2nd stage bootloader
I (45) boot: compile time 16:51:38
I (45) boot: Enabling RNG early entropy source...
D (61) esp_image: reading image header @ 0x1000
D (75) bootloader_flash: mmu set block paddr=0x00000000 (was 0xffffffff)
D (96) boot: magic e9
D (103) boot: segments 04
D (111) boot: spi_mode 02
D (119) boot: spi_speed 00
D (128) boot: spi_size 02
I (136) boot: SPI Speed : 40MHz
I (149) boot: SPI Mode : DIO
I (162) boot: SPI Flash Size : 4MB
D (174) bootloader_flash: mmu set paddr=00000000 count=1
D (191) boot: mapped partition table 0x8000 at 0x3f408000
D (208) flash_parts: partition table verified, 3 entries
I (224) boot: Partition Table:
I checked, and I don't have encryption activated...
Any idea on how to fix this issue?
Cheers,
Eric T.
Re: flash read err, 1000
Try setting "Extra delay in deep sleep wake stub" option in menuconfig (under Component config > ESP32 specific) to some higher value, like 500us.
Who is online
Users browsing this forum: Bing [Bot] and 294 guests