Hi @i-snore Is your problem solved with https://forums.freertos.org/t/missing-esp-http-client-component/9098/6? For issue regarding backtrace decoding: /Users/vp/esp/Pebble_ESP32_Firmware/build/esp32_app 0x400d6f75: [Errno 2] No such file or directory Can you please confirm as why your executable is...

When you get AWS qualification, have you ever pass IDT test? Yes, I am attaching IDT report summary for your reference ESP32_DQP.zip For IDT setup related issues you may file query at https://github.com/aws/amazon-freertos/. Interim, any specific reason why you would like to run IDT at your end?

For platform to be listed in device catalog, it must successfully cover all qualification tests. If you would like you may verify results by following setup guides listed at https://github.com/aws/amazon-freertos/tree/master/doc for any of qualified ESP32 platform.

Following code snippet from `advanced_https_ota_example` should help here: while (1) { err = esp_https_ota_perform(https_ota_handle); if (err != ESP_ERR_HTTPS_OTA_IN_PROGRESS) { break; } // esp_https_ota_perform returns after every read operation which gives user the ability to // monitor the status...

Is it possible to share more information, especially server configuration, data format (chunked or non-chunked)? Additional information to help us reproduce this at our end would be very useful.

I want to permanently change to use 4.0 IDF (from 3.3.1) as soon as I can for my project. But in order to do so, I would want 2019r2 toolchain included automatically when using install.sh/export.sh. It should not require manual patching. Do you think this will be the case by the time 4.0 is officia...

Seems like you have downloaded toolchain for `esp32s2beta` chip. Can you please download latest toolchain for `esp32` from https://dl.espressif.com/dl/xtensa-esp3 ... d64.tar.gz?

You will have to update your $PATH environment variable to point to /path/to/xtensa-esp32-elf-gcc8_2_0-esp-2019r2-linux-amd64/xtensa-esp32-elf/bin/ directory. echo $PATH export PATH="/path/to/xtensa-esp32-elf-gcc8_2_0-esp-2019r2-linux-amd64/xtensa-esp32-elf/bin/:$PATH" Post this just ensure that com...

Thanks for confirmation. So this is related to same toolchain SPIRAM issue being discussed at https://github.com/espressif/esp-idf/issues/3624. Fix for this is to upgrade toolchain to latest `xtensa-esp32-elf-gcc8_2_0-esp-2019r2` (ESP-IDF specific commit can be found at https://github.com/espressif/...

Can you please try once by enabling internal memory allocation strategy for mbedtls (please refer https://github.com/espressif/esp-idf/blob/master/components/mbedtls/Kconfig#L22)? I am just trying to see if it is not something related to issue mentioned at https://github.com/espressif/esp-idf/issues...