• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. CONFORMAL LEC-NON EQUIVALENT BLACK BOXES

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 65
  • Views 14688
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CONFORMAL LEC-NON EQUIVALENT BLACK BOXES

SWAROOP24X7
SWAROOP24X7 over 12 years ago

Hi all,

I'm very new to ASIC world.I have done lec b/w a RTL & a NETLIST.I have used hierarchial comparison for this.There are some un equivalent pointsI have got some few issues and doubts regarding those

1.Two modules were unequivalent because of unequivalent blackbox(that black boxes are done by tool).When I checked the diagnose point,it showed unknown.those black boxes are not the memory libraries even and got same name in both rtl and netlist.How this happens?Why tool blackboxed that instance?Will that un equivalent blackbox cause functional mismatch?How can I resolve those?

2.I had some Abort points,but I resolved those by {analyze abort -compare} command and setting multiplier implementation and making compare effort high.Now no Abort points are there.Were they the correct method to resolve those?

3.I also have 2 modules with un equivalent CUTPOINTS,and when I started searching in internet,I came to know that cuts are made by the tool for combinational feedback loops and those are tool defined and will not be a cause of functional mismatch. Can I neglect those unequivalent CUTPOINTS?

Can anyone help me out solving all these?Since Im doing LEC for the first time I face several problems and doubts.Please do reply......... 

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information