• 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. PVS Extraction Issue - Not finding PVS or QRC tab in Virtuoso...

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 125
  • Views 8149
  • 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 Extraction Issue - Not finding PVS or QRC tab in Virtuoso Layout to do parasitic extraction

vaishakprathap
vaishakprathap over 3 years ago

Hello,

I am using AMS 0.35um (C35B4C3) Process Hit Kit.

I finished a layout in Virtuoso Layout L. It does not have a schematic associated with it. I want to extract the layout and run simulation to ensure proper working.

The issue faced is that I do not know how to extract the layout. I do not find a PVS or QRC tab in Layout Window to do extraction. I went into the Launch-->Plugins tab but was unable to find a PVS tab.

The Cadence version is: IC6.1.8-64b.500.12

The Assura version is: sub-version 4.1_USR6_HF11

Checking for PVS home and version returns the following:

vaishakp@moose2(9-5:01am)$ env | grep PVS_HOME
PVS_HOME=/util-cse/cadence/ic/
vaishakp@moose2(10-5:04am)$ which pvs
/sbin/pvs

A deadline is approaching in a week and would be gratetful for any help.Kindly guide me on how to extract the layout without the schematic using PVS or QRC and run simulation on an extracted netlist....

  • Cancel
Parents
  • vaishakprathap
    vaishakprathap over 3 years ago

    In the AMS Hit Kit they show the paths that need to be set up for extraction. The snippet is shown below:

    ##########################################################
    # Cadence EXT / QRC path. Replace the /cad/cdsext15_26_s603 string by your installation path
    ##########################################################
    setenv PVS_HOME /cad/cdsext15_26_s603
    set path=($path $PVS_HOME/bin)
    if ( $?LD_LIBRARY_PATH == 0 ) then
    setenv LD_LIBRARY_PATH $PVS_HOME/tools/lib:/lib:/usr/lib
    else
    setenv LD_LIBRARY_PATH $PVS_HOME/tools/lib:${LD_LIBRARY_PATH}
    endif

    In my .aliases file we have the PVS_HOME path set up. Then why am I not able to see a PVS/QRC tab in CADENCE Virtuoso layout to do extraction? As shown in the screen shot there is no option to run Extraction under Assura Tab. But we ran DRC with Assura.....

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to vaishakprathap

    First of all, there's no need to set LD_LIBRARY_PATH for PVS. I initially wondered whether it was because you had /sbin in your path before the PVS binary directory (I assume) but that works OK because the detection is done by looking in all the paths in $PATH and checking for the presence of a few executables such as "lvsbrowser".

    What do you get if you type "which lvsbrowser" and "which pvsnvn" in the terminal which you started Virtuoso from?

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to Andrew Beckett

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to Andrew Beckett

    Both the commands show Error eval Unbound variable as shown in the snapshot

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to Andrew Beckett

    Shown below is the actual paths for the PVS_HOME:

    ##########################################################
    # Cadence EXT / QRC path. Replace the /cad/cdsext15_26_s603 string by your installation path
    ##########################################################
    setenv PVS_HOME /util-cse/cadence/ic/
    set path=($path $PVS_HOME/bin)
    if ( $?LD_LIBRARY_PATH == 0 ) then
    setenv LD_LIBRARY_PATH $PVS_HOME/tools/lib:/lib:/usr/lib
    else
    setenv LD_LIBRARY_PATH $PVS_HOME/tools/lib:${LD_LIBRARY_PATH}
    endif

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to vaishakprathap

    I didn’t ask you to type it in the Virtuoso window (CIW) because that would fail with an error because what I asked you to type was not a SKILL command. 

    Please type it in the terminal window as I asked. 

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to vaishakprathap

    I didn’t ask you to type it in the Virtuoso window (CIW) because that would fail with an error because what I asked you to type was not a SKILL command. 

    Please type it in the terminal window as I asked. 

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to Andrew Beckett

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to vaishakprathap

    Sorry for the misunderstanding. I typed the commands in the terminal from which I opened  Virtuoso as shown in the screenshot. Nothing seemed to happen....

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to vaishakprathap

    That's because you have run "ams_cds" in the foreground and so it's blocking the terminal - so typing anything in at the terminal won't do anything because the "ams_cds" program is running. That's pretty basic UNIX knowledge...

    Anyway, you'd need to run this in the terminal when you're not running "ams_cds" at the same time, or you have run it in the background by doing:

    ams_cds -tech c35b4 &

    (the ampersand backgrounds the job, giving the terminal prompt back again).

    Andrew 

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your time. I am new to UNIX enviornment. So pardon my limited knowledge. I had run the commands you mentioned from the directory from which I run CADENCE from. They also had returned "Command Not found" responses as shown in the screenshot below:

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to vaishakprathap

    OK, so you haven't set the UNIX PATH to include PVS - if it's not in your path, it won't appear in the UI.

    You referred to the path setting in your earlier post in the thread, but presumably that file is not being sourced. That's what you need to fix.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vaishakprathap
    vaishakprathap over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the quick response. Really appreciate the help.

    How do we know whether PVS is installed in that path?

    As I mentioned earlier the PVS_HOME path is already set as /util-cse/cadence/ic/. So I was assuming the PVS Tool must be in there.

    If I go inside /util-cse/cadence/ic/bin I can see 2 files pvs4dfii and pvs4dfiiver which has pvs names in it. Does this show PVS is installed?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to vaishakprathap

    Ah, I just realised what's wrong in what you've. You've set PVS_HOME to the IC installation. It needs to be to an installation of PVS (see http://downloads.cadence.com - you'll see that there is PVS191, PVS201 and PVS211). If you don't have it installed somewhere, you'll need to install it first, and point to the right software. That's your problem...

    Regards,

    Andrew

    • 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