Skip to content

Releases

JARNSEN MESH v2.0.0-alpha.33 · Build 187

Choose a tag to compare

@github-actions github-actions released this 17 Sep 09:48

JARNSEN MESH v2.0.0-alpha.33

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 187
Source SHA: d777be9

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.32 · Build 186

Choose a tag to compare

@github-actions github-actions released this 15 Sep 22:35

JARNSEN MESH v2.0.0-alpha.32

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 186
Source SHA: d648a08

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.31 · Build 185

Choose a tag to compare

@github-actions github-actions released this 15 Sep 13:44

JARNSEN MESH v2.0.0-alpha.31

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 185
Source SHA: 6c2cb31

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.30 · Build 184

Choose a tag to compare

@github-actions github-actions released this 12 Sep 19:44

JARNSEN MESH v2.0.0-alpha.30

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 184
Source SHA: ea951fb

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.29 · Build 181

Choose a tag to compare

@github-actions github-actions released this 12 Sep 12:03

JARNSEN MESH v2.0.0-alpha.29

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 181
Source SHA: fe42dee

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.28 · Build 178

Choose a tag to compare

@github-actions github-actions released this 11 Sep 16:24

JARNSEN MESH v2.0.0-alpha.28

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 178
Source SHA: aadae40

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.27 · Build 168

Choose a tag to compare

@github-actions github-actions released this 10 Sep 16:08

JARNSEN MESH v2.0.0-alpha.27

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 168
Source SHA: 46a7604

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.26 · Build 167

Choose a tag to compare

@github-actions github-actions released this 09 Sep 14:51

JARNSEN MESH v2.0.0-alpha.26

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 167
Source SHA: ff63f24

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + Meshtastic-Web-Flasher custom BIN
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • factory.bin is an absolute full-flash image starting at 0x000000
  • meshtastic-webflasher.bin is relative to the first OTA app partition for Meshtastic Web Flasher custom upload
  • ESP32 application offsets are read from the generated partition table; no board-specific 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.25 · Build 166

Choose a tag to compare

@github-actions github-actions released this 09 Sep 03:27

JARNSEN MESH v2.0.0-alpha.25

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 166
Source SHA: 20f3d4d

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + partition-derived webflasher
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • ESP32 application offsets are read from the generated partition table; no 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme

JARNSEN MESH v2.0.0-alpha.24 · Build 165

Choose a tag to compare

@github-actions github-actions released this 08 Sep 19:06

JARNSEN MESH v2.0.0-alpha.24

Unified Core prerelease generated only after the Tracker preflight and all six supported board builds completed successfully.

Build: 165
Source SHA: 1382273

Firmware package policy:

  • Tracker / Heltec V3 / Heltec V4 / T-Beam Supreme: update + factory + partition-derived webflasher
  • LILYGO T-Beam: update + factory
  • Seeed Wio Tracker L1: native UF2
  • Every board package includes a package manifest and SHA256 checksums
  • ESP32 application offsets are read from the generated partition table; no 0x10000 assumption is used

Boards:

  • Heltec Tracker V1.1
  • Heltec V3
  • Heltec V4
  • Seeed Wio Tracker L1
  • LILYGO T-Beam
  • LILYGO T-Beam Supreme