Arena studio isp artifacts - #134
Merged
Merged
Conversation
Consolidated onto current main. v5 is the approved density/ergonomics pass over v4 (one 44px bar; Console essentials + collapsible foot-gun groups; 150px collapsible run-log) with content re-synced to shipped main: ArenaSession broker shipped, run-log module built-but-unwired, plus #126 analog/digital-out, #129 run-whole-condition, #130 0x88 + panel-display-mode, #131 FicTrac. Handover refreshed to the verified 2026-07-01 shipped-vs-pending table. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Groundwork for Arena Studio's "push official builds to panels" flow: - docs/development/arena-studio-isp-firmware-push-handoff.md — catalog schema (isp_file/isp_sha256, firmware repo PR #17), the 0xE0/0xE3/0xC8/ 0xC9 wire flow (encoders already in js/arena-wire-g6.js), UX notes from the real fleet reflash, gotchas (CORS: Pages yes / Release assets no). - flasher/firmware/manifest-dev.json — schema-identical dev catalog to develop against until PR #17 + a release tag publish the real one. - Dev builds (same-origin): isp-progress-display 23d66af (progress bar while ISP-flashing + first-boot smiley), both revs, .bin + .uf2; plus the current fleet build (dd7d3f9) ISP bins. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mbreiser
added a commit
that referenced
this pull request
Jul 2, 2026
Follow-up to PR #134 (dev ISP artifacts + handoff doc). The chooser's hardcoded local list is gone — it now consumes TWO schema-identical manifests, refreshed every open: the published Pages catalog (empty until a panel-fw-v* tag is cut — merging to main does NOT republish, the workflow is tag-triggered) and this site's flasher/firmware/manifest-dev.json (4 entries: the ISP-progress builds 23d66af — on-panel progress bar + smiley — defaulted, plus the dd7d3f9 fleet builds). My earlier duplicate bins removed (byte- identical to the fleet ones from #134). Wire-level hardening from the handoff doc: - 0xE0 stored-CRC verify: the reply echoes the CRC-32 of what the SD actually wrote; we now compare against a local zlib crc32 and refuse to proceed on mismatch (corrupt SD write can no longer feed a panel flash). - Program (0xC8) timeouts 45 s → 240 s (stage ~540 pages + LittleFS commit + reboot), single and batch. - Connect-time init also reads the 0xE3 footer: "on SD: <release>" shown persistently, since the footer version now carries the release tag. Verified in-browser against the real manifests: 4 dev entries listed with the honest "no published ISP images yet (tag a panel-fw-v* release)" note, real isp_sha256 verified on fetch, corrupt stored-CRC refused. Handoff doc's status ledger updated (fetch/push UI: shipped). Co-Authored-By: Claude Fable 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
1 participant
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.
No description provided.