ESP32 Forum

Hi, we developed some years ago a product based on ESP32-WROOM_32D, initially using ESP-IDF 4.0.1. It has been working successfully until now. We have initiated a migration process aimed at ESP-IDF 4.4.3 (last stable release). After changing everything related to tcpip_adapter and solving an issue due to a call to adc_gpio_init (now deprecated), I was able to successfully build the project. However, after flashing, the board won´t start and we are receiving the following error:

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:0x3fff00b8,len:2316
ho 0 tail 12 room 4
load:0x40078000,len:17668
load:0x40080400,len:3272
entry 0x40080608

Could you please help me?

Thanks

I tried to go step by step so I downgraded to esp-idf 4.1 but it does not work either. The error is the following:

rst:0x10 (RTCWDT_RTC_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:0x3fff0030,len:4
load:0x3fff0034,len:1812
load:0x40078000,len:12436
ho 0 tail 12 room 4
load:0x40080400,len:3360
entry 0x4008060c
ets Jun 8 2016 00:22:57

I will keep on replying to myself

I connected the debug serial port and this is what I see. As far as I understand it seems I am using part of the reserved memory? How is that possible? Does anything change between 4.0.1 and 4.1? By the way, I am using flash encyrption and this is my partition table:

nvs, data, nvs, 0x9000, 0x4000, encrypted
otadata, data, ota, 0xd000, 0x2000, encrypted
phy_init, data, phy, 0xf000, 0x1000, encrypted
ota_0, app, ota_0, 0x10000, 1536K,
ota_1, app, ota_1, 0x190000, 1536K,
certs, data, 255, 0x310000, 64K, encrypted
nvs_key, data, nvs_keys, 0x320000, 0x1000, encrypted

(543) cpu_start: Pro cpu up.
I (543) cpu_start: Application information:
I (543) cpu_start: Project name: Conn_Board
I (574) cpu_start: App version: 2.2
I (629) cpu_start: Compile time: Dec 1 2022 13:50:34
I (702) cpu_start: ELF file SHA256: b0a602820b525504...
I (774) cpu_start: ESP-IDF: v4.1
I (830) cpu_start: Starting app cpu, entry point is 0x400813c0
I (0) cpu_start: App cpu up.
V (951) memory_layout: reserved range is 0x3f4429f8 - 0x3f442a20
D (1024) memory_layout: Checking 7 reserved memory ranges:
D (1091) memory_layout: Reserved memory range 0x3ffae000 - 0x3ffae6e0
D (1169) memory_layout: Reserved memory range 0x3ffb0000 - 0x3ffbda58
D (1247) memory_layout: Reserved memory range 0x3ffe0000 - 0x3ffe0440
D (1325) memory_layout: Reserved memory range 0x3ffe3f20 - 0x3ffe4350
D (1403) memory_layout: Reserved memory range 0x40070000 - 0x40078000
D (1481) memory_layout: Reserved memory range 0x40078000 - 0x40080000
D (1559) memory_layout: Reserved memory range 0x40080000 - 0x400968ac
D (1637) memory_layout: Building list of available memory regions:
V (1712) memory_layout: Examining memory region 0x3ffae000 - 0x3ffb0000
V (1793) memory_layout: Start of region 0x3ffae000 - 0x3ffb0000 overlaps reserved 0x3ffae000 - 0x3ffae6e0
D (1908) memory_layout: Available memory region 0x3ffae6e0 - 0x3ffb0000
V (1988) memory_layout: Examining memory region 0x3ffb0000 - 0x3ffb8000
V (2069) memory_layout: Region 0x3ffb0000 - 0x3ffb8000 inside of reserved 0x3ffb0000 - 0x3ffbda58
V (2176) memory_layout: Examining memory region 0x3ffb8000 - 0x3ffc0000
V (2256) memory_layout: Start of region 0x3ffb8000 - 0x3ffc0000 overlaps reserved 0x3ffb0000 - 0x3ffbda58
D (2372) memory_layout: Available memory region 0x3ffbda58 - 0x3ffc0000

I don't see an actual "error" message in any of those outputs. Is the displayed app version correct? Is that all that is displayed? What happens afterwards? Does the ESP32 just hang, or does it continue rebooting and displaying those same messages? Your partition table appears to be Ok, as far as I can tell. Maybe the encryption is causing an issue in the upgrade (?).

mbratch wrote: ↑

Sun Dec 04, 2022 1:58 am

I don't see an actual "error" message in any of those outputs. Is the displayed app version correct? Is that all that is displayed? What happens afterwards? Does the ESP32 just hang, or does it continue rebooting and displaying those same messages? Your partition table appears to be Ok, as far as I can tell. Maybe the encryption is causing an issue in the upgrade (?).

The error is the watcjdog reset itselft, which is happening continuously. Looks like increasing CONFIG_BOOTLOADER_WDT_TIME_MS from 9000 to 12000 did the trick and now the application is starting correctly. Thanks.