Firmware v0.13.7

Firmware v0.13.7 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.6

Firmware v0.13.6 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.5

Firmware v0.13.5 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.4

Firmware v0.13.4 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.3

Firmware v0.13.3 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.2

Firmware v0.13.2 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.1

Firmware v0.13.1 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.13.0

Firmware v0.13.0 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.12.1

Firmware v0.12.1 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.

Firmware v0.12.0

Firmware v0.12.0 for every supported board. Each esp-idf board ships app-<board>.bin + bootloader-<board>.bin + partition-table-<board>.bin; the esp8266 ships a single app-esp8266.bin (flash at 0x0). Every app image carries an ed25519 release signature (app-<board>.bin.sig, also embedded in version.json) that signature-enforcing firmware verifies before installing an OTA. version.json describes them, including a per-board ota flag — heltec-v3/v4 are OTA-updatable (2 MB A/B), the T-Display/C6 are 4 MB factory (USB re-flash), the esp8266 has no OTA. Pull into Sapwood with npm run sync:firmware.