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
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
- ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
- MIPI SoundWire I3S Peripheral IP
- ML-DSA Digital Signature Engine
- P1619 / 802.1ae (MACSec) GCM/XTS/CBC-AES Core
Related Blogs
- Why Aerospace Semiconductor Designers Are Taking a Page from Their Automotive Friends
- What are AI Chips? A Comprehensive Guide to AI Chip Design
- What Are Digital Twins? A Primer on Virtual Models
- Formal verification best practices: investigating a deadlock
Latest Blogs
- Tidying Up: FIPS-Compliant Secure Zeroization for OTP
- Accelerating Your Development: Simplify SoC I/O with a Single Multi-Protocol SerDes IP
- Why What Where DIFI and the new version 1.3
- Accelerating PCIe Gen6 L0p Verification for AI & HPC Designs using Synopsys VIP
- ML-DSA explained: Quantum-Safe digital Signatures for secure embedded Systems