Recurring OTA output

[DrMickeyLauer]

I have implemented a custom OTA routine using the documented API. After uploading the new binary and resetting, the new binary successfully boots and obviously runs normally, however via UART I keep seeing the following output:

Code: Select all

D (12173) esp_ota_ops: found ota app max = 2
D (12173) boot_comm: Both OTA copies are valid
D (12173) esp_ota_ops: finding ota_17 app...
I (12173) OTA: Running partition type 0 subtype 17 (offset 0x001b0000)
I (12183) OTA: Writing to partition subtype 16 at offset 0x10000
I (12183) OTA: Running firmware version: b6f2229-dirty
D (12193) esp_ota_ops: Invalid otadata[-1]
D (20673) esp_ota_ops: found ota app max = 2
D (20673) boot_comm: Both OTA copies are valid
D (20673) esp_ota_ops: finding ota_17 app...
I (20673) OTA: Running partition type 0 subtype 17 (offset 0x001b0000)
I (20673) OTA: Writing to partition subtype 16 at offset 0x10000
I (20683) OTA: Running firmware version: b6f2229-dirty
D (20693) esp_ota_ops: Invalid otadata[-1]
D (29133) esp_ota_ops: found ota app max = 2
D (29133) boot_comm: Both OTA copies are valid
D (29133) esp_ota_ops: finding ota_17 app...

What's that about? Is there something hanging in the background? Did I do something wrong in OTA?

I just followed the sequence of

Code: Select all

esp_ota_begin();
esp_ota_write();
esp_ota_end();
esp_ota_set_boot_partition(esp_ota_get_next_update_partition(NULL));