Hello,
I read a lot of hints and tested lots of versions but did not get the solution to use esp32-cam with ElegantOTA for over the air updates.
Using the example esp32-cam CameraWebServer and adding ElegantOTA works, if I use the board without PSRAM and small jpeg picture size (SVGA).
If I let the board detect PSRAM and use the UXGA size for grabbing a picture, ElegantOTA (and also WebOTA as Arduino Basis) stops the firmware upload and reboots the board during the firmware update process.
I used the MinimalSPIFFS partition scheme.
I disabled the "WebServer function -startCameraServer()" and only use take_picture with the fb = esp_camera_fb_get(); to send a picture out.
I wonder, why only the PSRAM usage seems to disturb the OTA function.
Hi,
after some tests I found out, that all the "helpful" OTA enhancements for ESP32-cam boards fail, if config.fb_count = 2 is used. If I use PSRAM but only config.fb_count = 1, all OTA variants work with the OTA enabled partition scheme like the Minimal SPIFFS one.
Can somebody explain, why the frame buffe size is causing the reboot of the board in the OTA update case?
Thanks
Sounds very strange..
Haven't noticed any issues with my cams..
I'll try to run some specific tests later today..
I do my own OTA using update.h directly..
I am using Arduino IDE 1.8.19 with esp32 board manager 2.0.9.
with esp32 1.0.6 version I had less problems, but can not fall back due to other 2.0.9 dependencies.
And still different OTA variants cause board rebooting on firmware upload, if I use config.fb_count = 2.
If I use
config.fb_count = 1
, OTA works but I get not the last picture, only an older buffer content.
(and I use