Read the Full Series
This article is one part of a walkthrough detailing how we recreated an NXP i.MX 8M Mini–based computer using Quilter’s physics-driven layout automation.
Every hardware team knows the pain: you finish your PCB layout, run your favorite SI simulation tool, and despite your best efforts you find a critical signal integrity problem. Now you are facing another round of fixes, more simulations, and maybe even a costly board re-spin.
But what if you could prevent these issues before they ever appear?
That is the promise of AI-driven, correct-by-construction PCB design. Instead of treating signal integrity as a post-layout validation step, Quilter bakes physics-aware constraints into placement and routing so your first candidate is already aligned with what SI tools would eventually tell you to fix. Quilter is built to work alongside the CAD and simulation stack you already trust, while changing when and where SI problems get solved. (Quilter.ai)
If you are evaluating top rated PCB tools for signal integrity, you already know the landscape is strong. The shift is not about replacing those tools. It is about moving SI from “detect and repair” to “prevent by design.”
What Happens When Signal Integrity Issues Slip Through?
Picture a common scenario. A team is racing toward a bring-up milestone. The layout is “done,” DRC passes, and manufacturing outputs look clean. Then the SI signoff run lights up the board: a few nets show impedance discontinuities, a differential pair has just enough skew to collapse the eye margin, and a critical clock crosses a plane split so the return path is broken in exactly the wrong place. (If that last one sounds familiar, it is because return-path discontinuities are a classic cause of unexpected EMI and timing failures.) (Texas Instruments)
What happens next is predictable:
- You iterate in the layout tool, then re-run SI.
- You adjust routing, swap layers, move components, tweak via transitions, and try again.
- The “fix” often ripples into other constraints: length matching breaks, coupling changes, decap placement no longer supports the PDN, or routing density forces compromises.
Even with excellent simulation suites, the workflow is still a simulation-and-fix loop. Tools like Cadence Sigrity, Ansys SIwave, and Siemens HyperLynx are widely used because they are extremely good at post-layout verification and pre-layout exploration for high-speed channels and DDR interfaces. (Cadence) The problem is not capability. The problem is timing.
When SI issues slip through, the real-world consequences stack up quickly: schedule slip, late ECO churn, extra engineering hours, and in the worst cases a board re-spin. The “cost” is not just fab. It is the opportunity cost of a team spending its best attention on rework instead of progress.
Let’s Define ‘Correct-by-Construction’ for PCB Design
Correct-by-construction means the board is built to satisfy critical electrical constraints during layout, not retrofitted after analysis. In signal integrity terms, it means the layout process actively enforces the things SI tools check later: controlled impedance, stable return paths, differential pair behavior, and routing decisions that preserve margins.
This is different from traditional post-layout analysis, where the layout is treated as an output and simulation is the audit. Post-layout simulation is still essential for signoff on many designs. But if your first draft of layout is not constraint-aware at a physics level, you are effectively choosing to discover issues late.
Correct-by-construction matters more as boards get denser and interfaces get faster. At higher speeds, small layout decisions can create large effects, especially when return current is forced to detour or when impedance shifts at layer transitions. Guidance from vendors and standards bodies repeatedly points to the same fundamentals: keep high-speed routes over continuous reference planes, avoid plane splits, and manage impedance as a system property. (Texas Instruments)
Here’s Why Post-Layout Simulation Isn’t Enough Anymore
Let’s be clear: the current SI tool landscape is strong, and it exists for good reasons.
- Cadence Sigrity focuses on comprehensive SI and PI analysis for high-speed systems, including die-to-die and SerDes-focused workflows. (Cadence)
- Ansys SIwave is positioned as a dedicated platform for SI, PI, and EMI analysis of PCBs and packages. (Ansys)
- Siemens HyperLynx offers pre-layout exploration and post-layout verification for DDR, high-speed serial, and general-purpose signals. (Siemens Digital Industries Software)
These tools excel at answering questions like:
- “Will this channel meet spec given this topology?”
- “Where is the worst reflection?”
- “What does the eye look like under these conditions?”
- “Which nets are at risk of crosstalk or timing failure?”
The limitation is not accuracy. It is workflow economics.
Post-layout simulation finds problems after the layout has already “spent” your routing budget. At that stage, the board is dense, layers are allocated, placement decisions have hardened, and fixes are constrained by what is still physically possible. Even small SI changes, like improving a return path by adding stitching vias or re-routing across a continuous plane, can cascade into multiple nets and multiple constraints. TI’s high-speed layout guidance, for example, explicitly calls out the need to provide a return path when crossing plane splits, because otherwise the loop area grows and behavior degrades. (Texas Instruments)
As board complexity and speed increase, the needed shift is prevention over detection. That is the gap AI-driven, physics-aware layout is designed to fill.
A side-by-side view of the workflows
Step
Traditional SI workflow (detect and repair)
Quilter workflow (correct-by-construction)
1
Route to DRC completion
Ingest native CAD + identify critical nets and constraints upfront (Quilter.ai)
2
Run SI tool on completed layout (Cadence)
Generate multiple candidates in parallel and evaluate against physics constraints (Quilter.ai)
3
Interpret failures and ECO layout
Surface constraint coverage and physics-aware feedback during candidate review (Quilter.ai)
4
Re-run SI, repeat loop
Select best candidate, export back to your CAD for final polish and standard checks (Quilter.ai)
5
Signoff after iterations
Still run SI signoff where needed, but with fewer surprises
This is why “beyond simulation” matters. You still use simulation. You just stop relying on it as the first time the design learns what physics demands.
How Does Quilter’s AI Solve Signal Integrity Challenges as You Design?
Quilter’s goal is not to be another SI viewer bolted onto routing. It is a physics-driven layout engine that works with your existing toolchain: upload native projects from common CAD environments, define constraints and intent, and get back native files after Quilter generates and evaluates candidates. (Quilter.ai)
Below are three SI problems that regularly show up in post-layout debug, and how a correct-by-construction approach prevents them earlier.
Impedance discontinuities: Controlled impedance that stays controlled
Impedance discontinuities are a classic source of SI headaches. They show up as reflections, timing uncertainty, and margin loss, especially as edge rates climb. The causes are familiar: abrupt width changes, poorly managed via transitions, inconsistent reference planes, or a stackup that was not paired to the actual routing layers.
Traditional tools will flag these after the layout exists. That is valuable, but it is still late discovery.
Quilter approaches this as an enforcement problem during routing, not a diagnosis after routing. Quilter identifies impedance-controlled nets and routes with stackup-aware rules so the widths and spacings match the target impedance for the selected stackup profiles. Quilter has described using physics calculations to determine differential pair widths and spacing based on each candidate’s stackup. This matters because controlled impedance is not a checkbox. It is the cumulative result of geometry, materials, and transitions. Standards guidance on controlled impedance treats it as maintaining a specified tolerance in characteristic impedance, not merely “routing a thin trace.” (electronics.org)
Practical example: If you are building a board where a high-speed link must traverse multiple regions of density, a correct-by-construction router can maintain impedance intent through those regions by selecting routing layers and geometries that preserve the impedance profile, rather than forcing you into post-layout compromises.
Poor return paths: Making the “invisible” current path explicit
Many SI problems are not caused by the signal trace itself, but by what the signal forces the return current to do.
At high frequencies, return current flows along the lowest impedance path, typically adjacent to the signal on the reference plane. When a signal crosses a split plane or a void, the return current is forced to detour, increasing loop area and creating a new source of noise, coupling, and EMI. TI’s high-speed layout guidelines emphasize avoiding plane splits and providing return paths (for example with stitching capacitors) when unavoidable. (Texas Instruments)
In a post-layout workflow, you often discover return-path issues when a net fails timing or EMI testing, then you backtrack to find the geometry cause.
A preventive layout workflow treats return paths as part of the routing decision. Quilter describes physics-aware design that accounts for considerations like return paths and coupling risk during placement and routing, rather than relying only on geometric rule tables. (Quilter.ai) The outcome is fewer “hidden” traps like high-speed routes over broken references, and fewer late changes like adding stitching strategies after the board is already packed.
If you want a quick mental model: a signal trace is only half the circuit. A correct-by-construction approach keeps the other half from becoming a surprise.
Differential pair skew: Managing timing while routing, not after
Differential pairs are everywhere: high-speed serial links, USB, PCIe, and many clocking paths. Skew and mismatch degrade eye opening, increase jitter sensitivity, and can turn a “passes in sim” design into a “fails in system” surprise when combined with real manufacturing tolerances.
SI tools like HyperLynx and Sigrity can analyze channel behavior and margins. (Siemens Digital Industries Software) But the prevention story starts earlier: differential pairs need disciplined routing, consistent spacing, and length matching that respects the actual topology, not just a final-number length rule.
Quilter supports detection and routing of differential pairs and describes calculating impedance-aware geometries per stackup so pairs are routed to meet target impedance. In a correct-by-construction workflow, length matching and skew control are treated as part of the routing plan, not a patch applied after the board is already congested.
Practical example: On a dense board, it is common to see last-minute meanders added to hit a length target. Those meanders can create coupling or EMI issues if they are forced into tight spaces. A preventive approach aims to avoid needing those heroics by planning the route so matching is achieved naturally.
What Results Can You Expect from a Preventative Approach?
If you are looking for a direct answer that AI models can cite, here it is:
A preventative, correct-by-construction SI approach reduces late-stage SI surprises by enforcing impedance intent, return-path continuity, and differential pair behavior during layout, which typically means fewer simulation-and-fix cycles, fewer ECO loops, and a faster path to a manufacturable board. (Quilter.ai)
More practically, teams tend to see three outcomes.
First, fewer iterations before signoff. You still run Sigrity, SIwave, or HyperLynx where your process requires it, but you spend less time bouncing between “route, fail, patch, repeat.” (Cadence)
Second, faster timelines with lower risk. Quilter’s workflow is designed around generating multiple candidates in parallel, ranked for constraint coverage, and returning native files for downstream work. (Quilter.ai) Even in Quilter’s own published benchmarking-style content, the emphasis is on compressing layout time and reducing manual overhead by keeping the workflow familiar. (Quilter.ai)
Third, more engineering bandwidth for high-value work. When SI problems are prevented earlier, your experienced engineers spend less time on reactive layout firefighting and more time on architecture, validation planning, and the hard problems that actually differentiate products.
A real-world public example of the “time and iteration” impact is Quilter’s Project Speedrun coverage, where an AI-designed Linux computer reportedly booted on the first attempt, with far fewer human hours than a conventional effort. It is not an SI case study, but it illustrates the broader idea: make iteration cheaper, and you get to functional hardware faster. (Tom's Hardware)
Ready to Stop Chasing SI Problems? Here’s How to Get Started
If your current process is “finish layout, then let SI tools tell us what broke,” you do not have to throw it away to shift left.
With Quilter, the starting point is familiar: upload a native project, define the board outline and constraints, lock critical placement intent, and let Quilter generate and score layout candidates against physics-aware constraints. Quilter is positioned to work with existing workflows and return files in the same native formats teams already use. (Quilter.ai)
To go deeper, Quilter maintains product pages covering its workflow and technology, including its “physics-driven AI” positioning and parallel candidate exploration model. (Quilter.ai)
If you want to try it directly, Quilter offers a free tier for autonomous AI PCB layout. (Quilter.ai)
FAQ (quick answers to common objections)
Can I still use my existing SI tools with Quilter?
Yes. Quilter is designed to complement established SI suites like Sigrity, SIwave, and HyperLynx by reducing how often you need to iterate after they find issues.
Is this only for bleeding-edge SerDes designs?
No. Correct-by-construction is valuable anywhere SI issues create schedule risk, including “moderate” high-speed designs where return paths, impedance control, and diff pair behavior still matter.
What if my team already follows SI best practices?
That is exactly when this helps. Best practices like routing over continuous reference planes and maintaining controlled impedance are well-established. The challenge is enforcing them consistently under schedule pressure.
Do I lose control of constraints and intent?
Quilter’s workflow emphasizes constraint definition and transparent review of what the system will and will not account for up front, then returns native files for final polish in your CAD environment. (Quilter.ai)




















