Closed franz-ms-muc closed 1 year ago
Thanks for reporting.
Hello Franz,
Changing the TLS memory setting from SPIRAM to Internal RAM seems to solve the problem.
Made longterm flash in the loop test with one application updating the other => no checksum verification failures.
However, with the same setting in the example project advanced_https_ota I can’t still force it to break so that I can show the issue to ESP.
Best regards,
Martin
Hello @franz-ms-muc Could you also share the sdkconfig file? It will be helpful in reproducing the issue. Thanks!
@franz-ms-muc
I suspect this could be related to memory corruption. Please use guidelines from https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/heap_debug.html.
Alternatively, if you would recreate the issue under any IDF example then please share us the instructions.
Hello @franz-ms-muc Any update on this issue?
@franz-ms-muc Thanks for reporting, would you please help share if any updates for the issue? Thanks.
Closing. Please drop a comment if you are still facing a issue here..
Answers checklist.
IDF version.
ESP-IDF Pre-release v5.0-rc1
Operating System used.
Windows
How did you build your project?
Eclipse IDE
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
Custom Board
Power Supply used.
USB
What is the expected behavior?
I expected a clean OTA Process.
What is the actual behavior?
but sometimes there are 16bit Portions in the Flash corrupted, and therefore the OTA Checksum failes.
sometimes also sectors gets filled with FF,
Steps to reproduce.
In the Moment we cannot let you reproduce this, it is happening in our closed-Source software, and we could not see it in the Samples, nor reproduce it. so we need Support in detecting and fixing the Error.
Debug Logs.
More Information.
No response