• 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. How to create "extracted netlist file"

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 4687
  • 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

How to create "extracted netlist file"

fatcat1206
fatcat1206 over 9 years ago

Hi All

I am trying to update the binding in the layout view with LVS results, in order to make the view Layout-XL compliant.

When reading the Cadence document, 2 files (.ixf and .net files) are needed as mentioned below.

"Note: PVS creates a .ixf cross-reference file in the svdb directory of the PVS run directory when using the PVS Create QRC Input Data option.

Note: PVS creates a .net extracted netlist file in the svdb directory of the PVS run directory when using the PVS Create QRC Input Data option."



For the .ixf file, it has been generated when I run the LVS and enable the “Create Quantus QRC Input Data”
 

But there is no .net file as mentioned by the document.

On the other hand, it has also been mentioned in the document
 

"If you run PVS in LVS mode with the -qrc_data argument specified, the extracted netlist gets created in the form of a .spi file in the same directory as the .ixf. The .spi file provides a normalized output for QRC and may not be useful for generating the binding file required by Update Binding. Therefore, you must ensure that you set lvs_keep_data to yes in your lvs.pvl rule file so that the extracted netlist output file is a .net file, which can be read by the Update Binding form."

But I did not find the “lvs_keep_data” in the lvs.pvl file.

Does any one have a clue how to get the "extracted netlist file", or has a work around to update the binding according to the LVS results.

Best Regards


Yi

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hi Yi,

    Good to see you on Monday - sorry for not responding soon - the tour continued! 

    Anyway, what you have to do is create a text file (e.g. "extra.pvl") and put in this file:

    lvs_keep_data yes

    Then on the Rules page of the PVS LVS form, add this extra file as an additional rules file.

    I did this, and together with the generate QRC data, I got both the .ixf and .net file, and was able to use those for Update Bindings (I put together a small example on the plane home tonight, and it worked a treat).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hi Yi,

    Good to see you on Monday - sorry for not responding soon - the tour continued! 

    Anyway, what you have to do is create a text file (e.g. "extra.pvl") and put in this file:

    lvs_keep_data yes

    Then on the Rules page of the PVS LVS form, add this extra file as an additional rules file.

    I did this, and together with the generate QRC data, I got both the .ixf and .net file, and was able to use those for Update Bindings (I put together a small example on the plane home tonight, and it worked a treat).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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