EDA & Design Tools

last updated 2026-08-31
Assessment draft · unreviewed
Viability
3/5
Drivers
3/5
Novelty
3/5
Diffusion
2/5
Impact
4/5

Timing Soon (2-5yr) · Read Fairly rated

EDA is the software layer that turns design intent into manufacturable silicon, and the 2026 research front is rebuilding it around large language models, differentiable optimisation and surrogate models, with benchmark results showing real gains in design turnaround but verification quality still well short of sign-off.

Summary

Electronic design automation (EDA) covers the tool chain between a designer’s intent and a manufacturable chip: writing register transfer level (RTL) code in Verilog, SystemVerilog or VHDL, verifying it, synthesising it, placing and routing it, estimating power and timing, laying out analog blocks, and exploring architectures before any of that is committed. Each of those stages is currently a mix of solver-based algorithms, hand-tuned heuristics, slow simulators and large amounts of manual engineering judgement.

The current wave of work attacks this from three directions. First, LLMs as code and property generators: RTL generation with tool assistance and curated datasets, VHDL generation and evaluation infrastructure built by automatically converting Verilog designs and testbenches into executable VHDL benchmarks validated with VUnit/GHDL, hierarchical formal verification via generated SystemVerilog Assertions, and full analog flows that carry design intent through topology synthesis, sizing and constraint-driven layout. Second, learned or differentiable replacements for expensive inner loops: source-level module power estimation without simulation at inference time, Gaussian-reparameterised differentiable operator scheduling for compilation and high-level synthesis, and neural surrogates plus a decision-tree quality gate for signal-integrity-compliant PCB interconnect design. Third, modelling tools for physical realities the existing tools were never built for: inter-die routing in 2.5D and 3D FPGAs, modelled by extending the open-source VTR/VPR flow with HSPICE circuit models of a 7 nm die on a 45 nm interposer, and embodied plus operational carbon as a first-class architectural metric.

The parameters that decide whether any of this matters are unglamorous. For generative tools, everything hinges on whether the output is checked by a real tool rather than scored by string similarity: compile rate, proof success, vacuity, mutation coverage and formal core coverage are the numbers that separate a demo from usable automation. For surrogate tools, it is whether accuracy holds across configurations and workloads outside the training distribution. For both, the binding constraint is training and evaluation data, which is why several of these papers are data synthesis pipelines rather than models. And for anything touching a real tape-out, the question is whether the result can be signed off, which none of the supplied sources demonstrates.

Evidence base

Open questions


Assessment drafted 2026-08-31 from up to 18 KB sources using the technology-scorecard framework; scores are a draft read pending review.

Recent mentions

Frontier questions