| 1 |
The following are daily builds of the ESP8266 firmware. This will work on |
| 2 |
boards with at least 2MiB of flash. They have the latest features and bug |
| 3 |
fixes, WebREPL is not automatically started, and debugging is enabled by |
| 4 |
default. |
| 5 |
|
| 6 |
For boards with 1MiB or 512kiB of flash, two variants are provided with reduced |
| 7 |
functionality. The 1MiB variant removes asyncio and FAT-filesystem support as |
| 8 |
well as some modules from micropython-lib. The 512kiB variant further removes |
| 9 |
all filesystem support, as well as framebuffer support, some Python language |
| 10 |
features, and has less detailed error messages. |
| 11 |
|
| 12 |
Note: v1.12-334 and newer (including v1.13) require an ESP8266 module with |
| 13 |
2MiB of flash or more, and use littlefs as the filesystem by default. When |
| 14 |
upgrading from older firmware please backup your files first, and either |
| 15 |
erase all flash before upgrading, or after upgrading execute |
| 16 |
`vfs.VfsLfs2.mkfs(bdev)`. |
| 17 |
|
| 18 |
### OTA builds |
| 19 |
Over-The-Air (OTA) builds of the ESP8266 firmware are also provided. |
| 20 |
|
| 21 |
The first time you use this build you need to flash one of the "initial image" |
| 22 |
images using esptool.py as described above. After that, you can update the |
| 23 |
firmware over the air using the "OTA update" file in conjunction with the |
| 24 |
ota-client script from yaota8266. The "OTA update" files are digitally signed |
| 25 |
and will only work with the provided "initial image" files, and vice versa. |
| 26 |
(Note: this feature is work-in-progress.) |