Home > Community > Blogs > Industry Insights > user view how to succeed with formal verification
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

Register | Membership benefits
Get email delivery of the Industry Insights blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

User View: How to Succeed With Formal Verification

Comments(0)Filed under: Industry Insights, DAC, Incisive, IEV, Formal Analysis, Cisco, IFV, Formal, Incisive Formal Verifier, formal verification, Incisive Enterprise Verifier, DAC 2011, Oski, Vigyan Singhal, Singhal

If you can speed your verification by 6X while finding more bugs, that's a pretty good deal. And that's exactly what happened when Cisco Systems turned to formal verification for a complex statistics block, according to a Design Automation Conference (DAC 2011) paper authored by Oski Technology, Cisco, and Cadence.

I did not attend the paper session, but I conducted the video interview shown below with Vigyan Singhal, CEO of Oski Technology, the same day at DAC. Oski is a verification services firm that specializes in formal model checking. They use tools including the Cadence Incisive Formal Verifier (IFV) and Incisive Enterprise Verifier (IEV). Oski also provides abstraction models that help formal tools achieve convergence.

In the video interview, Singhal discusses the adoption and acceptance of formal technology, why formal can offer faster verification than simulation, what types of blocks are best suited for formal, what types of blocks are not suited for formal, and how users can merge coverage results from formal tools and simulation. In particular, Singhal notes that IFV and IEV can generate coverage results with the same meaning as simulation coverage, a development he calls "extremely exciting."

We also talked about the DAC paper, which describes how what was projected to be an 18 month effort with dynamic simulation was cut to 3 months with IFV. The statistics block was exhaustively verified and 26 bugs were found, of which 10 would have been practically impossible to find with simulation, according to the authors.

Formal verification is not as difficult as many might think. "When you apply formal verification, you don't need a PhD, you need good problem solving skills," said Singhal, the only person in Oski who does have a PhD in formal verification. "Once you have the problem solving skills, the bandwidth and the resources, I think you're all set."

If video does not open, click here

Richard Goering

Comments(0)

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.