• 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. Digital Implementation
  3. PVS-LVS

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 90
  • Views 16621
  • 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

PVS-LVS

archive
archive over 13 years ago

Hi All

Im new to run pvs-lvs can i know how to run lvs and what are the input files required for it and how i have to check the results.

Im getting some warnings while running it

I used the following input files

postrouted netlist,cdl files,gds (merged all std cell and rams gds files),hcell.txt(contains all head cell names two times)

 

  • Cancel
  • Kari
    Kari over 13 years ago
    Are you running this command-line or through a gui? If command-line, please post the command you're using. Sounds like you have all the right inputs. I look at the .cls file for the results.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 13 years ago

    Hi Kari,

    Im ruuning by command line only

    pvs -64 -lvs -gds clu.gds.gz -ascrdb clu.db -top_cell clu -spice clu.spi -verilog clu_lvs_new.vg -hcell hcell.txt -source_cdl sub.cdl -layout_top_cell clu -source_top_cell clu -sum clu.sum DFM_LVS_CAL_N65_ALRDL_noU_13b.7m | & teelog_file

    this is the command im using , im seeing in .cls file for mismatches i found all filler cells as mismatched in layout.but i opend the .gds file in virtuso there im seeing filler cells what might be the reason for mismatch of fillers?

    what is the best way to analyse and debug the lvs reports?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 13 years ago

    Hi,

     When we output the physical verilog for LVS, we leave out the filler cells. I'm not sure what tool you're using to generate the physical verilog, but the command in EDI would look something like this:

     saveNetlist design.phys.v -phys -excludeLeafCell -excludeCellInst FILL64 -excludeCellInst FILL32 -excludeCellInst FILL16 -excludeCellInst FILL8 -excludeCellInst FILL4 -excludeCellInst FILL2 -excludeCellInst FILL1

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 13 years ago

    Hi Kari,

    Why we need to exclude the FILL*(*=16,8,4,2,1)  is there any specific reason?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 13 years ago

    Hi Kari,

    Im using in lvs command like -spice <block name>.spi what this switch used for, it generates spice netlist right , from layout or from schematic?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 13 years ago

    The FILL cells are physical-only cells, they are not connected to anything in the netlist.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Kari
    Kari over 13 years ago

    -spice <filename> should give you the spice file that PVS generates from the layout. I typically don't generate this, unless I'm trying to track down something specific to compare to the .cdl that was created from the physical verilog.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 13 years ago

    Hi Kari,

     Still i didnt clear how lvs works, when we are saving gds in EDI it also saves FILL* information right, and morover FIll* are used for implant and well continutiy right, if we exclude FILL in SaveNetlist Command then in scematic it wont save FILL information, but in layout still we will have the FILL information, in this case will it wont show any  mismatches for FILL(As it sees FILL information in GDS and it wont see FILL information in netlist i meen in schematic)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 13 years ago

    I'm somewhat new to the details of LVS myself, so I'm not sure how to explain it properly. I just know this is how we've always done it. I think it's because the fillers don't have any logical netlist connection. They continue the rails and wells, but can sort of be "flattened" from that point of view, if that makes any sense. Sorry I'm not very good at explaining this one!

     

    • Cancel
    • Vote Up +1 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