Finally I found the reason - I was doing memcpy to a string literal. This gave no warnings (and also somehow worked). When the code was fixed, esp_ota_end does not fail.

It appears that a call to esp_partition_get_sha256 also results in the same crash. I added the following code (taken from native OTA example): uint8_t sha_256[HASH_LEN] = {0}; esp_partition_t partition; // get sha256 digest for the partition table partition.address = ESP_PARTITION_TABLE_OFFSET; part...

Hello, Unfortunately I cannot share my complete application. I've enabled Debug log level, boot log attached. What I also did was comment out the while loop in the panic handler: // For cache error, pause the non-offending core - offending core handles panic if (panic_get_cause(frame) == PANIC_RSN_C...

After another day of fruitless bug hunting, I am considering the possibility of cache error. I've disabled the TWAI driver, and deregistered the FreeRTOS tick hook just before calling esp_ota_end - with no effect. Edit: I also checked all running tasks' stack before calling esp_ota_end, did not noti...

Another lead: the code execution ends in panic_handlers.c : // For cache error, pause the non-offending core - offending core handles panic if (panic_get_cause(frame) == PANIC_RSN_CACHEERR && core_id != esp_cache_err_get_cpuid()) { // Only print the backtrace for the offending core in case of the ca...

Updating the topic again in the hope that anyone with a similar problem will shed some light. The reset reason which is printed out after the chip reboots is rst:0x8 (TG1WDT_SYS_RST),boot:0xb (SPI_FAST_FLASH_BOOT) It is defined in rtc.h as " Timer Group1 Watch dog reset digital core" . Looking in th...

Update: I attached a JTAG debugger, which confirms failure happens in esp_image_format.c/process_segment function.
In addition, EXCAUSE is set to 0x04.

I am implementing update over USB HID for my application, following the native OTA example . I can write the complete binary image using esp_ota_write, and when I call esp_ota_end, the application hangs with message: I (184599) esp_image: segment 0: paddr=00210020 vaddr=3c060020 size=1f13ch (127292...

When using idf.py monitor, I get a bunch of errors related to missing file xtensa-esp32s3-elf-addr2line. The binary is on my file system, under $IDF_TOOLS_PATH directory. How to ensure idf.py monitor finds it? Thanks -- idf_monitor on /dev/ttyUSB1 115200 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: C...

I would really appreciate input from ESP support here. I've spent a few days with no results and I need to know if I am on the wrong path.