Skip to content

BDLMiner 2.5.1

Choose a tag to compare

@github-actions github-actions released this 06 Nov 12:27
4c038d3

BDLMiner V2 2.5.1

Fixes from the first days of 2.5.0; settings, mining, screens and web
pages are unchanged and the update installs over WiFi.

  • PSRAM is back on the boards that have it. The ESP-IDF rebuilt for 2.5.0 turned
    PSRAM off unless the board file declared it: the M5StickC Plus2 lost its 2 MB and
    could no longer open a secure connection to GitHub (release unavailable: manifest HTTP 0; API HTTP 0, with SSL - Memory allocation failed in the log), so it did not
    update by itself; M5Stack Core2 and Fire, and modules with PSRAM on the headless
    builds, lost theirs too. It is found at start-up again, as up to 2.4.2.
    An M5StickC Plus2 on 2.5.0 must be updated once through its web page (Settings ›
    Firmware update
    , m5stickc-plus2-firmware.bin of this release); later updates come
    by themselves again.
  • Built as C++23 and C23. 2.5.0 announced C++23 but was compiled as C++20 (the
    framework's flags ended with an older standard); the firmware's own code is now C++23
    and its C C23, and the build stops if another standard comes back.
  • Clearer TLS failures. On boards with PSRAM, a failed secure connection also logs
    the free PSRAM and its largest block.

Validation

All host, tool and browser tests and every board build pass; the M5StickC Plus2 build
has PSRAM enabled again. The PSRAM fix comes from a Plus2 log on 2.4.2 and 2.5.0; this
release has not yet been run on a Plus2.

What's Changed

  • build: C++23 and C23 for real, checked at compile time by @bdlglua in #25
  • docs(2.5.0): it was compiled as C++20, not C++23 by @bdlglua in #26
  • tls: log PSRAM next to the internal heap on failed handshakes by @bdlglua in #27
  • 2.5.1: PSRAM back on the boards that can carry it by @bdlglua in #28

Full Changelog: v2.5.0...v2.5.1