The same bits, on the board
You will learn
How to show that a bitstream is byte-identical and that it runs.
The claim most FPGA people doubt: a bitstream built by an open flow from t27 specs, byte-identical to the reference toolchain, and working on a real board. This recording compares the files, loads the bits into the chip's SRAM and counts the receipts the board sends back. Drop two .bit files into bit-diff to check the byte-identical part yourself.
Try it
Wait for the receipts count at the end, then try bit-diff under Also try. In the spec frame, ACTIONS lists the steps of tri x7-board: which one loads the chip's SRAM, and which flag does HELP_LINE say it needs?

Byte-identical to openXC7's .bit, loaded into SRAM, 51,840 of 51,840 tagged receipts on the board.
specs/tools/trios/tri/x7-board.t27
// SPDX-License-Identifier: Apache-2.0
; specs/tools/trios/tri/x7-board.t27 -- tool gHashTag/BrowserOS:tri/x7-board, the `tri x7-board` command of the trios loop CLI
; Generated by apps/website/scripts/tools-from-trios-tri.mjs from gHashTag/BrowserOS:trios/bin/tri at 7366096248df; do not edit.
; The CLI the loop timers run (`tri drift` holds ~/.local/bin/tri to the tracked copy). It is another program than
; the Rust tri of gHashTag/t27 and the Zig tri of gHashTag/trinity, so the ID is repository-qualified.
; A card is data and carries no test block. ASCII only (L3). phi^2 + 1/phi^2 = 3 | TRINITY
module tool_trios_tri_x7_board;
pub const KIND : str = "tool";
pub const FAMILY : str = "tri-cli";
pub const ID : str = "gHashTag/BrowserOS:tri/x7-board";
pub const REPO : str = "gHashTag/BrowserOS";
pub const QUALIFIED_ID : str = "gHashTag/BrowserOS:tri/x7-board";
pub const SCHEMA : u32 = 2;
pub const COMMAND : str = "tri x7-board";
; The case arm of the dispatcher and the first line of it that does the work.
pub const VARIANT : str = "case arm `x7-board)`, line 1904";
pub const SOURCE : str = "trios/bin/tri";
pub const ENTRY : str = "trios/bin/tri";
pub const SOURCE_COMMIT : str = "7366096248dfb09893e9a7d1a0f1c56ced13d16e";
pub const ROUTED : bool = true;
pub const DISPATCH : str = "exec python3 \"$HOME/skills/xilinx7-bitstream-loop/scripts/x7board.py\" \"$@\"";
pub const DOCUMENTED : bool = true;
pub const HELP_LINE : str = "tri x7-board build|compare|load|receipts|all -- bitwalk on a real 200T build: byte-compare + timing vs openXC7, SRAM load (--owner-yes), harness receipts";
pub const CATEGORY : str = "xilinx7 MVP loop (bitstream back half as .t27, skill xilinx7-bitstream-loop)";
pub const ABOUT : str = "bitwalk on a real 200T build: byte-compare + timing vs openXC7, SRAM load (--owner-yes), harness receipts";
pub const ABOUT_SOURCE : str = "`tri help` (the heredoc under the help arm of trios/bin/tri)";
pub const ACTIONS : [5]str = ["build", "compare", "load", "receipts", "all"];
pub const ACTIONS_ABOUT : [5]str = ["", "", "", "", ""];
pub const ARGS : [0]str = [];
pub const AGENTS : [0]str = [];
pub const AGENTS_NOTE : str = "No source binds an agent letter to this command: the trios CLI is not named by docs/agents/AGENTS_ALPHABET.md or .claude/agents/*.md of gHashTag/t27.";
pub const WHEN_TO_USE : str = "bitwalk on a real 200T build: byte-compare + timing vs openXC7, SRAM load (--owner-yes), harness receipts";
; public/term/x7-board/meta.json lists 3 run(s) of `tri x7-board`; recorded with the live ~/.local/bin/tri,
; not a build of SOURCE_COMMIT. The site plays it at the end of this card.
pub const CAST : str = "term/x7-board/session.cast";
pub const WITNESS : str = "source-parse";
pub const WITNESS_SOURCE : str = "gHashTag/BrowserOS:trios/bin/tri at 7366096248dfb09893e9a7d1a0f1c56ced13d16e, read as text (the help heredoc and the top-level case arms); the CLI was not run";
pub const ENABLED : bool = true;
All lessons
Module 1 · The chip
What an FPGA is, which chip we use, and how its pins meet the board.
Module 2 · Numbers in hardware
Bits, trits and number formats, and what arithmetic costs in logic.
Module 3 · Your t27 program
Write a spec, test it, and see why compiling is not the same as being right.
Module 4 · Inside t27c
How the compiler reads a spec and what it writes, including the native t27b.
Module 5 · From spec to hardware
The Verilog t27c writes, the cells it becomes, and what one LUT does.
Module 6 · Reading synthesis
What yosys reports about your design, and which warnings matter.
Module 7 · Place, route, timing
Where the cells land on the die, and whether the clock is met.
Module 8 · The bitstream
How a routed design becomes the bits the chip loads, with no Vivado.
Module 9 · On the board
Ask the chip who it is, load the bits, and check them.