Skip to content

Add hardware & SoC architecture reference page - #4

Merged
cscaff merged 2 commits into
mainfrom
docs/hardware-architecture
Jul 11, 2026
Merged

Add hardware & SoC architecture reference page#4
cscaff merged 2 commits into
mainfrom
docs/hardware-architecture

Conversation

@cscaff

@cscaff cscaff commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Adds docs/reference/hardware.md: the board (Lattice ECP5), the fixed LiteX SoC every node boots, the 2 KB user address window, and a real (measured, not estimated) FPGA resource budget built from the base SoC with a no-op placeholder in the user slot.
  • Wires up Mermaid rendering for the custom theme (docs/javascripts/mermaid-init.js, loaded as an ES module), themed to match docs.css's dark palette, and used for a system architecture diagram on the new page.
  • Cross-links the new page from reference/index.md and examples/ffn-accel.md.

Test plan

  • mkdocs build --strict passes with no warnings/errors
  • Verified the Mermaid diagram actually renders (not just parses) using a headless browser against the built site; caught and fixed a real bug where Mermaid v11's run() chokes on the <code> child that pymdownx.superfences wraps fenced content in
  • Confirmed no em dashes, no exposed vendor/PCB-level infra details, no Wishbone "slave" terminology
  • CI

🤖 Generated with Claude Code

cscaff added 2 commits July 11, 2026 16:18
Users had no way to see what's on the other end of mrg run: the board,
the fixed LiteX SoC every node boots, or how much of the FPGA is left
for their own design. Adds docs/reference/hardware.md with the address
space, a Mermaid architecture diagram, and a real (measured, not
estimated) resource budget from building the base SoC.

Also wires up Mermaid rendering for the custom theme (superfences
already emitted mermaid fences, but nothing rendered them), themed to
match docs.css's palette.
The deploy step already guarded itself with
if: github.event_name != 'pull_request', but nothing ever triggered
the workflow on a PR, so mkdocs build --strict never actually ran as
a check before merge. Add the missing trigger.
@cscaff
cscaff merged commit d3b37c6 into main Jul 11, 2026
1 check passed
@cscaff
cscaff deleted the docs/hardware-architecture branch July 11, 2026 20:21
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.

1 participant