Home > Community > Forums > Functional Verification > CONFORMAL LEC-NON EQUIVALENT BLACK BOXES

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

 CONFORMAL LEC-NON EQUIVALENT BLACK BOXES 

Last post Mon, Sep 17 2012 12:03 PM by SWAROOP24X7. 0 replies.
Started by SWAROOP24X7 17 Sep 2012 12:03 PM. Topic has 0 replies and 1383 views
Page 1 of 1 (1 items)
Sort Posts:
  • Mon, Sep 17 2012 12:03 PM

    CONFORMAL LEC-NON EQUIVALENT BLACK BOXES Reply

    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......... 

    • Post Points: 5
Page 1 of 1 (1 items)
Sort Posts:
Started by SWAROOP24X7 at 17 Sep 2012 12:03 PM. Topic has 0 replies.