• 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. Digital Implementation
  3. Special open on VCC, and GND while doing connectivity check...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13742
  • 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

Special open on VCC, and GND while doing connectivity check after using SRoute command

elgunidy91
elgunidy91 over 9 years ago

Hi all,

After doing sroute for pad pins only, the connectivity report gives the following violations:

Net VCC, Pin VDD_PAD.VCC: unconnected terminal at (696.070000,1633.320000) (732.870000,1636.800000)
Net VCC: special open at (265.350000,265.350000) (1371.450000,1423.350000)
Net GND, Pin VSS_PAD.GND: unconnected terminal at (696.070000,0.000000) (732.870000,3.480000)
Net GND: special open at (273.960000,213.250000) (1362.840000,1361.240000)

 Where: VDD_PAD: is the VDD pad, and the pin VCC is the only pin defined for it in the lef. The same for VSS_PAD.

My lef power, ground pins either for standard cells or core power pads is VCC, and GND, and also I defined my global nets in encounter to be the same names.

I used those commands for global connect:

globalNetConnect VCC -type pgpin -pin VCC -inst *
globalNetConnect VCC -type net -net VCC
globalNetConnect VCC -type tiehi
globalNetConnect GND -type pgpin -pin GND -inst *
globalNetConnect GND -type net -net GND
globalNetConnect GND -type tielo

My thoughts tell me that I can ignore the unconnected terminals warnings, because it will be connected using i/o filler cells to complete the power ring for pads.

Attached is a pic. for my chip with violation markers.

Any help how can I solve this !

Thanks you.

AbdUllah,

  • Cancel
  • Kari
    Kari over 8 years ago
    without having the design in my hands, it sounds like your theory is right. add the IO filler cells, rerun verifyConnectivity, and see if you still get the warnings.
    • 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