Are Formal Apps a Trojan Horse?
Mythology tells us that the Greeks finally sacked Troy after a 10-year siege by being invited into the city hidden inside a now famous wooden “Trojan” horse. Similarly, formal verification (FV) has threatened to become mainstream for as long as I can remember. However, could it be that “formal apps” are the disguised guest that finally see us realize the Kathryn Kranen prediction that "formal will dominate verification"?
Formal apps are automated applications to achieve specific verification tasks such as verifying that signals correctly cross clock domain boundaries, that post-reset X’s do not cause functional issues, or that a SoC (system-on-chip) correctly implements signal connectivity as specified in a spreadsheet or an IP-XACT description. In this blog I investigate such apps and whether they are leading us to full formal adoption.
To read the full article, click here
Related Semiconductor IP
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
Related Blogs
- Power, Not Area: Why Edge GPU Design Is Entering a New Era
- Area, Pipelining, Integration: A Comparison of SHA-2 and SHA-3 for embedded Systems.
- NXP's Market Figures Are Wrong, Says Future Horizons CEO
- Product managers are the unsung heroes in startups
Latest Blogs
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Manufacturing Intelligence: Turning EDA Data into Trusted Action
- Execute-in-Place: Getting More from Embedded NVM
- Rethinking RTL flows with AI-driven hybrid formal verification
- Arm and NVIDIA: Building the trusted compute foundation for the agentic AI era