Dedicated or combined OTA

[Ritesh]

Its too not work. But it once worked and now get error

esp_http_client_config_t config = {
.url = EXAMPLE_SERVER_URL,
//.cert_pem = (char *)server_cert_pem_start,
};
11.jpg

Still, Error itself shows it's mbedtls security error. So, I suggest to bypass security for time being to verify same.

[brp80000]

And how do you propose to do I not understand something?

[Ritesh]

And how do you propose to do I not understand something?

Hi,

Would you please try with sample example of socket to download data from server and store into flash as per your configuration. And then update image.

[brp80000]

Ok, now my OTA is work.

[brp80000]

But then I am trying to install the certificate but have a problem with .rnd

[Ritesh]

Ok, now my OTA is work.

Great. Thanks for update regarding same.

[Ritesh]

But then I am trying to install the certificate but have a problem with .rnd

So, When you enabled security at that time OAT is not working with certificates related issue?

[brp80000]

I am trying to install the certificate but have a problem with .rnd

11.jpg (56.81 KiB) Viewed 9777 times

[brp80000]

Please explain that contains the "factory"...
OTA_0 and OTA_1 contain alternately updating the firmware.
As I understand it, in the "factory" area you can write a simple initial firmware, which will be loaded into the OTA_0 area.
If a piece of the program from OTA_0 in the future will start the firmware update it will be located in OTA_1. Continue alternating OTA_0 and OTA_1.
Is the "factory" area no longer used?

[loboris]

Please explain that contains the "factory"...
OTA_0 and OTA_1 contain alternately updating the firmware.
As I understand it, in the "factory" area you can write a simple initial firmware, which will be loaded into the OTA_0 area.
If a piece of the program from OTA_0 in the future will start the firmware update it will be located in OTA_1. Continue alternating OTA_0 and OTA_1.
Is the "factory" area no longer used?

You can use OTA_0 and OTA_1 without factory partition.
If the factory partition is used, the the code will run from it only until the 1st OTA upgrade, after that, the code will run from OTA_0 or OTA_1, whichever was updated last.
If both OTA_0 and OTA_1 gets corrupted, the code will run from factory partition again.
You can force running from factory partition (or ota partition different from the currently active partition) from application code or from the 2nd stage bootloader.
You can upgrade your factory partition while running from one of the OTA partitions by slightly modifying the the OTA upgrade code.