Can't update my S3 via OTA

[chromoxdor]

Any ideas why?

[chromoxdor]

I am writing on a wake-on-GPIO addition and it is really annoying to reflash the device via serial since the flash gets erased. I also noticed that with the serial monitor connected, the ESP very often tends to reboot...

[tonhuisman]

it is really annoying to reflash the device via serial since the flash gets erased

Why is that? When using Upload from pioarduino plugin (or PlatformIO) it only uploads the .bin, and not erase the flash. When uploading via a web-flasher, you should be able to uncheck that option.

[chromoxdor]

Why is that? When using Upload from pioarduino plugin (or PlatformIO) it only uploads the .bin, and not erase the flash. When uploading via a web-flasher, you should be able to uncheck that option.

You are right, I could use other options. But it is my force of habit, I guess.
Especially when you are struggling with another problem, you do not want to learn another way of doing things that are not so important right now. And to be honest, I never used the webflasher nor the PIO option :)

[TD-er]

And the 'partition not found' error sounds like you might be flashing the wrong type of build?
For example a build for 4M or 8M on a 16M device (or any other combination which may cause issues)

[chromoxdor]

And the 'partition not found' error sounds like you might be flashing the wrong type of build?

No, I was flashing always the same build. It now seems to be working again. Don't know what happened here.
But the heavy slowdowns and reboots while using the serial monitor still persist. I will try to find another S3 to see if it is a hardware-related issue.

[TD-er]

Do you connect via USB-JTAG or USB to serial chip?

Recently something broke the serial on ESP32-S3. Not sure yet where, but I suspect the .available() is no longer working for serial on the S3
This even results in lost characters on the log output

[chromoxdor]

Do you connect via USB-JTAG or USB to serial chip?

I use the native USB CDC.
I also encountered that when a serial monitor is connected, the device is unable to connect to the given AP.

This even results in lost characters on the log output
Not only characters but whole lines of info...

[TD-er]

Yep, the lost characters (or lines, which are multiple characters ;) ) is under investigation.
Problem is, it isn't just the USB-CDC (JTAG) port, but also the HWSerial 0. So it is likely other use cases also may experience issues.

Espressif is also looking into this issue.

[TD-er]

For the serial issue, please change in platformio_esp32_envs.ini :

;monitor_filters           = esp32_exception_decoder
monitor_filters           = direct