• 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-QRC flow and QRC_Advanced_Modeling licence

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 16630
  • 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-QRC flow and QRC_Advanced_Modeling licence

jdimov
jdimov over 8 years ago

Hi,

I am having problems setting up Quantus RC extraction using the files generated from PVS-iLVS

I am using Virtuoso IC6.17 64bit500.7
Quantus is ext-15.2.3 64bit
PVS is 15.16 64bit

I obtained the files for lvs and qrc through my vendor (tsmc 28nm)
So far I have managed to do drc and lvs and I think I compiled the files for qrc correctly too (I have generated the svdb folder and I have qrc techfile generated with Techgen I think ok (it's my first time doing this from scratch...))
I ran with two output formats the qrc_cmd.rsf using the qrc -cmd qrc_cmd.rsf

1. When I ran with SPICE output I got a licence error saying I am missing QRC_Advanced_modeling. What is that? I tried finding it in EXT help files, and on the internet and I just didn't find anything that made sense.
The error is LMF-02018
I do have a licence for Virtuoso_QRC_Extraction_XL, I checked with lmstat.

2. When I run using ?outputFormat "dfii" and ?extractedView "av_extracted" I get an error
 /opt/eda/cadence/ic06.17.latest/tools/dfII/bin/qrcToDfii exit with bad status

I'd appreciate if someone could help me out on this.

----

I also have another question.
For running LVS and lvs for RC extraction I got a big .tcl script which I modify (it contains switches and variables and sets a lot of ilvs commands in general).
I would like to make it more organized by creating a better file structure and preferably run it from Layout Editor through GUI.
Can someone give me an advice how should the file structure look like for pvs-lvs and quantus-qrc?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Search in the QRC documentation for "Advanced Modeling" and you'll find there are a few features needed for modeling technologies 32nm and below that require the QRCX320 Cadence Quantus QRC Advanced Modeling GXL Option license. That's what the first issue is complaining about.

    The second (and third) doesn't really have enough information to go on - I suggest you contact customer support (hopefully you'll have done that by now anyway).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jdimov
    jdimov over 8 years ago

    Thank you Andrew I found it. I also managed to sort things out with the second and third thing by carefully going over the needed files and how to instantiate them.
    I was also missing an extview.rul and extview.trp (or an icellmap.yaml) files in my provided PVS folders.
    I have found an icellmap.yaml file in the PDK for QCI and Calibre though ( they were the same and I hope it is a small cheat since I didn't have one in the PVS folders I obtained from my vendor), and Quantus PVS-RC check doesn't seem to mind (reports that all symbols are there and in order, I have just included the icellmap.yaml file with the input_db -icell_map_file command). (of course, I still don't have a licence for Advanced Modeling, so I can't get my extracted view, but at this point I think I at least got my files sorted)
    Should I perhaps be aware of some other things regarding the icellmap.yaml file for PVS?

    Regards,
    Jelena

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Hi Jelena,

    I probably would suggest you either contact the foundry or customer support - I'm not sure of the answer to this and it probably would need specific knowledge of the precise technology documents you're using. I'm not sure whether the extracted view problem is necessarily anything to do with the Advanced Modeling license, as I would expect that would control the extractor, not the output format.

    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