Skip to content

[codex] Publish verified AVR HEX and high-DPI application artwork - #44

Draft
atomicdeploy wants to merge 3 commits into
fix/opcode-registry-admissionfrom
codex/firmware-hex-branding
Draft

atomicdeploy wants to merge 3 commits into
fix/opcode-registry-admissionfrom
codex/firmware-hex-branding

Conversation

@atomicdeploy

Copy link
Copy Markdown
Owner

Changes

  • Publish application-only and full-flash AVR Intel HEX for all three link builds. Both enter checksummed CI reports and release ZIPs. Reuse the existing Intel HEX parser; reject checksum/encoding/reset errors and compare the bootloader HEX byte-for-byte with its verified BIN. ESP32-S3 images stay raw BIN.
  • Replace the prototype monochrome Circuitry mark with original editable SVG artwork: staggered illuminated cells and a circular key, in emerald/mint/white on deep teal.
  • Render 24–1024px assets with the existing external Sharp rasterizer. Native executable/window/ICO and README/Android launcher use the 1024px master. Firmware/peer/Web headers retain a bounded 64px derivative; retain board-role/custom artwork priority and seven native ICO sizes.
  • Deterministic committed artwork/source hashes provide dependency-free no-write checks; no per-build download/rasterizer installation or extra native cache.

Part of #11/#5. Stacked on #43; shared opcode changes belong there, not this diff.

Verification

Branding/generation, script tooling, release/governance/manifest, Web identity, UPnP image metadata and actual release ZIP fixtures pass. Malformed and mismatched HEX is rejected. Existing local outputs validate six HEX files (three app/full-flash pairs); this is not a newly compiled firmware delivery. The 1024px and compact PNGs were visually inspected.

The guarded local Rust branding test stopped before compilation because the active Pealayer checkout changed required donor sources. Historical reviewed per-file pins are preserved, new paths inventoried and live drift is not waived. CI remains the independent native compilation/executable acceptance gate. Earlier #43 Windows CI also has an unrelated WebSocket bootstrap test failure (507 pass, one fail); no all-green, deployment or production resource-extraction claim.

No board, installed app, settings, OS icon cache, EEPROM or fuses changed. Existing useful donor omissions and deployment/physical gates remain open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants