Formal property verification: A tale of two methods
David Vincenzoni, STMicroelectronics
EDN (January 15, 2018)
The Formal Property Verification (FPV) methodology often gets used in the last step of verification flow, after much time spent building a complex random constrained UVM (Universal Verification Methodology) environment where some corner cases are still not covered.
Other times, FPV is used when a silicon bug is found that was not raised during the dynamic verification phase.
In a wisely applied verification flow, FPV should be used in the first phase, as soon as the RTL (Register Transfer Logic) code is available.
Here we look at two examples of verification flow:
- A digital block verified through a UVM test bench
- Then, first verified using FPV flow.
To read the full article, click here
Related Semiconductor IP
- MACsec Engine optimized for 10Base-T1S/T1L applications
- Dual Port, Voltage Scaling Register File Compiler on GF22FDX+
- Single Port, Voltage Scaling, High Speed SRAM Memory Compiler on GF22FDX+
- I3C Full Controller / Target
- I3C HCI Host Controller
Related Articles
- Don't over-constrain in formal property verification (FPV) flows
- How formal verification saves time in digital IP design
- Formal Verification Has It Covered!
- Formal Property Checking for IP - A Case Study
Latest Articles
- An Agentic Python Framework for LLM-Driven UVM Testbench Synthesis with Closed-Loop Compiler Feedback
- Reconfiguring System-Level Protection Through Bounded Delegation in RISC-V MCUs
- SkipLane: Write-Once, Conflict-Free Accumulation for Zero-Skipping CNN Engines on FPGAs
- Priority-Aware Deficit Round Robin for AXI4 Bandwidth Fairness in ASAP-7nm Process
- Atik: A Shared-Mesh Transformer Accelerator for RISC-V