OTA from 2.3.4 to 2.3.5 fails

[avandorp]

OTA via link in top banner or via "info/firmware/Select firmware file for upload" both fail on my ESP32-C3. Previous upgrade experience would suggest that it might work after some more tries. Currently I've only tried it probably two dozen times. And I'm pretty sure that upgrading via USB after disassembly of the installation would work (I will try that later).

Using the link in the top banner reloads the UI a few seconds after pressing OK, showing "Previous upgrade attempt from v2.3.4 to v2.3.5 failed -100" in the info/firmware box. Debug log shows:

[frames]
(V) LNG
(E) Serial buffer overflow
(E) Serial FIFO overflow
(E) Update failed
(W) Used 2401ms to handle web
(V) HDLC frame:
[more frames]

Using the upload method takes much longer (and I see my computer having egress network traffic, indicating that the firmware file is sent) and reboots the device. Debug log shows:

[frames]
(V) LNG
(D) handleFileUpload file: /firmware.bin
(D) handleFileUpload Open file and write: 0
(D) handleFileUpload Written: 0
(E) Serial buffer overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(E) Serial FIFO overflow
(D) handleFileUpload Ended
(W) Used 24474ms to handle web
(E) Serial buffer overflow
[...frames...]
(W) loop() used 24635ms
(I) Successfully connected to MQTT
(I)   Subscribing to [homeassistant/status]
(I) Received online status from HA, resetting sensor status
(V) HDLC frame:
(V) 7E A0 7D CE  FF 03 13 D0  45 E0 40 00  02 00 00 6C 
(V) 02 04 12 00  03 09 06 01  01 01 08 00  FF 0F 02 12 
(V) 00 00 02 04  12 00 03 09  06 01 01 02  08 00 FF 0F 
(V) 02 12 00 00  02 04 12 00  03 09 06 01  01 05 08 00 
(V) FF 0F 02 12  00 00 02 04  12 00 03 09  06 01 01 06 
(V) 08 00 FF 0F  02 12 00 00  02 04 12 00  03 09 06 01 
(V) 01 07 08 00  FF 0F 02 12  00 00 02 04  12 00 03 09 
(V) 06 01 01 08  08 00 FF 0F  02 12 00 00  FF 09 08 
(W) Boundry flag missing
(V)   payload:
(V) 7E A0 7D CE  FF 03 13 D0  45 E0 40 00  02 00 00 6C 
(V) 02 04 12 00  03 09 06 01  01 01 08 00  FF 0F 02 12 
(V) 00 00 02 04  12 00 03 09  06 01 01 02  08 00 FF 0F 
(V) 02 12 00 00  02 04 12 00  03 09 06 01  01 05 08 00 
(V) FF 0F 02 12  00 00 02 04  12 00 03 09  06 01 01 06 
(V) 08 00 FF 0F  02 12 00 00  02 04 12 00  03 09 06 01 
(V) 01 07 08 00  FF 0F 02 12  00 00 02 04  12 00 03 09 
(V) 06 01 01 08  08 00 FF 0F  02 12 00 00  FF 09 08 36 
(V) 33 33 32 36  34 31 33 06  00 00 02 44  06 00 00 00 
(V) 00 06 00 2D  14 96 06 00  00 0F 01 06  00 00 CA A5 
(V) 06 00 00 00  6D 06 00 00  17 25 06 00  0E 27 C7 12 
(V) 00 3E 12 00  81 12 00 6B  69 42 7E 
(D) Sending translation file for language: en
(D) Language file /translations-en.json
[...frames...]
(I) Rebooting

Somehow I would expect that handling frames, subscribing/sending to MQTT would be stopped during upgrade and only resumed after reboot. But whether that would solve the problem I don't know.