Formal Verification
Formal Verification is a Linty scan engine that provides additional rules based on formal verification. These advanced rules help you detect bugs and vulnerabilities, improving the reliability and security of your IPs.
Formal Verification is available as part of Linty Ultra.
ROI
The real ROI of formal verification isn’t finding more bugs. It’s finding them earlier, with less effort.
In most hardware teams, critical corner-case issues are only discovered:
Late in simulation
During integration
After delivery, when the cost is highest
By that point, the cost of fixing them is already high.
What changes the economics is automation. When formal verification can be applied without weeks of manual setup or scarce expert knowledge, it stops being a specialist activity and becomes a continuous risk-reduction mechanism.
That means:
Fewer late-stage surprises
Less time spent debugging symptoms instead of causes
Higher confidence in new features before they reach customers
For leaders, the impact is straightforward:
Lower verification cost per release
Shorter feedback loops
More predictable delivery timelines
The strongest ROI doesn’t come from running more verification. It comes from making early correctness the default, not the exception.
Linty helps you generate and run formal verification checks in seconds.
That’s how teams scale quality without slowing innovation.
Workflow
Generate and run formal checks directly in VS Code with Linty HDL Designer. Watch the tutorial for more details:
Save these formal checks in your project repository (default location:
.linty/formal; this can be updated via thesonar.hdl.formal.pathsproperty).Integrate these formal checks into your continuous integration workflow. First, activate the formal verification rules tagged as formal in your quality profiles. Then, run a Linty scan.
Available Rules
Rule |
VHDL |
Verilog/SystemVerilog |
|---|---|---|
✓ |
✓ |
|
✓ |
✗ |
Custom Formal Checks
You can embed your own formal checks based on SymbiYosys into Linty. To do so, for each check:
Create a rule from the Linty formal check template and activate it in your quality profiles.
Get the ID of the rule you just created.
Add the following line at the top of your formal check
.sbyfile:# Linty check ID: my_rule. Replacemy_rulewith the ID of the rule you just created (everything afterhdlformal).Store the
.sbyfile in your project repository (default location:.linty/formal; this can be updated via thesonar.hdl.formal.pathsproperty).