Enhance documentation for OTA write function

Added comments to clarify OTA write behavior and timeout handling.

Signed-off-by: Niel Nielsen <nieldk@gmail.com>
This commit is contained in:
Niel Nielsen authored and GitHub committed 2026-09-03 10:44:08 +02:00
1 parent d4427d3da5
commit 0dfcb72206
1 file changed
+5
+5
View File
@@ -322,6 +322,11 @@ int bwm_esp_ota_begin(uint32_t total_size) {
}
int bwm_esp_ota_write(const uint8_t *data, uint16_t len) {
// Documented OTA has no resume/offset: the payload is the raw chunk, written
// sequentially. A dropped chunk cannot be re-sent (it would double-write and
// fail the OTA_END size check) - recovery is to restart the whole OTA, which
// the client does. Keep a generous timeout so a slow flash write is not
// mistaken for a drop.
return bwm_cmd(BWM_CMD_OTA_WRITE, data, len, NULL, NULL, 15000);
}