• 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. Import verilog with VDD, VSS, VNW & VPW

Stats

  • Replies 9
  • Subscribers 127
  • Views 1975
  • Members are here 0

Import verilog with VDD, VSS, VNW & VPW

mzn ehv
mzn ehv 5 months ago

Hello,

I am importing a synthesized verilog gate level netlist in Cadence Virtuoso File -->Import --> Verilog.  After import I see that VDD, VSS, VNW & VPW ports are unconnected in the schematic view. I see a similar post (  Import Verilog ) where a perl script is used to to add in VDD and VSS connections to the verilog netlist. I have used it and it is connecting VDD and VSS but VNW and VPW are still floating. Is there a way by which all of the pins VDD, VSS, VNW & VPW could be connected. 
Thanks

  • Sign in to reply
  • Cancel
Parents
  • Volker T
    Volker T 5 months ago

    Please see my first reply that I have edited in the meanwhile. I had some trouble responding to your answer, so you find my latest reply there.

    I think the key point is to check if you use a tapless standard cell process (see last paragraph of my edited text).

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • mzn ehv
    mzn ehv 5 months ago in reply to Volker T

    Thank you very much Volker. The way you mentioned worked for all of the ports I wanted to connect (VDD, VSS, VNW & VPW). VNW and VPW are indeed connections to NWELL and PWELL. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Volker T
    Volker T 5 months ago in reply to mzn ehv

    Perfect.

    Unless you only need this solution for first simulation and you will later use a proper place and route tool that automatically adds the well tap cells, please don't forget to add them manually to also have them in your layout...

    If you do use a proper place and route tool, it will generate a new Verilog netlist for the routed design anyways, then including the well tap cells and all the additional buffers and antenna cells that the tool identifies to be required and inserted to get a working layout meeting timing constraints. Then, you should import that netlist instead of the pre-layout Verilog netlist and eventually re-simulate.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • mzn ehv
    mzn ehv 5 months ago in reply to Volker T

    Sure, will do that.
    Thank you very much once again.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • mzn ehv
    mzn ehv 5 months ago in reply to Volker T

    Hello Volker,

    When I simulated I found out that VPW and VNW do not have "Property Name" attribute. In that case how can we use netSet property?

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • mzn ehv
    mzn ehv 5 months ago in reply to Volker T

    Hello Volker,

    When I simulated I found out that VPW and VNW do not have "Property Name" attribute. In that case how can we use netSet property?

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • Volker T
    Volker T 5 months ago in reply to mzn ehv

    Again, I can only guess.

    Presumably, the most easy thing is to simply add a tap cell from your standard cell library into the test bench you use for simulation.

    If you are lucky, the tap cell has a VDD and VSS pin (or property name you can use in conjunction with a netSet for VDD / VSS), and then simply connects VPW / VNW to VDD and VSS, respectively, by itself, using a global net of whatever name.

    Otherwise, investigate the global net names of VPW and VNW (like e.g. "vpw!" and "vwn!") and assign suitable voltages to the two global nets in your test bench directly by e.g. two DC voltage sources.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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