Repository navigation
v4.0.2-rc1: hardware results and mandatory BSSID pin for Ultra variants - #2
Merged
Merged
Conversation
…ident Board 601 / BM1370 (192.168.178.80), 124 samples over 3 711 s, evaluated from the raw CSV against thresholds declared before the run: all T1-T9 pass (0 rejected/stale, 1 530.8 GH/s last-30-min mean, 60.4 C / 82 C, heap flat, notifyDropped 0). Per-sample identity and Wi-Fi state were not CSV columns and are marked as snapshot/reachability based. No improvement is claimed. The new OTA handler has not run on hardware yet; reconnect-after-outage is NOT MEASURED. Records the BM1366 units flashed in the same session, including the failure: the un-pinned blackharkminer image went offline after OTA because the station picked a mesh node that associates but relays nothing (shown on timsminer's boot log); pinned variants fixed both. States the process fault and that the pin defaults to empty in tools/build_release.sh. Readiness: observation criteria and CI status updated; BSSIDs redacted. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
build_release.sh took the BSSID as an optional sixth argument defaulting to empty. On a mesh every node shares the SSID and a rebooted station takes the loudest one, which can be a node that associates but relays nothing. The un-pinned blackharkminer image went offline after OTA that way (reports/v4.0.2-rc1/HARDWARE_VALIDATION.md section 4). timsminer/blackharkminer now need <ip> <gw> <mask> <dns> <bssid|none>; 'none' is an explicit opt-out for single-AP networks, the format is validated, and the gateway/netmask/DNS defaults are gone so nothing is guessed. tools/test_build_release_args.sh checks the rejections (no args, missing, empty, short, non-hex, dashes, trailing char) for both variants and runs in the host-tests CI job. Against the previous script it fails; against this one it passes. A valid call was confirmed to pass validation and stop only at the missing IDF environment. README, CHANGELOG and RELEASE_READINESS updated accordingly. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Follow-up to #1 (already merged). Three commits:
ed796afdocs(report): hardware results forv4.0.2-rc1on the Board 601 / BM1370 unit (192.168.178.80) and the BM1366 incident from the same session.notifyDropped0).blackharkminerimage went offline after OTA, and the cause.f3563b4fix(tools):tools/build_release.shnow requires the BSSID pin fortimsminer/blackharkminer(noneopts out explicitly), validates the format, and drops the gateway/netmask/DNS defaults.tools/test_build_release_args.shcovers the rejections and runs in thehost-testsCI job.88926d9docs(readme): corrects the README status rows (the 353 h figures were v4.0.0), the build examples (the old ones would now be rejected) and the release row.Why
On a mesh every node shares the SSID, and a rebooted station takes the loudest one. That can be a node that associates but relays nothing (no DHCP, gateway unreachable). The pin was an optional sixth argument defaulting to empty, so an OTA-flashed unit could end up needing a USB cable. That is what happened to
blackharkminer; evidence is inreports/v4.0.2-rc1/HARDWARE_VALIDATION.md§4.For the reviewer
build_release.shand passes against this one. A valid call was checked to pass validation and stop only at the missing IDF environment; no firmware build was run for this change.NOT MEASURED. Per-sample board/ASIC and Wi-Fi state were not CSV columns and are marked snapshot/reachability based.746a2d7. Runs forf3563b4were started and not awaited when this PR was opened.docs/RELEASE_READINESS.md): noSHA256SUMSin the release assets, pool credentials logged at INFO bystratum_api, and the OTA handler untested on hardware..80was already intools/build_release.sh.GEMINI.mdhas uncommitted local edits that are not part of this work.🤖 Generated with Claude Code