ESP32 Forum

Posted: **Sat Oct 26, 2019 8:47 am**

I enabled secure boot and encrypted flash. The following error occurred during the first boot. How can I solve this problem?

Code: Select all

rst:0x1 (POWERON_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:2
load:0x3fff0018,len:4
load:0x3fff001c,len:7792
ho 0 tail 12 room 4
load:0x40078000,len:18136
ho 0 tail 12 room 4
load:0x40080400,len:6272
entry 0x40080710
E (29672) esp_image: image at 0x210000 has invalid magic byte
W (29673) esp_image: image at 0x210000 has invalid SPI mode 61
W (29674) esp_image: image at 0x210000 has invalid SPI size 15
ets Jun  8 2016 00:22:57

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:2
load:0x3fff0018,len:4
load:0x3fff001c,len:7792
ho 0 tail 12 room 4
load:0x40078000,len:18136
ho 0 tail 12 room 4
load:0x40080400,len:6272
entry 0x40080710
I (807) cpu_start: Pro cpu up.
I (807) cpu_start: Application information:
I (807) cpu_start: Project name:     native_ota
I (810) cpu_start: App version:      0.0.0
I (814) cpu_start: Compile time:     Oct 26 2019 16:16:40
I (821) cpu_start: ELF file SHA256:  6429ca7c09016e24...
I (827) cpu_start: ESP-IDF:          v4.0-beta1-dirty
I (832) cpu_start: Starting app cpu, entry point is 0x400812fc
0x400812fc: call_start_cpu1 at C:/esp-idf-v4.0-beta1/components/esp32/cpu_start.c:281

I (839) cpu_start: Flash encryption mode is RELEASE
I (0) cpu_start: App cpu up.
I (848) heap_init: Initializing. RAM available for dynamic allocation:
I (855) heap_init: At 3FFAE6E0 len 0000F480 (61 KiB): DRAM
I (861) heap_init: At 3FFC7148 len 00018EB8 (99 KiB): DRAM
I (867) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (874) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (880) heap_init: At 4009214C len 0000DEB4 (55 KiB): IRAM
I (886) cpu_start: Pro cpu start user code
I (905) spi_flash: detected chip: generic
I (905) spi_flash: flash io: dio
I (906) cpu_start: Chip Revision: 1
Guru Meditation Error: Core  0 panic'ed (LoadStoreError). Exception was unhandled.
Core 0 register dump:
PC      : 0x40157d3c  PS      : 0x00060130  A0      : 0x800812b6  A1      : 0x3ffe3b50
0x40157d3c: vprintf at /builds/idf/crosstool-NG/.build/HOST-i686-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/vprintf.c:30

A2      : 0x40157d3c  A3      : 0x3ffc194c  A4      : 0x3f40055c  A5      : 0x0000001f
0x40157d3c: vprintf at /builds/idf/crosstool-NG/.build/HOST-i686-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/vprintf.c:30

A6      : 0x00000001  A7      : 0x00000005  A8      : 0x800825d4  A9      : 0x3ffe3b10
A10     : 0x3f40055c  A11     : 0x3ffe3b80  A12     : 0x3ffe3b60  A13     : 0x0000000c
A14     : 0x00000000  A15     : 0x00000000  SAR     : 0x00000017  EXCCAUSE: 0x00000003
EXCVADDR: 0x4015811c  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff
0x4015811c: _dtoa_r at /builds/idf/crosstool-NG/.build/HOST-i686-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdlib/dtoa.c:360


ELF file SHA256: 890a18b63bd4cbd447418b3e97d9cac4f01d7dabbbfb51a951182a60f83cdf8f

Backtrace: 0x40157d39:0x3ffe3b50 0x400812b3:0x3ffe3ba0 0x4008155d:0x3ffe3bf0 0x4007931b:0x3ffe3c30 |<-CORRUPTED
0x40157d39: __sbprintf at vfprintf.c:?

0x400812b3: start_cpu0_default at C:/esp-idf-v4.0-beta1/components/esp32/cpu_start.c:461 (discriminator 9)

0x4008155d: call_start_cpu0 at C:/esp-idf-v4.0-beta1/components/esp32/cpu_start.c:269

Posted: **Sun Oct 27, 2019 11:28 am**

Hello,

I think issue is in between bootloader and application firmware. As per error it seems to be like bootloader has been started and it tries to up application image in which there are some issues.

Did you check same bootloader and application image in which you haven't enabked secure boot and encrypted flash? So that you can have idea to dig more for issue resolution.

Posted: **Sun Oct 27, 2019 1:01 pm**

Ritesh wrote: ↑
Sun Oct 27, 2019 11:28 am
Hello,

I think issue is in between bootloader and application firmware. As per error it seems to be like bootloader has been started and it tries to up application image in which there are some issues.

Did you check same bootloader and application image in which you haven't enabked secure boot and encrypted flash? So that you can have idea to dig more for issue resolution.

Thanks, Bootloader and APP can start normally without enabling secure boot and flash encrypt.

Posted: **Wed Oct 30, 2019 4:30 am**

shawn2019 wrote: ↑
Sun Oct 27, 2019 1:01 pm

Ritesh wrote: ↑
Sun Oct 27, 2019 11:28 am
Hello,

I think issue is in between bootloader and application firmware. As per error it seems to be like bootloader has been started and it tries to up application image in which there are some issues.

Did you check same bootloader and application image in which you haven't enabked secure boot and encrypted flash? So that you can have idea to dig more for issue resolution.
Thanks, Bootloader and APP can start normally without enabling secure boot and flash encrypt.

So, What can be your next step to enable secure boot and flash encryption for same to move further for that? It seems like there might be some issues while configuring secure boot and flash encryption.

ESP32 Forum

Bootloader crash, help me pls!

Bootloader crash, help me pls!

Re: Bootloader crash, help me pls!

Re: Bootloader crash, help me pls!

Re: Bootloader crash, help me pls!