flash read err, 1000 on ESP32-WROVER

hopkinskong
Posts: 3
Joined: Sat Oct 28, 2017 4:10 pm

flash read err, 1000 on ESP32-WROVER

Postby hopkinskong » Sat Oct 28, 2017 4:17 pm

Hi,

I am using ESP32-WROVER module, for some reason, it suddenly stopped working. When on manual reset:

Code: Select all

$ make monitor
MONITOR
--- idf_monitor on COM7 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
And it goes on forever.

When I try to flash:

Code: Select all

$ make flash
Flashing binaries to serial port COM7 (app at offset 0x10000)...
esptool.py v2.1
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Compressed 18320 bytes to 10813...
Wrote 18320 bytes (10813 compressed) at 0x00001000 in 1.0 seconds (effective 153.6 kbit/s)...

A fatal error occurred: Timed out waiting for packet header
make: *** [/home/xxx/esp/esp-idf/components/esptool_py/Makefile.projbuild:55: flash] Error 2
It seems that the ESP32 does not recognize the flash chip anymore. Is there any solution, or I need to replace the whole module?

BTW,
BOTH Secure boot in bootloader and flash encryption in boot are off in menuconfig;
Flash SPI mode is DIO in menuconfig

Thanks.

hopkinskong
Posts: 3
Joined: Sat Oct 28, 2017 4:10 pm

Re: flash read err, 1000 on ESP32-WROVER

Postby hopkinskong » Sun Oct 29, 2017 6:40 pm

Solved.

I recommend anyone encountering the same issue check:

1. GPIO12 (MTDI) must be pulled up to power SDIO with 1.8V, it is already done internally in ESP32-WROVER. However if your board is pulling down that pin, it will power the internal SDIO LDO with 3.3V which will damage the PSRAM/SPI FLASH. Luckily my board left that pin floating.

2. This is my issue: Pin 20 (CLK) and Pin 21 (SD0) shorted, that makes SPI flash is not working, luckily it isn't shorted to the 3V3 rail, or I am really need to replace the module.

anandvilayil
Posts: 22
Joined: Mon Apr 30, 2018 12:14 pm

Re: flash read err, 1000 on ESP32-WROVER

Postby anandvilayil » Wed Jun 13, 2018 8:55 am

hii all,

i am also facing this similar problem. exactly what are the reason for esp flash getting corrupted ?.

Kiranoday
Posts: 1
Joined: Wed Jun 13, 2018 10:18 am

Re: flash read err, 1000 on ESP32-WROVER

Postby Kiranoday » Wed Jun 13, 2018 10:59 am

I am also facing the same issue...

hugonbs
Posts: 2
Joined: Wed Jan 10, 2018 11:52 am

Re: flash read err, 1000 on ESP32-WROVER

Postby hugonbs » Mon Sep 17, 2018 9:59 am

I'm experiencing the same issue, but only some times when the module are recovering from deep sleep (the average is +/- 1/30000)
This is the error message:
rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:672
ho 0 tail 12 room 4
load:0x40078000,len:0
load:0x40078000,len:10320
entry 0x40078ac0
Can anyone help with this issue?

cvargcal
Posts: 12
Joined: Sat Sep 08, 2018 2:06 pm

Re: flash read err, 1000 on ESP32-WROVER

Postby cvargcal » Thu Nov 01, 2018 12:54 am

Hi,I have the same problem... What I have bad?

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371

I tried put resistor 5K to GND on IO2 but same
Not let flashing...
I used a normal USB/TTL wire
Image


LD build/hello-world.elf
esptool.py v2.5.1
Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000 )...
esptool.py v2.5.1
Serial port /dev/ttyUSB0
Connecting........_____....._
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
MAC: 3c:71:bf:16:0f:3c
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Flash params set to 0x0220
Compressed 20928 bytes to 12400...

A fatal error occurred: Timed out waiting for packet content
/home/ubuntu/esp/esp-idf/components/esptool_py/Makefile.projbuild:62: recipe for target 'flash' failed
make: *** [flash] Error 2

ESP_Angus
Posts: 2344
Joined: Sun May 08, 2016 4:11 am

Re: flash read err, 1000 on ESP32-WROVER

Postby ESP_Angus » Thu Nov 01, 2018 2:26 am

Hi cvargcal,

The line "Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB" indicates that communication with the SPI flash chip inside the WROOM32 is failing.

It looks like you have external peripherals connected to a number of the SPI flash bus lines. GPIOs 6-11 should not be used for any other purpose, unless you're very careful about coexisting with the SPI flash chip. Check ESP32-WROOM32 datasheet section 4 for more details.

Angus

cvargcal
Posts: 12
Joined: Sat Sep 08, 2018 2:06 pm

Re: flash read err, 1000 on ESP32-WROVER

Postby cvargcal » Thu Nov 01, 2018 2:35 am

Thanks you for your answer.... I saw the PIN20 (CLK) i used for ADC... so I did cut the wire and now show this


rst:0x10 (RTCWDT_RTC_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:3480
load:0x40078000,len:7804
ho 0 tail 12 room 4
load:0x40080000,len:252
entry 0x40080034
[0;32mI (46) boot: ESP-IDF v2.0-3-gbef9896 2nd stage bootloader[0m
[0;32mI (46) boot: compile time 05:59:45[0m
[0;32mI (47) boot: Enabling RNG early entropy source...[0m
[0;32mI (65) boot: SPI Speed : 40MHz[0m
[0;32mI (78) boot: SPI Mode : DIO[0m
[0;32mI (90) boot: SPI Flash Size : 4MB[0m
[0;32mI (103) boot: Partition Table:[0m
[0;32mI (114) boot: ## Label Usage Type ST Offset Length[0m
[0;32mI (137) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
[0;32mI (160) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
[0;32mI (183) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
[0;32mI (206) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
[0;32mI (230) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
[0;32mI (253) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
[0;32mI (276) boot: End of partition table[0m
[0;32mI (289) boot: Disabling RNG early entropy source...[0m
[0;32mI (306) boot: Loading app partition at offset 00100000[0m
[0;32mI (1482) boot: segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
[0;32mI (1482) boot: segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map[0m
[0;32mI (1499) boot: segment 2: paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load[0m
[0;32mI (1529) boot: segment 3: paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
[0;32mI (1553) boot: segment 4: paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load[0m
[0;32mI (1631) boot: segment 5: paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load[0m
[0;32mI (1632) boot: segment 6: paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648) [0m
[0;32mI (1649) boot: segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map[0m
[0;32mI (1676) heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
[0;32mI (1699) heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM[0m
[0;32mI (1720) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
[0;32mI (1741) heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM[0m
[0;32mI (1762) cpu_start: Pro cpu up.[0m
[0;32mI (1774) cpu_start: Single core mode[0m
[0;32mI (1787) cpu_start: Pro cpu start user code[0m
[0;32mI (1847) cpu_start: Starting scheduler on PRO CPU.[0m
[0;32mI (2104) uart: queue free spaces: 10[0m
Bin version:0.10.0
I (2106) wifi: wifi firmware version: c604573
I (2106) wifi: config NVS flash: enabled
I (2107) wifi: config nano formating: disabled
I (2115) wifi: Init dynamic tx buffer num: 32
I (2116) wifi: wifi driver task: 3ffc4e24, prio:23, stack:3584
I (2121) wifi: Init static rx buffer num: 10
I (2125) wifi: Init dynamic rx buffer num: 0
I (2129) wifi: Init rx ampdu len mblock:7
I (2133) wifi: Init lldesc rx ampdu entry mblock:4
I (2137) wifi: wifi power manager task: 0x3ffca1cc prio: 21 stack: 2560
I (2144) wifi: wifi timer task: 3ffcb24c, prio:22, stack:3584
[0;31mE (2149) phy_init: PHY data partition validated[0m
[0;32mI (2171) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
I (2171) wifi: mode : softAP (3c:71:bf:16:0f:3d)
I (2174) wifi: mode : sta (3c:71:bf:16:0f:3c) + softAP (3c:71:bf:16:0f:3d)
I (2178) wifi: mode : softAP (3c:71:bf:16:0f:3d)


But still no let write the software...


Edit

I see... I can not use that pins... so the UART1 can not used?
I cut all wires to 6-11 and now show this


Guru Meditation Error of type LoadProhibited occurred on core 0. Exception was unhandled.
Register dump:
PC : 0x40108a22ets 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:3480
load:0x40078000,len:7804
ho 0 tail 12 room 4
load:0x40080000,len:252
entry 0x40080034
I (280) boot: ESP-IDF v2.0-3-gbef9896 2nd stage bootloader
I (281) boot: compile time 05:59:45
I (281) boot: Enabling RNG early entropy source...
I (300) boot: SPI Speed : 40MHz
I (313) boot: SPI Mode : DIO
I (326) boot: SPI Flash Size : 4MB
I (339) boot: Partition Table:
I (350) boot: ## Label Usage Type ST Offset Length
I (373) boot: 0 phy_init RF data 01 01 0000f000 00001000
I (396) boot: 1 otadata OTA data 01 00 00010000 00002000
I (419) boot: 2 nvs WiFi data 01 02 00012000 0000e000
I (442) boot: 3 at_customize unknown 40 00 00020000 000e0000
I (466) boot: 4 ota_0 OTA app 00 10 00100000 00180000
I (489) boot: 5 ota_1 OTA app 00 11 00280000 00180000
I (512) boot: End of partition table
I (525) boot: Disabling RNG early entropy source...
I (542) boot: Loading app partition at offset 00100000
I (1718) boot: segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1718) boot: segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map
I (1735) boot: segment 2: paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load
I (1765) boot: segment 3: paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load
I (1789) boot: segment 4: paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load
I (1867) boot: segment 5: paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load
I (1868) boot: segment 6: paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648)
I (1885) boot: segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map
I (1912) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1935) heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM
I (1956) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM
I (1977) heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM
I (1998) cpu_start: Pro cpu up.
I (2010) cpu_start: Single core mode
I (2023) cpu_start: Pro cpu start user code

ESP_Angus
Posts: 2344
Joined: Sun May 08, 2016 4:11 am

Re: flash read err, 1000 on ESP32-WROVER

Postby ESP_Angus » Thu Nov 01, 2018 4:07 am

I see... I can not use that pins... so the UART1 can not used?
You can use the GPIO Matrix to remap UART1 to any other GPIOs which are unused.
I cut all wires to 6-11 and now show this
Looks like it's mostly working?

cvargcal
Posts: 12
Joined: Sat Sep 08, 2018 2:06 pm

Re: flash read err, 1000 on ESP32-WROVER

Postby cvargcal » Thu Nov 01, 2018 5:06 am

ESP_Angus wrote:
I see... I can not use that pins... so the UART1 can not used?
You can use the GPIO Matrix to remap UART1 to any other GPIOs which are unused.
I cut all wires to 6-11 and now show this
Looks like it's mostly working?
thanks , now work fine and let me flashing... but its rare.. I have presed reset and boot sw for can flashing... Well I have fixed my PCB .

Who is online

Users browsing this forum: Google [Bot] and 304 guests