• 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: use of extracted Spice netlist with Spectre?

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 16669
  • 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: use of extracted Spice netlist with Spectre?

dontpanic
dontpanic over 7 years ago

Hi! We are trying to switch to PVS-QRC for our extractions in 16nm TSMC, but we're having a hard time configuring the flow to generate "av_extracted" views. As as workaround, we would like to use instead the "Spice" netlist created by QRC. However, it seems it's not even in Spectre syntax. I was wondering: what would be the most straightforward way of using the QRC Spice netlist for postlayout simulation? I remember in the past having imported netlists into Cadence, and the process was a bit lengthly, and definitely user-error prone. Is there an easy way to use these netlists?

Thanks and regards, Jorge.

  • Cancel
Parents
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago

    Hi Jorge,

    You are right that QRC generated 'Spice' netlist is as the name suggests 'spice' syntax, but not Spectre syntax. You can create a cell view type called 'Spice' in Virtuoso (just like you create a new schematic), and copy-paste the contents of this extracted spice netlist in there. Remember to use the SUBCKT header generated automatically by Virtuoso, and not what is in the netlist. Then, you can use this 'spiceText' view in simulations using hierarchy editor.

    Regards,

    Saloni

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 7 years ago in reply to Saloni Chhabra

    Thank you so much for your reply, Saloni; your proposed solution works fine. Just one question: when I edit the spiceText view I get the error below. Do you know what could be the problem? For now I am doing all these experiments using the libraries and the setup of the "Quantus QRC UI 001: Working with the Setup Tab" RAK.

    Thanks and regards, Jorge.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dontpanic
    dontpanic over 7 years ago in reply to Saloni Chhabra

    Thank you so much for your reply, Saloni; your proposed solution works fine. Just one question: when I edit the spiceText view I get the error below. Do you know what could be the problem? For now I am doing all these experiments using the libraries and the setup of the "Quantus QRC UI 001: Working with the Setup Tab" RAK.

    Thanks and regards, Jorge.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago in reply to dontpanic

    Hi Jorge,

    What other views does this cell have? It seems that there is a verilog/verilogAMS/systemVerilog view which needs INCISIVE or XCELIUM (Cadence's digital/mixed-signal simulator) to be installed, so the view can be compiled. This is triggered even when you check & save the spiceText view. So, if you add this simulator to your installation path, this error should go away. Or, you can remove the views that you don't intend to work with.

    Even with this error, your spiceText view should still work..

    Regards,
    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 7 years ago in reply to Saloni Chhabra

    Hi Saloni. Indeed, adding XCELIUM to my startup setup took care of the error (and yes, the extracted view seems to work fine).

    Thanks so much for your help!

    Cheers, Jorge.

    • 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