• 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. Creating all pin symbol containing inherited power\ground...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 4172
  • 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

Creating all pin symbol containing inherited power\ground connections

saikatc
saikatc over 7 years ago

Hi,

I am working on Virtuoso, version IC6.1.7-64b.500.4. I am using inherited connections in the schematic. AFter parasitic extraction, I observe that the inherited connections are missing in the netlist. I know that it is not recommended to use inherited netlist. Still, is it possible to have a work around so that with the inherited connections we can have a symbol with all the power\ground pins?

thanks in advance.

Saikat Chatterjee

  • Cancel
Parents
  • saikatc
    saikatc over 7 years ago

    Hello Andrew,

    Sorry for not providing the details related to the extraction tool and inherited connections. Let me clarify them first.

    The extraction tool I am using, is PLaSMa. Here for extraction I am selecting StarRC. 

    Let me explain now the steps I followed. I drew a schematic where I used vdd_inherit, vdd1_inherit, gnd_inherit, gnds_inherit from STlib library. A symbol is generated from the schematic cellview, which I used in the testbench for the testing purpose.

    Once the circuit schematic is complete, I drew the layout. In the layout, I used explicit pins for the power rails. Once, the DRC and LVS results are clean, I went for extraction. 

    The extracted netlist is used while running the same testbench. I selected the 'extracted' option in ADE for that. Now, I see the simulation result is way too far from the actual output. While debugging, I realised that the extracted netlist cannot find vdd, vdd1 and gnds.

    Please let me know whether there are points which I still missed out. 

    Regards

    Saikat

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • saikatc
    saikatc over 7 years ago

    Hello Andrew,

    Sorry for not providing the details related to the extraction tool and inherited connections. Let me clarify them first.

    The extraction tool I am using, is PLaSMa. Here for extraction I am selecting StarRC. 

    Let me explain now the steps I followed. I drew a schematic where I used vdd_inherit, vdd1_inherit, gnd_inherit, gnds_inherit from STlib library. A symbol is generated from the schematic cellview, which I used in the testbench for the testing purpose.

    Once the circuit schematic is complete, I drew the layout. In the layout, I used explicit pins for the power rails. Once, the DRC and LVS results are clean, I went for extraction. 

    The extracted netlist is used while running the same testbench. I selected the 'extracted' option in ADE for that. Now, I see the simulation result is way too far from the actual output. While debugging, I realised that the extracted netlist cannot find vdd, vdd1 and gnds.

    Please let me know whether there are points which I still missed out. 

    Regards

    Saikat

    • 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