Problem:
1. In low-memory scenarios, the dynamic buffer feature can fail due to memory fragmentation.
2. It requires a contiguous 16KB heap chunk, but continuous allocation and deallocation of
the RX buffer can lead to fragmentation.
3. If another component allocates memory between these operations, it can break up the
available 16KB block, causing allocation failure.
Solution:
1. Introduce configurable strategy for using dynamic buffers in TLS connections.
2. For example, convert RX buffers to static after the TLS handshake.
3. Allow users to select the strategy via a new field in the esp_http_client_cfg_t structure.
4. The strategy can be controlled independently for each TLS session.
Checked the support of OTA features for esp32c5, tested
examples and added the support in README.md file. Even
added the support in systems .build-test-rules.yml
This commit adds one more config option under partition table menu
to support large size image during ota
This also updates the default config for simple ota example.
This commit refactors the script responsible for starting a Python-based HTTPS server
to align with the latest Python version's requirements and best practices.
Closes https://github.com/espressif/esp-idf/issues/13575
fix(nt/bluedroid): Split the device name set functions
feat(bt/bluedroid): added APIs to get/set device name on BT GAP side
change(bt/common): Marked some APIs in device module as deprecated
1. esp_bt_dev_set_device_name
2. esp_bt_dev_get_device_name
change(bt/bluedroid): use BT GAP APIs to set/get device name in bluetooth classic examples
change(bt/bluedroid): use BT/BLE GAP APIs to set/get device name in coexist examples
openssl server does not support for range request mechanism.
Consequently, it does not support partial download feature.
So, removing commands and steps required for staring openssl server.
Also, updated pytest file to avoid unnecssary issues while starting server.
esp_https_ota_get_img_desc() is incorrectly referred to as esp_https_ota_read_img_desc()
in some error messages.So, this MR updates related references
Closes https://github.com/espressif/esp-idf/issues/13065
The members of the esp_decrypt_cfg_t configuration structure have been updated to correctly
reflect that we are using RSA private key member for the decryption purpose. Earlier their names were
incorrect. This old names have been marked as deprecated for IDF 5.2 release. This change can be viewed
at https://github.com/espressif/idf-extra-components/pull/187 and its part of esp_encrypted_img
component version 2.0.4
This commit updated to newer API usage from esp_encrypted_img component v2.0.4 for
pre_encrypted_ota example.