BRENNEN

Industries / Technology / Electronics and semiconductors

Chip design

Chip design turns what a chip must do into a drawing a factory can make: the architecture, the logic, the checks that it is right, and the placing and wiring of transistors with software called EDA (electronic design automation).

7

Milestones achieved, from 1973 to 2020.

3

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1973

    Circuits simulated before building

    Laurence Nagel and Donald Pederson at UC Berkeley published SPICE, a program that predicts the voltages and currents in a circuit, so designers could test a circuit on a computer before making it. An IEEE Milestone plaque says it became the worldwide standard simulator for integrated circuits.

    Lessona tool that is easy to obtain and teach can become the standard for a whole trade.,_1969-1970).

    www2.eecs.berkeley.eduethw.org

    Credit

    Laurence W. Nagel and Donald O. Pederson, UC Berkeley

  2. 1979

    Design separated from the factory

    Carver Mead and Lynn Conway wrote "Introduction to VLSI Systems", whose simple layout rules let people outside chip factories design chips, and Conway's MPC79 service made a dozen universities' designs on shared wafers. From 1981 the MOSIS service at USC's Information Sciences Institute ran this multi-project wafer model, in which many designs share one wafer and each customer pays only for its own area; it has since made over 60,000 designs.

    Lessonsharing a wafer cut the cost of a first chip enough that students could make one.

    ai.eecs.umich.eduisi.edu

    Credit

    Carver Mead (Caltech), Lynn Conway (Xerox PARC); USC Information Sciences Institute (MOSIS)

  3. 1987

    Foundries make fabless possible

    Morris Chang founded TSMC as a dedicated foundry, a factory that makes chips designed by other companies, so firms could design and sell chips without owning a factory; such firms are called fabless. TSMC says it made 12,682 different products for 534 customers in 2025.

    Lessononce anyone could rent factory time, a chip company could spend its money on design instead of on a factory.

    computerhistory.orgtsmc.com

    Credit

    Morris Chang and TSMC, set up with Taiwan's government research institute ITRI

  4. 1988

    Hardware languages and logic synthesis

    In the 1980s designers moved from drawing logic diagrams to writing a chip's behaviour as code in hardware description languages, such as Verilog from Gateway Design Automation and VHDL from a US Department of Defense programme. In 1988 Synopsys announced Design Compiler, which turns that code into a list of logic gates a factory can build, a step called logic synthesis.

    Lessonsynthesis became common only once tools arrived, around 1990, to check timing and to prove that two versions of a circuit do the same thing.

    shmj.or.jpcomputerhistory.orgdac.com

    Credit

    Phil Moorby (Verilog); Aart de Geus and the Synopsys team

  5. 1994

    The Pentium division bug

    Intel's Pentium processor gave wrong answers for some divisions because entries were missing from a lookup table on the chip. Mathematician Thomas Nicely reported it in October 1994, and in December Intel agreed to replace the chips, at a cost of $475 million.

    Lessontesting a sample of inputs can miss rare errors; Intel's John Harrison wrote that the episode "considerably" raised investment in formal verification, which proves a design correct for every possible input.

    righto.comcl.cam.ac.uk

    Credit

    Thomas Nicely (found it); Intel

  6. 2010

    An open instruction set

    A team at UC Berkeley started RISC-V, an instruction set (the list of basic commands a processor understands) that is an open standard anyone may build on without paying royalties. Outside firms use it routinely: Nvidia said in October 2024 that 10 to 40 of its own RISC-V cores manage each of its graphics chips.

    riscv.orgtomshardware.com

    Credit

    Krste Asanović, Yunsup Lee and Andrew Waterman, with David Patterson, UC Berkeley

  7. 2020

    Open design kit, shared shuttles

    Google and SkyWater published the process design kit for SkyWater's 130 nm process under an open-source licence; a design kit (PDK) is the set of files that tells design tools what a factory can make. With free tool flows such as OpenROAD and a Google-funded shuttle that made 40 public designs at no cost in 2021, a person could take a design to a real chip without paying for tools.

    Lessonwhen Efabless, which ran the shuttles, shut down in March 2025, chips in progress were stranded; by 2026 Tiny Tapeout was sending designs to three factories so the open route no longer rests on one company.

    github.comdesign-reuse.comopenroad.readthedocs.iotinytapeout.comtinytapeout.com

    Credit

    Google and SkyWater Technology; Efabless (shuttles); the UC San Diego-led OpenROAD team

Watch for

  1. Autonomous verification agent

    Cadence says the top level of its ChipStack AI Super Agent reads a specification, writes the RTL (the code that describes a chip's logic), plans and runs the checks, and fixes bugs without step-by-step prompts, and that it makes RTL checking over 40 times faster, cutting a five-week loop to under a day. No customer is named.

    Achieved whena customer outside Cadence publishes measured before-and-after results on its own design, or an independent benchmark reproduces the speed-up.

    design-reuse.com

    Claimed by

    Cadence Design Systems, June 2026

  2. Agentic debug with AMD

    Synopsys says two agent workflows built with Microsoft find and fix design bugs and finish chip layouts with little human help, that early evaluations cut debug time by 25 to 40%, and that AMD is evaluating them. The release does not say who ran the evaluations.

    Achieved whenAMD or another named user reports the cut on a production design and says how it was measured.

    news.synopsys.com

    Claimed by

    Synopsys, July 2026

  3. CPU designed by an agent

    Verkor says its Design Conductor agent took a 219-word requirements document to a finished layout of a RISC-V processor in 12 hours with no human help, meeting timing at 1.48 GHz in ASAP7, a teaching kit that models a 7 nm process but is not used to make real chips. A Meta researcher's personal replication, posted in May 2026, also stops at the layout file.

    Achieved whenan agent-built processor is made in a real process and someone other than its builders measures it working.

    arxiv.orggithub.com

    Claimed by

    Verkor, February 2026

Open

  1. 01

    Agent-designed tile proven in silicon

    Give an AI coding agent a one-page spec for a small block, such as a serial-port transmitter or an 8-bit multiplier, and have it produce a Tiny Tapeout tile (one design slot on a shared community chip) with no human edits to the design, tests or tool settings. Submit it to a shuttle, and when the chips arrive, test them against acceptance tests that a second person wrote beforehand and kept from the agent.

    The brief
    Credit · unclaimed
  2. 02

    Same spec, ten agent runs

    Run one open spec-to-layout agent flow at least ten times with the same spec, design kit, tools, settings and model version, and publish how much the results vary: pass or fail, top clock speed, area, power, hours taken and cost.

    The brief
    Credit · unclaimed

Open 01 · the brief

Agent-designed tile proven in silicon

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

Give an AI coding agent a one-page spec for a small block, such as a serial-port transmitter or an 8-bit multiplier, and have it produce a Tiny Tapeout tile (one design slot on a shared community chip) with no human edits to the design, tests or tool settings. Submit it to a shuttle, and when the chips arrive, test them against acceptance tests that a second person wrote beforehand and kept from the agent.

Why it is still open

Public results for agent-designed chips stop at the layout file. Verkor's agent ends at a "tape-out ready" layout; Build-A-Chip-Bench, a benchmark from ChipAgents with Nvidia (October 2026), also ends at the layout, and its best agent scores 16.6% overall; NYU's 2023 chip QTcore-C1 was written with GPT-4 but "co-architected" by a human engineer; and the Siliconsmith project, which connects coding agents to Tiny Tapeout, says it "cannot make a chip yet".

arxiv.orgsemiengineering.comarxiv.orggithub.com

Built with what exists

a coding agent such as Claude Code running an AI model such as Claude Fable 5.2 (the Note "Three working devices" covers the same question for circuit boards); Tiny Tapeout's Verilog template, which builds the layout with the open LibreLane flow and runs a precheck on GitHub; cocotb and Icarus Verilog for tests; a Tiny Tapeout demo board and its MicroPython SDK to test the finished chips.

github.com

  1. First step

    Write the spec and its hidden tests, run the agent, and submit before Tiny Tapeout's TTSKY26e run closes on 30 November 2026 or TTGF26c closes on 7 December 2026.

    tinytapeout.com

  2. Done looks like

    the git history shows no human edits to design, test or flow files; the full agent log is public; the tile passes Tiny Tapeout's precheck and is made on a shuttle; and it passes every hidden acceptance test on at least three delivered chips.

Open 02 · the brief

Same spec, ten agent runs

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

Run one open spec-to-layout agent flow at least ten times with the same spec, design kit, tools, settings and model version, and publish how much the results vary: pass or fail, top clock speed, area, power, hours taken and cost.

Why it is still open

Verkor and the outside replication each report one set of results, and a September 2026 SemiWiki article lists repeated independent runs, compared as distributions, among the evidence still to be shown before engineers trust agents with a tapeout.

semiwiki.comgithub.com

Built with what exists

OpenROAD flow scripts with the ASAP7 kit (or the open SKY130 or IHP SG13G2 kits); Yosys; Verilator or Icarus Verilog with cocotb; a coding agent such as Claude Code; the tanfer-meta/vercore repository as a starting harness; Python for the statistics.

  1. First step

    Fix one short processor spec and the tool versions, then run the flow twice to measure the time and cost of one run before committing to ten.

  2. Done looks like

    at least ten logged runs from one fixed setup; a table and chart of each measure with median and spread; every log public; and a second person who reruns two of the runs gets results inside the reported range.