Skip to content

History / Programming Protocols

Revisions

  • Repoint two firmware doc links at firestarter_fw

    Henrik Olsson committed Sep 14, 2026
  • docs: add generated provenance footers to six migrated pages (phase 173, D-09)

    Henrik Olsson committed Sep 2, 2026
  • docs: point the firmware reference links at beta main is 525 commits behind beta on the firmware repository, so a link into main would not resolve for a long time. beta is where work actually lands. These resolve once firestarter#57 merges.

    @henols henols committed Aug 31, 2026
  • docs: put the logo on every page Five pages were missing the header block -- the ones written or rewritten during this pass rather than migrated from a repository that already had it.

    @henols henols committed Aug 31, 2026
  • docs: restore the chip pin maps, lead protocols with their name Pin Maps carries all 15 chip family pin maps again. Moving them to the firmware repository was the wrong call: a pinout is what someone with a chip in their hand actually wants to look at. Only the shield's own wiring and control-register bits stay in the firmware repository, which is developer detail nobody programming a chip needs. Programming Protocols leads each section with the protocol's name and puts the number in parentheses after it.

    @henols henols committed Aug 31, 2026
  • docs: make the protocol pages user-facing Programming Protocols is now a plain description of what each protocol does and which chips it is for. Protocol ID and Protocol Flags are merged into it and deleted as separate pages. The implementation detail -- write algorithms, pulse widths, voltage routing, register constants, datasheet citations, the invariant matrix -- moves to PROTOCOLS.md in the firmware repository, linked from the top of the page. Pin Maps keeps the adapter wiring and the pin-21 warning a user acts on; the full per-family maps and shield wiring move to PINOUTS.md alongside it. Part numbers on the protocol page are now ones that actually resolve in the chip database -- the truth check caught W29C0xx filed under the wrong protocol, and several family prefixes and Dallas suffixes that were not real part numbers.

    @henols henols committed Aug 31, 2026
  • docs: cut the reference pages down to what a user needs Shield Revisions: replace the git-provenance inventory with a plain list of the real revisions and how to tell them apart. Drop the silkscreen alias table, the ADC band table and the investigation-history pointer. Capability matrix loses supported_protocol_ids, max_vcc_v and runtime_guard_gaps; notes now carry detection and jumpers. No modified or personal boards. Pin Maps replaces Pinout Safety Review and AT28C04 Adapter: socket pin maps for all 15 chip families generated from the pinout data, the DIP24 adapter reroute, and the shield's own pin and control-register assignments. Chip Database Fields replaces Infoic Field Dictionary: describes the Firestarter chip database rather than the upstream format. Protocol ID: protocol and what the algorithm is, nothing else. Protocol Flags: one bit/mask/meaning table, unknown bits included as unknown rather than guessed at. Package Details deleted -- its flags tables duplicated Protocol Flags and its own half was DIP-filter internals. SRAM and NVRAM Behavior deleted. Lockable PROMs keeps its family tables; intro tightened and tracking parameters stripped from the datasheet links.

    @henols henols committed Aug 31, 2026
  • docs: rework the front pages for a first-time reader Home: lead with what Firestarter is, then install the stable release directly. Drop the adapter and pinout-safety links; keep the protocol and chip reference sections. Link the beta last. Beta-Testing-Install -> Install-Beta: the board table now tells you how to identify your board rather than listing firmware assets and avrdude flags. Flashing cut to the command and what it does. Port-numbering note removed. Smoke test shortened. Community-Validation -> Testing-Chips, absorbing the 'help test a chip' handoff: written for a contributor rather than a maintainer, with no code references, no ladder internals and no summary table. Every claim about writing to the chip is kept in force. How-This-Wiki-Is-Published/How-To-Edit-This-Wiki deleted: with the publish pipeline retired there is no pipeline left to document. The adapter and pinout-safety pages are now reached from the protocol bucket that discusses those parts.

    @henols henols committed Aug 31, 2026
  • Migrate 12 documentation pages from firestarter/doc and firestarter_app/doc Copied byte-for-byte from the pre-deletion sub-repo commits recorded in tools/wiki/MIGRATION-TABLE.md, then edited within a bounded set: page title, removal of unopenable .planning/ paths, cross-file link repair to page titles, a firestarter-claim-stamp against the current chip database, and a firestarter-claims-begin/end region around the three tables whose claims this milestone's checkers will resolve against that database. The two GSD-framed pages (Pinout-Safety-Review, SRAM-and-NVRAM-Behavior) are de-framed: no phase-number title suffix, no audit-trail pointer into an unopenable path, their safety content otherwise intact. PY32F071-FIRMWARE-INSTALL.md is deliberately not migrated (deferred). Home.md and the sidebar are untouched by this commit; a later push updates their navigation once WIKI-05's live-orphan failure has been captured against this state.

    @henols henols committed Aug 31, 2026