SourceVu will show references to esp_https_ota_begin() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading...
esp_https_ota_begin() function
Start HTTPS OTA Firmware upgrade This function initializes ESP HTTPS OTA context and establishes HTTPS connection. This function must be invoked first. If this function returns successfully, then `esp_https_ota_perform` should be called to continue with the OTA process and there should be a call to `esp_https_ota_finish` on completion of OTA operation or on failure in subsequent operations. This API supports URL redirection, but if CA cert of URLs differ then it should be appended to `cert_pem` member of `http_config`, which is a part of `ota_config`. In case of error, this API explicitly sets `handle` to NULL.
Syntax
esp_err_t esp_https_ota_begin(const esp_https_ota_config_t *ota_config,
esp_https_ota_handle_t *handle);
Implemented in ![]()
esp_https_ota.c:260
Return value
- ESP_OK: HTTPS OTA Firmware upgrade context initialised and HTTPS connection established - ESP_FAIL: For generic failure. - ESP_ERR_INVALID_ARG: Invalid argument (missing/incorrect config, certificate, etc.) - For other return codes, refer documentation in app_update component and esp_http_client component in esp-idf.
Notes
This API is blocking, so setting `is_async` member of `http_config` structure will result in an error.
Related Functions
Found 2 other functions taking a ![]()
esp_https_ota_config_t
argument:
Function
Description
HTTPS OTA Firmware upgrade. This function allocates HTTPS OTA Firmware upgrade context, establishes HTTPS connection, reads image data from HTTP stream and writes it to OTA partition and finishes HTTPS OTA Firmware upgrade operation. This API supports URL redirection, but if CA cert of URLs differ then it should be appended to `cert_pem` member of `ota_config->http_config`.