Boot loop after flashing esp32

#1

If you are asking a question, please follow this template:

  1. My goal is: Configure WiFi

  2. My actions are: after following the instruction in quickstart and executing the mos flash command my esp32 get this message in an infinite loop

  3. The result I see is:

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:4
load:0x3fff0034,len:6868
load:0x40078000,len:13428
ho 0 tail 12 room 4
load:0x40080400,len:5064
entry 0x400806d4
e[0;32mI (60) boot: ESP-IDF 4.2-r1 2nd stage bootloadere[0m
e[0;32mI (60) boot: compile time 13:39:07e[0m
e[0;32mI (60) boot: chip revision: 1e[0m
e[0;32mI (64) boot_comm: chip revision: 1, min. bootloader chip revision: 0e[0m
e[0;32mI (71) qio_mode: Enabling QIO for flash chip WinBonde[0m
e[0;32mI (76) boot.esp32: SPI Speed      : 80MHze[0m
e[0;32mI (81) boot.esp32: SPI Mode       : QIOe[0m
e[0;32mI (85) boot.esp32: SPI Flash Size : 4MBe[0m
e[0;32mI (90) boot: Enabling RNG early entropy source...e[0m
e[0;32mI (95) boot: Partition Table:e[0m
e[0;32mI (99) boot: ## Label            Usage          Type ST Offset   Lengthe[0m
e[0;32mI (106) boot:  0 nvs              WiFi data        01 02 00009000 00004000 00000000e[0m
e[0;32mI (115) boot:  1 otadata          OTA data         01 00 0000d000 00002000 00000000e[0m
e[0;32mI (123) boot:  2 app_0            OTA app          00 10 00010000 00180000 00000000e[0m
e[0;32mI (131) boot:  3 fs_0             FS               01 82 00190000 00040000 00000000e[0m
e[0;32mI (140) boot:  4 app_1            OTA app          00 11 001d0000 00180000 00000000e[0m
e[0;32mI (148) boot:  5 fs_1             FS               01 82 00350000 00040000 00000000e[0m
e[0;32mI (156) boot: End of partition tablee[0m
e[0;32mI (161) boot: OTA data 0: seq 0x00000001, st 0x10, CRC 0x157a2b85, valid? 1e[0m
e[0;32mI (168) boot: OTA data 1: seq 0x00000000, st 0x00, CRC 0x00000000, valid? 0e[0m
e[0;32mI (176) boot_comm: chip revision: 1, min. application chip revision: 0e[0m
e[0;32mI (183) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x442d8 (279256) mape[0m
e[0;32mI (273) esp_image: segment 1: paddr=0x00054300 vaddr=0x3ffbdb60 size=0x0394c ( 14668) loade[0m
e[0;32mI (278) esp_image: segment 2: paddr=0x00057c54 vaddr=0x40080000 size=0x00400 (  1024) loade[0m
e[0;32mI (280) esp_image: segment 3: paddr=0x0005805c vaddr=0x40080400 size=0x07fbc ( 32700) loade[0m
e[0;32mI (301) esp_image: segment 4: paddr=0x00060020 vaddr=0x400d0020 size=0x1192a4 (1151652) mape[0m
e[0;32mI (636) esp_image: segment 5: paddr=0x001792cc vaddr=0x400883bc size=0x16300 ( 90880) loade[0m
e[0;32mI (668) esp_image: segment 6: paddr=0x0018f5d4 vaddr=0x400c0000 size=0x00034 (    52) loade[0m
e[0;31mE (669) esp_image: Checksum failed. Calculated 0x3d read 0x3ce[0m
e[0;31mE (673) boot: OTA app partition slot 0 is not bootablee[0m
e[0;31mE (678) esp_image: image at 0x1d0000 has invalid magic bytee[0m
e[0;33mW (685) esp_image: image at 0x1d0000 has invalid SPI mode 255e[0m
e[0;33mW (691) esp_image: image at 0x1d0000 has invalid SPI size 15e[0m
e[0;31mE (697) boot: OTA app partition slot 1 is not bootablee[0m
e[0;31mE (703) boot: No bootable app partitions in the partition tablee[0m
ets Jun  8 2016 00:22:57
  1. My expectation & question is: how i can solve this probleme
#2

That doesn’t look good.
What exactly are you doing, because it is not properly flashing the right chip with the right code

1 Like
#3

i follow the insctuction in this link :
https://mongoose-os.com/docs/mongoose-os/quickstart/setup.md

i Use esp32 joy - it model based on esp 32 wroom
and in mos i choose esp32 board
the boot loop appear after flashing commande

#4

@Achraf_bouassria I’m wondering if you resolved thi? It looks like you have a Winbond SPI flash chip in there somewhere, is this right?