• 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. Need help in extracting a SPICE from a layout

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 3311
  • 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

Need help in extracting a SPICE from a layout

gaddan14
gaddan14 over 1 year ago

Hello 

I have a layout generated in Virtuoso for a simple ALU circuit. The layout was generated from a verilog code compiled by design_vision, with a floor plan and P&R created in INNVOUS and then imported in Virtuoso.
The design passed the DRC in Virtuoso in generic PDK 45.
Now I want to do the parasitic extraction for the layout and generate a SPICE netlist for the extracted version. 
The problem I am currently facing is, since I only have a layout view of the ALU and not the schematic, I am unable to run the LVS test and subsequently do the parasitic extraction for netlist generation. 
I used to extract parasitics and do the LVS for simple cells. This situation is new to me.
I thereby wanted to know if there are any procedure where I can directly extract a SPICE netlist from the layoutt?
Your help and guidance in this matter, as to what tools and processes I need to use, will be greatly appreciated.
  • Cancel
  • RobMan
    RobMan over 1 year ago

    You can use a Verilog top level netlist for PVS/Pegasus LVS.

    I assume it's a small digital design if intending to target a spice netlist. What simulator are you intending to use?

    Consider dspf or new i-dspf flow instead of spice.

    • 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