• 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. VDD of padring not connected to VDD of core ring via power...

Stats

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

VDD of padring not connected to VDD of core ring via power pad

maxb
maxb over 16 years ago

Hello,
I am having trouble connecting the VSS and VDD nets of the padring with the core VDD/VSS. I have created a core power ring, and after running sroute the power pads are connected to the VSS and VDD of the padring, and they are also connected the the core ring (on the CLASS CORE ports VDD/VSS of the power pads).

But if I run verifyConnectivity I get violations: "Special Wires: Pieces of the net are not connected together." The reason for this warning seems to be that SoC Encounter does not see that the different VSS/VDD ports of the power pad are connected internally.

A quick check by manually connecting the pad ring VDD with the core ring VDD (using a wire, not via the power pad) makes the violation disappear.

What could be the reason that SoC Encounter does not see the connection between the different VDD ports of the power pad?

The VDD and VSS nets are connected logically using globalNetConnect.

Here is a snippet of the LEF for the power pad:

MACRO PWC_VD_RCD_12V
    CLASS PAD POWER ;
    PIN VDD
        DIRECTION INOUT ;
        USE POWER ;
        PORT
            CLASS CORE ;
            LAYER M2 ;
                RECT 4.71 119.9 48.285 120 ;
        END
        PORT
            LAYER M5 ;
                RECT 0 115.27 0.1 118.025 ;
                RECT 49.9 115.27 50 118.025 ;
        END
    END VDD

  • Cancel
  • Kari
    Kari over 16 years ago

     Hi,

    Your guess is correct - verifyConnectivity only sees what is in the LEF files (the whole layout is not visible here). So since in the LEF there is no connection between the padring and the core pin, it's flagged as "not connected together". But you know that is not really the case (assuming the layouts are correct), so you can ignore this violation.

    - Kari

    • 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