4 posts • Page 1 of 1
OTA in ESP32 is implemented in application logic in your own application. What this means is that your app is responsible for retrieving the new flash image. How the data gets into your ESP32 is up to you ... whether it be received by TCP/IP over WiFi, or loaded from a flash memory card or pushed in by serial ... all are good. For Bluetooth, your puzzle breaks down to "How do I move about 1MByte of data from a source into the ESP32?" ... from there the OTA APIs take over. If the ESP32 is one half of the communicating pair, what is the other half? How would you envisage Bluetooth and OTA being combined?
Free book on ESP32 available here: https://leanpub.com/kolban-ESP32
hahaha, nice 3 years later he gets his answer... i was looking for this too thanks!
Who is online
Users browsing this forum: Bing [Bot] and 55 guests