User's Guide

Firmware: 3.1.003-2-g7ea18b4-dirty/factory/main (build idf
v3.1-dev-453-g0f978bcb Apr 7 2018 16:26:57)
Server Available: 3.1.003
Running partition: factory
Boot partition: ota_1
If the bootloader fails to boot from the specified OTA firmware, it will failover and boot from
factory.
We can flash firmware to OTA either from a file on VFS (normally /sd), or over the Internet (via
http). Let’s try a simple OTA update over HTTP:
OVMS# ota flash http
Current running partition is: factory
Target partition is: ota_0
Download firmware from api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin to
ota_0
Expected file size is 2100352
Preparing flash partition...
Downloading... (100361 bytes so far)
Downloading... (200369 bytes so far)
Downloading... (300577 bytes so far)
...
Downloading... (1903977 bytes so far)
Downloading... (2004185 bytes so far)
Download complete (at 2100352 bytes)
Setting boot partition...
OTA flash was successful
Flashed 2100352 bytes from
api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin
Next boot will be from 'ota_0'
OVMS# ota status
Firmware: 3.1.003-2-g7ea18b4-dirty/factory/main (build idf
v3.1-dev-453-g0f978bcb Apr 7 2018 16:26:57)
Server Available: 3.1.003
Running partition: factory
Boot partition: ota_0
Rebooting now (with ‘module reset’) would boot from the new ota_0 partition firmware:
OVMS# ota status
Firmware: 3.1.003/ota_0/main (build idf v3.1-dev-453-g0f978bcb Apr 7
2018 13:11:19)
Server Available: 3.1.003
Running partition: ota_0
Boot partition: ota_0
OVMS v3 User Guide Page 34 / 86