Skip to content

V4.0 Beta. OTA enabled, no face recognition
Compare
Choose a tag to compare
@easytarget easytarget released this 08 Jun 13:51
· 71 commits to master since this release
v4.0.beta
84b55ba
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This initial 4.x release brings OTA to the ESP CAM example

.. at the expense of Face Recognition; which has been stripped out of the code.

OTA == Over The Air firmware updates (eg, you can update using WiFi)

  • Before you can use OTA you must flash your board at least once with an OTA enabled app and partition scheme. So you will still need the FTDI-Friend (or equivalent) at least once.

This is a big deal (for me, and others) because:

  • OTA makes updating installed cameras much easier, especially if you have mounted it in a high corner or on a trailer etc..
  • Face recognition was a nice demo; but of limited practical use, and made the firmware very large, slow to compile and slow to upload.

OTA is enabled by default, but you can disable it if required or set a password on the updater in your custom config to stop the cam being hijacked

Please See the updated Uploading Instructions, you must select the correct generic ESP32 DEV board type for OTA to work

  • The AI-THINKER board definition we use for v3.x in the IDE does not support OTA partitioning, unfortunately there is no warning for this; the cam and everything will appear to work until you try an update, which will fail. So we need to select a 'better' partition scheme with OTA enabled.
  • OTA works by reserving (approx) half of the memory for your program, and the other half for receiving the updates, this effectively halves the memory you have available for your program (which is why Face Recognition has to go, it uses over 75% of the whole esp32 memory).
  • I've updated the README with all the necessary details
Assets 2
Loading