"esp_ota_set_boot_partition()" triggers WDT during image validation
Posted: Sun Oct 15, 2023 10:34 am
Hi to all.
On an Esp32s3 devkit c1 I'm running an http server wich hosts a small webpage, inspired to the "file_serving" example, which allows me to upload a new firmware into memory. However, no matter what I try (enlarging/reducing partition, smaller flash size, etc...) it always triggers the Task watchdog timer while updating.
I've been tinkering for some time with this issue and I've just found out that the update is halting right after calling "image_validate()", giving the following output:
If I understand well, there may be something wrong with the header of the application, since it is stuck on the segment 0.
I tried commenting the code in "esp_ota_set_boot_partition()" (inside "esp-idf-v5.1.1\components\app_update\esp_ota_ops.c") which calls "image_validate()", and the ota update succeded.
Is there anyone that could help me?
Thanks in advance,
Pascon.
On an Esp32s3 devkit c1 I'm running an http server wich hosts a small webpage, inspired to the "file_serving" example, which allows me to upload a new firmware into memory. However, no matter what I try (enlarging/reducing partition, smaller flash size, etc...) it always triggers the Task watchdog timer while updating.
I've been tinkering for some time with this issue and I've just found out that the update is halting right after calling "image_validate()", giving the following output:
Code: Select all
I (31654) esp_image: segment 0: paddr=00110020 vaddr=3c090020 size=26ae8h (158440) map
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x8 (TG1WDT_SYS_RST),boot:0x28 (SPI_FAST_FLASH_BOOT)
Saved PC:0x42002f67
0x42002f67: panic_handler at C:/ESP-IDF/esp-idf-v5.1.1/components/esp_system/port/panic_handler.c:145 (discriminator 3)
SPIWP:0xee
mode:DOUT, clock div:1
load:0x3fce3818,len:0x16e8
load:0x403c9700,len:0x4
load:0x403c9704,len:0xc00
load:0x403cc700,len:0x2ed0
entry 0x403c9908
I (31) boot: ESP-IDF v5.1.1-dirty 2nd stage bootloader
I (31) boot: compile time Oct 15 2023 11:04:46
I (32) boot: Multicore bootloader
I (35) boot: chip revision: v0.2
I (39) boot.esp32s3: Boot SPI Speed : 80MHz
I (44) boot.esp32s3: SPI Mode : DOUT
I (49) boot.esp32s3: SPI Flash Size : 8MB
W (53) boot.esp32s3: PRO CPU has been reset by WDT.
W (59) boot.esp32s3: APP CPU has been reset by WDT.
I tried commenting the code in "esp_ota_set_boot_partition()" (inside "esp-idf-v5.1.1\components\app_update\esp_ota_ops.c") which calls "image_validate()", and the ota update succeded.
Is there anyone that could help me?
Thanks in advance,
Pascon.