Skip to content
Template application with OTA capability for
Branch: master
Clone or download
Pull request Compare This branch is 9 commits ahead, 7 commits behind espressif:master.
Type Name Latest commit message Commit time
Failed to load latest commit information.
components/ota_server update components/ota_server Sep 7, 2017
main Added OTA capability to esp-idf-template Sep 5, 2017

ESP-IDF OTA template app

This is a template application with OTA capability, to be used with Espressif IoT Development Framework.

See also (component version):

OTA capability is achieved with rather small binary and memory footprint.

repository binary size free memory flashing speed
espressif/esp-idf-template 423,424 bytes 248,604 bytes 10s (via UART in 921,600bps)
yanbe/esp-idf-ota-template 474,849 bytes 245,060 bytes 6s (via OTA)

With OTA template app, your build-flashing-monitor cycle become much easier and faster.


You have to flash via UART first, then confirm IP address (like assigned to ESP32 via log output of make monitor with USB UART.

$ make menuconfig # configure "WiFi Configuration" menu on your network.
$ make erase_flash flash monitor

After that, you can use flashing capability with special make target

$ make ota ESP32_IP=

What's difference from official OTA example in ESP-IDF?

ESP-IDF's OTA example project is a good starting point to understand how ESP32's OTA flashing works with official OTA suppoprt components. But it is pull architecture. You have to launch HTTP server on your PC every time, and wait ESP32 to update their program. It is not optimal in terms of speed up build-flashing-monitor cycle on developing phase.

My OTA template app push architecture. So you can flashing natural make command like berow.

$ make ota ESP32_IP=

Additionally, in esp-idf-ota-template, OTA implementation is placed into components/ota_server so you can concentrate your project without be bothered by OTA-related socket programming code.

You can’t perform that action at this time.