ESP32 Forum

HW: ESP32-WROVER-KIT
ESP_IDF GIT VERSION: 43b6c76 or greater

after make micropython and deploy, the system cannot boot success and throw a exception:

Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x3e (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:0x3e (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:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4664
load:0x40078000,len:1020
load:0x40080000,len:13072
entry 0x40083254
Fatal exception (28): LoadProhibited
epc1=0x4008067e, epc2=0x00000000, epc3=0x00000000, excvaddr=0xcea1a570, depc=0x00000000

it seems that the bootloader expand feature cause the issue. can someone give me some hints about this issue?

rst:0x1 (POWERON_RESET),boot:0x3e (SPI_FAST_FLASH_BOOT)
flash read err, 1000

why flash read err when reset. since there is no any source code here, need expert to help!!

"flash read err, 1000" means that the bootloader.bin flashed at offset 0x1000 is not a valid binary image to boot from.

Some summary information on boot messages can be found here: https://github.com/espressif/esptool/wi ... de-message

Because Micropython uses a different build system to ESP-IDF, updating can require some care to bring over changes from IDF builds into Micropython. You may need to talk to the Micropython developers about any particular issues you are seeing.

(However, if it's failing to either build or flash a valid bootloader.bin, the problem may be a quite simple one which is easy for you to fix.)

this issue is caused by bootloader ld changes which cause bootloader mapping issue for micropython. after create custom bootloader ld file, this issue is solved.