• 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 run LVS without v2lvs

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 15703
  • 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 run LVS without v2lvs

Hypnus
Hypnus over 10 years ago

Hi,

I am designing a mixed signal circuit, while for the digital part I could run LVS directly using .v file from encounter with the standard cell cdl file, but for a mixed signal circuit, and I don't have v2lvs from calibre, we have only assura to run everything, how could I run the LVS......please give me some tips, please...

Thank you really much!
Bison

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

    OK, I did some experiments and read the documentation for you...

    In the "rsf" (run-specific file), you need to use this kind of construct:

    avCompareRules(
    schematic(
    netlist( cdl "/export/home/myuser/support/playGPDK/file1.cdl" )
    netlist( verilog "/export/home/myuser/support/playGPDK/file2.v" )
    )
    bindingFile("/export/home/myuser/kits/gpdk090_v4.6/assura/bind.rul")
    )

    If you run $ASSURAHOME/tools/bin/cdnshelp and then search for avCompareRules you'll find relevant references. In particular there's a sectionin the Assura Physical Verification Command Reference which details the syntax of the options for the schematic block including the netlist statement.

    There is also a general section in the "Assura Physical Verification User Guide" on "Comparing Layout and Schematic Netlists", and a subsection in that called "Directing the LVS Run with Compare Rules", which explains it pretty well. Given that there are not huge numbers of Assura manuals, finding the information is quite straightforward.

    I also generated the example above using the UI for Assura LVS within Virtuoso.

    Regards,

    Andrew.

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

    OK, I did some experiments and read the documentation for you...

    In the "rsf" (run-specific file), you need to use this kind of construct:

    avCompareRules(
    schematic(
    netlist( cdl "/export/home/myuser/support/playGPDK/file1.cdl" )
    netlist( verilog "/export/home/myuser/support/playGPDK/file2.v" )
    )
    bindingFile("/export/home/myuser/kits/gpdk090_v4.6/assura/bind.rul")
    )

    If you run $ASSURAHOME/tools/bin/cdnshelp and then search for avCompareRules you'll find relevant references. In particular there's a sectionin the Assura Physical Verification Command Reference which details the syntax of the options for the schematic block including the netlist statement.

    There is also a general section in the "Assura Physical Verification User Guide" on "Comparing Layout and Schematic Netlists", and a subsection in that called "Directing the LVS Run with Compare Rules", which explains it pretty well. Given that there are not huge numbers of Assura manuals, finding the information is quite straightforward.

    I also generated the example above using the UI for Assura LVS within Virtuoso.

    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