Read a bitstream
You will learn
What is inside a .bit file, and which chip it was built for.
A .bit file is a header followed by packets: commands to the chip's configuration logic and the frames themselves. One of those commands writes the IDCODE of the chip the file was built for. Drop a .bit into the autopsy and see which chip it asks for. Five bitstreams committed to t27 turn out to target a different part than our bench.
Try it
Open the blink_j26 sample and compare the part in its header with the IDCODE it writes. In the spec frame, read HELP_LINE: against which reference tool is tri x7-writer byte-identical, and what kind of input does it refuse?

Drop a Xilinx 7-series .bit: header, the IDCODE it writes and the part that names, frames, zero bytes and packets, read in your browser. Nothing is uploaded.
specs/tools/trios/tri/x7-writer.t27
// SPDX-License-Identifier: Apache-2.0
; specs/tools/trios/tri/x7-writer.t27 -- tool gHashTag/BrowserOS:tri/x7-writer, the `tri x7-writer` 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_writer;
pub const KIND : str = "tool";
pub const FAMILY : str = "tri-cli";
pub const ID : str = "gHashTag/BrowserOS:tri/x7-writer";
pub const REPO : str = "gHashTag/BrowserOS";
pub const QUALIFIED_ID : str = "gHashTag/BrowserOS:tri/x7-writer";
pub const SCHEMA : u32 = 2;
pub const COMMAND : str = "tri x7-writer";
; The case arm of the dispatcher and the first line of it that does the work.
pub const VARIANT : str = "case arm `x7-writer)`, line 1903";
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/x7.py\" writer \"$@\"";
pub const DOCUMENTED : bool = true;
pub const HELP_LINE : str = "tri x7-writer [--heal] -- bitwalk --write byte-identical to xc7frames2bit on ~/.cache/x7/writer (16 entries) + wrong-part refusal";
pub const CATEGORY : str = "xilinx7 MVP loop (bitstream back half as .t27, skill xilinx7-bitstream-loop)";
pub const ABOUT : str = "bitwalk --write byte-identical to xc7frames2bit on ~/.cache/x7/writer (16 entries) + wrong-part refusal";
pub const ABOUT_SOURCE : str = "`tri help` (the heredoc under the help arm of trios/bin/tri)";
pub const ACTIONS : [0]str = [];
pub const ACTIONS_ABOUT : [0]str = [];
pub const ARGS : [1]str = ["[--heal]"];
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 --write byte-identical to xc7frames2bit on ~/.cache/x7/writer (16 entries) + wrong-part refusal";
; public/term/tri-x7-fasm/meta.json lists 1 run(s) of `tri x7-writer`; 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/tri-x7-fasm/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.