Projects

Whole designs, not single capabilities: each one was built by the AI from the BKM's examples and skills, reviewed, tested in simulation and on the board, and documented the same way: an overview with the block diagram and the flow, an architecture spec, a user guide, and the full Quartus project as a .qar. No bitstreams in the repo: one build (a few minutes) makes the .sof.

RISC-V Tetris on the DE10-Lite screen

RISC-V Tetris

A RISC-V CPU in Verilog, 32 KB RAM, an 80x60 text screen; a Python assembler, C compiler and simulator; Tetris in C on it. The RTL matched the simulator over 294,803 steps.

runs on the board; joystick and sound to be checked by a person Pac-Man on the DE10-Lite screen

Pac-Man

The arcade game: the real maze, four ghosts with the arcade AI, power pellets, levels, lives, the intro tune. 9,504 LEs.

runs on the board; joystick and sound to be checked by a person

What every project folder holds

FileWhat it is
index.htmlthe overview: what it does, what you will see, the block diagram, how it flows, how it was tested, the review log, status, files
spec.htmlthe architecture spec: requirements, modules and ports, clock domains, memories, state encodings, budgets, design decisions
guide.htmlthe user guide: build, load, use, test over USB, flash, simulate, change, troubleshoot
<name>.qarthe whole Quartus project, archived by Quartus itself
src/, sim/, assets/, media/the sources, the testbench, generated data and generators, the pictures

The standard is the make-project skill, with a template in projects/_template/; a test checks that every project has these files and that this page links it. For single capabilities (a PLL, a ROM, the SDRAM...) see the examples.