GitHub Repos intermediate 3 min read Jun 20, 2026 · Updated Jun 21, 2026
Public Preview Sign in free for the full digest →

Two EE Students Built an 8-Bit CPU From Raw Logic Gates

“The control unit has no EEPROM — every signal like 'increment PC' or 'load register' is a physical AND/OR gate. Add a 17th instruction and you are not editing a ROM; you are rewiring gates.”

Two EE Students Built an 8-Bit CPU From Raw Logic Gates
1 Views
0 Likes
0 Bookmarks
Source · github.com

“"We actually made it on breadboards, since it was hardwired the bread-board is now a sea of wires everywhere, and some things are not working too. I am thinking of getting a custom PCB just for the control unit to make it presentable." — CorRupT9 (https://news.ycombinator.com/it...”

You know that feeling when a computer architecture textbook shows you a CPU control unit as a box labeled 'microcode ROM' and you nod along — but you have no intuition for which gate actually switches on when the CPU needs to load a register? Microcode hides that mapping in a ROM you cannot open. STEPLA-1 replaces that ROM with explicit AND/OR gate combinations, so every control signal has a visible, traceable physical cause. The cost is that the breadboard build is now, in the creator's own words, 'a sea of wires everywhere, and some things are not working too.'

cpu-designdigital-logiccomputer-architecturehardwarelogisimeducationassembly

STEPLA-1 fetches an 8-bit instruction from Instruction SRAM. The top 4 bits select one of 16 operations; the bottom 4 bits encode source and destination registers (RA–RD). Instead of looking up required control signals in an EEPROM, the control unit drives each control wire from a combination of AND/OR gates keyed directly to the current opcode bits — a PLA-inspired gate matrix. The clock runs in two phases: the control logic evaluates on the first phase, the data path acts on the second, giving the gates time to settle before any flip-flops latch. A Bootstrap Control Unit runs once on power-on, copying a ROM image into Instruction SRAM, then hands control to the main CPU.

01
Hardwired PLA gate matrix — every control signal (increment PC, load register, enable ALU) is a physical AND/OR gate combination you can trace end-to-end; no EEPROM or ROM chip required to store the control logic
02
Dual-phase clocking — the control unit evaluates on phase one and the data path acts on phase two, eliminating a class of race conditions that trip up first-time CPU designers without needing complex timing constraints
03
Bootstrap Control Unit — cold-boots by copying a ROM image into Instruction SRAM, so you can trace the full startup sequence at gate level rather than having it hidden in firmware
04
Early-exit conditional branching — checks zero or carry flag and branches immediately if the condition is met; per primary source, saves up to 25% of cycles per branch when the condition is not met (not independently benchmarked)
05
Python assembler included — write programs in STEPLA-1 assembly and assemble them without an external toolchain; Fibonacci sequence and counter demos are included
06
43-page specification document — covers each subsystem with version control, structured as a reference design you can study and reproduce independently
Who it’s for

If you are an EE or CS undergraduate studying computer organization, or an engineer who wants to trace every control signal in a CPU down to the gate level with full documentation, this is a rare reference design. Also useful for instructors looking for a concrete, open-source teaching artifact. Not useful if you need a production CPU, want interrupt support, or plan to synthesize directly to an FPGA without reworking the non-standard dual-phase clock.

Worth exploring

Worth reading the spec document and stepping through the Logisim simulation if you are studying computer architecture at the gate level — the hardwired control unit is a genuinely uncommon reference design with unusually thorough documentation for a student project. Not a platform to build on: no interrupt support, the physical build has unresolved wiring issues, no versioned releases, and extending the ISA requires redesigning the gate matrix rather than updating a ROM.

Developer playbook
Tech stack, code snippet, sentiment, alternatives.
PM playbook
Adoption angles, user fit, positioning.
CEO playbook
Traction signals, ROI, build vs buy.
Deep-dive insight
Full long-form analysis, no fluff.
Easy mode
Core idea, fast — when you need the gist.
Pro mode
Technical nuance, edge cases, tradeoffs.
Read the full digest
Go beyond the preview

Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.

Underrated tools. Unfiltered takes.

Read the full digest in the Snaplyze app for deep-dive insight, Easy and Pro modes, and the playbooks you can actually use.

Install Snaplyze →