DESIGN YOUR OWN PROCESSOR, A REAL FAB BUILDS IT

Breaking Taps had never touched an FPGA, gave himself one month, and sent a custom microprocessor to GlobalFoundries.

by Breaking Taps

Open-hardwareScience

Built withRaspberry Pi Pico / RP2040

difficulty
●●●●●
time
about a month of design before the tapeout deadline, then 3-4 months at the foundry
license
license not specified
repo
repo
1
Jump to section

COMPAREE VERDICT

This is not a weekend build. It shows that custom silicon is no longer reserved for corporations. Breaking Taps, who had never designed a chip or even used an FPGA, designed a microprocessor with a transport triggered architecture in Spade, a Rust-like hardware language: about 18-20 MHz, 4 KB of RAM, 16 registers, SPI, UART and a bootloader. The layout took about four hours to compile on a rented gaming server, and it was made on GlobalFoundries' 180 nm process through wafer.space, a shared wafer run. After 3-4 months the packaged chip ran his program, counting to 100 and lighting LEDs on a breadboard. It is not fully working: a few instructions do not work because of his own bugs, and he says the SPI is broken. The source is open on GitHub. Wafer.space lists 1,000 chips for 8,000 dollars; he does not say what he paid. If you want to design silicon yourself, this is a detailed look at the whole process, but the foundry makes the chip, not you.

GOOD TO KNOW

  • —Source code is on GitHub (polyfractal/BreakingTTAPs-Spade), written in Spade, a Rust-like HDL.
  • —No bill of materials, no PCB files, no step-by-step guide — this is the HDL source and the story of how he did it.
  • —The chip was made through wafer.space, a shared wafer service on GlobalFoundries' 180 nm process.
  • —Some instructions are broken because of his own bugs (he says so in the video at 29:16).
  • —The video does not say what he personally paid; wafer.space lists 1,000 chips for $8,000.
  • —This is not a project you clone and run — it is a proof that you can design a chip at home and have a real foundry build it.

Parts to buy

2 items

From our check of the build. Exact quantities and part numbers are in the creator’s BOM.

  • Slot on a shared wafer run such as wafer.space1,000 chips listed for $8,000; half and quarter size dies are cheaper, and Tiny Tapeout is a much cheaper optionFind
  • Breakout board for the packaged chipsFind

Can I build this?

Printnothing required — this is chip design, not a 3D print
Buya slot on a shared wafer run such as wafer.space (1,000 chips listed for $8,000; half and quarter size dies are cheaper, and Tiny Tapeout is a much cheaper option), plus a breakout board for the packaged chips
ToolsSpade, cocotb or Verilator for tests, the open-source LibreLane layout flow (wafer.space provides a Nix flake), a large rented server for the layout run, and for bring-up a breadboard with a Raspberry Pi Pico as the bootloader, level shifters and LEDs
SkillsHDL experience or a month to learn it; comfort with command-line tools, digital logic, and debugging hardware you cannot probe inside
Timeabout a month to design before the tapeout deadline, about four hours to compile the layout, then 3-4 months waiting for the foundry
Cost$$$, dominated by the shared wafer run — wafer.space lists 1,000 chips for $8,000, though the video does not confirm what he paid
SafetyNone beyond ordinary electronics care — this is digital logic at breadboard voltages, not mains or lithium.

Build at your own risk. Projects involve tools, electronics and sometimes mains voltage — follow the creator’s safety notes.

Videos

Custom microprocessor designed and sent to a real semiconductor foundry

33-minute walkthrough: the TTA idea, the Spade language, the open-source layout flow, wafer.space, and first bring-up with blinking LEDs

More builds like this

All projects

Gallery

Start here

Navigation into the creator’s own docs — we don’t rewrite the guide, we route you to the source.

  1. 1.Watch the full video (This is the primary source. He explains the TTA idea, the Spade language, the layout compile and the bring-up, and says the detailed processor design is coming in a later video.)
  2. 2.Read the Spade source (The open-source code for his chip, written in Spade. Some instructions are broken, so treat it as a reference.)
  3. 3.Check wafer.space(This is where he submitted the design for the shared GlobalFoundries 180 nm run.)
  4. 4.Learn transport triggered architecture(The processor uses TTA, not a traditional RISC design — if you have never seen it, start here before writing Spade.)

Resources

Documentation, files and community threads for this build — we link straight to the original sources and never rehost the creator’s files.

KNOWN ISSUES

  • This is not a clone-and-build project — the repository is the HDL source, not a kit. You are designing your own chip, not assembling his.
  • Some instructions in his processor are broken because of his own mistakes (he says so at 29:16). If you use this as a reference, you will inherit those bugs unless you catch them.
  • The video does not say what he paid. Wafer.space lists 1,000 chips for $8,000, but that is the service's published price, not confirmation of what this specific run cost him.
  • Compiling the layout took about four hours even on a large rented gaming server, which he rented because of the deadline.
  • Manufacturing took 3-4 months. If you are used to next-day PCBs, the timeline here is foundry timeline, not hobby timeline.
  • This is a 180 nm chip at about 18-20 MHz, nowhere near a modern CPU. The point is that he designed it and a real foundry built it.

Do I need semiconductor lab access?

No. You design it at home in Spade, compile the layout on a rented server, and submit it to wafer.space. The foundry is GlobalFoundries, and the shared wafer service handles the rest.

What does the $8,000 get you?

Wafer.space lists 1,000 chips for $8,000 on a shared wafer run. The video does not say what he paid. He also mentions half and quarter size dies, which are cheaper, and Tiny Tapeout as a much cheaper way to start.

Can I use this HDL source directly?

The source is open on GitHub, but a few instructions do not work because of bugs he introduced, the SPI is broken and the UART is partly broken. Treat it as a reference and a proof of concept, not a drop-in design.

How long does the whole process take?

He had one month to finish the design before the tapeout deadline, the layout compile took about four hours on a rented gaming server, and manufacturing took 3-4 months.

Is this faster or cheaper than an FPGA?

No. That is not the point. It is a 180 nm chip running at about 18-20 MHz, and the point is that a real foundry made his own design. He says the correct way to test a design is on an FPGA first, which he skipped because of the deadline.

What licence does the source use?

He says the source code is open source and on GitHub, but the video does not name a licence. Check the repository before you fork or redistribute it.

Community builds

No community builds yet — be the first, we feature the best ones.

Discussion1

FROM THE COMPAREE TEAM

A shared wafer run lists 1,000 chips for $8,000, and it took about a month of design plus 3-4 months at the foundry. What would you put on your own chip?

CompareeTEAM12d ago

The video covers the whole path: the TTA idea, the Spade language, testing with cocotb, the open-source layout flow, the wafer.space submission and the first bring-up with LEDs on a breadboard. He saves the detailed processor design for a later video. The biggest takeaway is that the toolchain from HDL to packaged silicon is now open and reachable without a corporate cleanroom. The single thing to know before starting: this is not a weekend project, and some instructions in his design do not work; he says so plainly at 29:16.

Breaking Taps

Breaking Taps had never designed a chip or even used an FPGA before this. He gave himself one month to design a custom processor, compiled it on a rented gaming server, sent it to GlobalFoundries through wafer.space, and brought it up on a breadboard three to four months later.

Star the project on GitHub

DISCLAIMER

  • Comparee is not the author of the projects featured here. All rights to each project belong to its creator — every page links to the original source, and we never host creators’ files.
  • Information is provided without warranty and may become outdated as projects evolve. Prices are indicative bands only — always check the creator’s parts list for current costs.
  • Building and operating any project is at your own responsibility. Protective equipment, safe workshop practice and compliance with local regulations are the builder’s responsibility.