• 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. Custom IC Design
  3. LVS Analysis Error

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 16211
  • 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

LVS Analysis Error

dineshp
dineshp over 17 years ago

Hi,

I'm new to Cadence layout and was running a tutorial available in cdnshelp called the "Cell Design Tutorial". This tutorial is located in $CDSDIR/doc/celltut/celltut.pdf

It uses some Cadence supplied technology files and libraries available at $CDSDIR/tools.lnx86/dfII/samples/tutorials/le/cell_design/

The supplied library has a predefined a mux, including schematic and layout views. The LVS flow is to first extract connectivity from the layout by using the Verify -> Extract comand in Virtuoso. Next, LVS is performed between the extracted cell view and the schematic by running Verify -> LVS in Virtuoso. This results in an analysis error, i.e. LVS aborts, with the following log:

Begin netlist at:    Aug  6 11:20:04 2008
    view name list    = ("auLvs" "schematic" "cmos_sch" "netlist" "symbol")
    stop name list    = ("auLvs")
    library name    = "master"
    cell name    = "mux2"
    view name    = "schematic"
    globals lib    = "basic"
End netlist:    Aug  6 11:20:04 2008

Begin netlist at:    Aug  6 11:20:04 2008
    view name list    = ("auLvs" "extracted" "schematic" "symbol")
    stop name list    = ("auLvs")
    library name    = "master"
    cell name    = "mux2"
    view name    = "extracted"
    globals lib    = "basic"
global error:
( pfet symbol ) in library sample has been changed since it was last extracted.
global error:
( nfet symbol ) in library sample has been changed since it was last extracted.
    si: Netlist did not complete successfully.
End netlist:    Aug  6 11:20:04 2008

Comparison program did not complete. Check the log.

Can somebody please tell me how I can get rid of this? When I check the hierarchical tree, I find that the extracted layout consists of pfet and nfet ivpcells from the sample library. I'm guess its some sort of time stamping error. How can I force everything to be current? 

Really appreciate any help!

 

  • Cancel
  • dmay
    dmay over 17 years ago

    Looks to me like you'll need to Check&Save the pfet and nfet symbols in the sample library so the netlister will complete.

    -Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dineshp
    dineshp over 17 years ago

    Derek, Many thanks for replying.

    The sample library is a read only library. Is it necessary to actually copy this library somewhere and redefine everything to point to the new library? Is this some kind of bug?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dineshp
    dineshp over 17 years ago

    Could someone also please shed some light on the following!

    All the predefined cells in this particular tutorial use parameterised cells from a library called pCells. Nowhere is the samples library used in the actual layout, at any level of hierarchy. The explanation provided in the tutorial is that device occurences in the layout are identifed by being mapped to an instance of either an nfet or pfet ivpcell. An ivpcell is described as a special parameterized cell used by the verification program to display devices. It is my guess that these ivpcells reside in the samples library, and some mismatch with a time stamp causes the error.

    Where is the rule that points to these particular ivpcells (i.e. the ones in the sample library) defined please? How can I change it?

    Many thanks in advance. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dmay
    dmay over 17 years ago

    It sounds like this would be a bug in the Sample library. Either open up the permissions and do the check and save so the sample is good for everyone who wants to use it, or make a copy, but a check & save is a requirement to fix cells that need extraction.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dineshp
    dineshp over 17 years ago

    Thanks Allen, a few changes in the rule file to point to the corrrect cells fixed things.

    • Cancel
    • Vote Up 0 Vote Down
    • 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