Home > Community > Blogs > Logic Design > is equivalence checking a must for signing off an fpga netlist targeting very large fpga devices
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 Logic Design blog (individual posts).


* 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: *

Is Equivalence Checking a MUST for signing off an FPGA netlist targeting very large FPGA Devices?

Comments(1)Filed under: Formal analysis, Logic synthesis, Equivalence checking, EC methodology

The majority of designers today use equivalence checking for netlist signoff prior to tapeout or ASIC vendor netlist handoff. As FPGA devices become larger and larger capable of tens of millions of gates, will equivalence checking become the norm rather than the exception?

From your prespective, what is preventing you today from running equivalence checking on your FPGA design. Is it, cost of tool ownership? flow issues/availability? Trusting your logic synthesis and place&route tool will not generate bad logic? Consequence of a bad FPGA due to logic bugs is not a big deal because you can always reprogram it? etc..

Please share your views with me on this subject. I have worked extensively in this formal verification area for FPGA in the past eight years.


Bassilios Petrakis


By TheLowRoad on September 22, 2008
What I am hearing is that this issue is all a matter of practical efficiency.  The practice of debugging the device after programming is just getting too big of a turnaround loop to be effective.  Equivalence checking at least eliminates the possibility of tool of script related failure prior to investing the energy in lab debug time.  It will be very interesting to see what the FPGA users on this forum have to say...

Leave a Comment

E-mail (will not be published)
 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.