G1 Mini Custom Firmware 1.2.1
Highlights
- Fixed the dashboard trend graph so startup and restart gaps are not rendered as repeated drops to zero.
- Added a standalone MCU loader that probes supported buses, uses board-matched reset paths, and verifies all firmware CRC values after loading.
- Added a bounded-backoff supervisor so an unexpected Lua controller exit does not leave mining permanently stopped.
- Serialized MCU register and rail-monitor transactions through a shared lock.
- Made DDR telemetry an atomic, validated register-pair read with retries and exception isolation.
- Expanded support bundles with MCU route, reset, mount, network, service, and loader diagnostics while redacting pool identity fields.
- Kept DHCP as the public default and removed the development pool worker from the image.
Hardware Qualification
The 1.2.1-test5 runtime stack completed an 8.4-hour hardware run on the custom 2100 MHz profile:
- 1,032 accepted shares
- 5 pool rejections, approximately 0.48 percent
- 2 unknown result frames
- no MCU resets, core resets, pool reconnects, telemetry errors, or active faults
- 59.52 C maximum observed chip temperature
- approximately 1.416 G/s and 2.05 shares/min near the end of the run
The final 1.2.1 image adds the graph-only test6 correction on top of that runtime stack. The corrected JavaScript, history filtering, packaged squashfs contents, native helper builds, shell scripts, DHCP configuration, and artifact hashes were validated locally.
First Boot
The miner obtains its address by DHCP. Find hostname g1m-110 in the router lease table, open its dashboard, and configure your own pool account/worker identity in Admin before expecting mining to start.
Known Limitations
- Hardware compatibility is currently qualified on the available G1 Mini board; the adaptive MCU loader diagnostics are intended to make other board-batch failures actionable.
- Rail telemetry remains optional and may be unavailable on some boards.
- The flash image retains the proven vendor host rootfs baseline; OpenWrt 25 is not used for this release.
- The experimental 2100 MHz profile is opt-in and is not the public boot default.