• 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. sroute options for connecting power domain ring to power...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 92
  • Views 15015
  • 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

sroute options for connecting power domain ring to power pad

archive
archive over 17 years ago

Hi
   
    i am trying to use some of the options of sroute command, is there any option where i can connect the Power ring of a power domain to the Power Pad.
    

thanks
deepak.


Originally posted in cdnusers.org by deepak
  • Cancel
  • archive
    archive over 17 years ago

    Hi Deepak,

    Have you tried using the GUI:
    Route->Special Route
    Enter the power net name
    Select only the Pad Pin option
    Set other options as desired

    The core-facing pin of the IO cell needs to be defined as CLASS CORE.

    - Kari


    Originally posted in cdnusers.org by Kari
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • deeps
    deeps over 16 years ago

     Hi Kari,

       I have also tried the same way as you have told but did not work, as i wanted a list of pads to be connected to the power domain ring but as the pin names for all the pads were VDD & VSS i was not able to connect the list of selected pads alone using the sroute command,

      so we have to first clear all the golbal net connections & create the ring for the power domain with a different global net (VDD1 & VSS1 ) then define the globalnetconnect command with -pgpin option & specify the pin as VDD & then provide the list of instances (pad instance ) to be connected. 

        This is how it works now.

     

    any way thanks for your suggestions

     

    regards

    deepak. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Willbe
    Willbe over 16 years ago

     hi deepak,

     

    I'm new in cadence tools and i  have the same problem and don't know how to lose it. Please can you send me your configuration's file, so that i can do the configuartion by my side?

    Thanks,

     regards,

     

    Eric

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • deeps
    deeps over 16 years ago

     Hi Eric,
        I am not sure about the configuration file your are asking about,

            I had some problem in connecting the power domain rings to a list of power pads (different source ), so what I did is,

        Listed all the instances of the pads that needs to be connected to the power domain ring,
        Defined the global nets for the tool to understand the logical connectivity (Power domain net names will be different to that of default domain net names)
        Used sroute command to connect the power ring to the selected power pad.


    Example:
    ClearGlobalNets
    set power_nets {VDD1  VDD2}
    set GND_nets {VSS1  VSS2 }

    set pad_inst_VDD1 { __PAD_981  __PAD_1148 __PAD_1130 __PAD_1096 }
    set pad_inst_VDD2 { __PAD_1004 __PAD_994 __PAD_967 __PAD_933 }
    set pad_inst_VSS1 { __PAD_1156 __PAD_1155 __PAD_1133 __PAD_1132}
    set pad_inst_VSS2 { __PAD_1005 __PAD_995 __PAD_966 __PAD_934 }

    foreach i $pad_inst_VDD1  {
    globalNetConnect [lindex $power_nets 0] -type pgpin -pin VDD -singleInstance $i
    }
     
    foreach i $pad_inst_VSS1  {
    globalNetConnect [lindex $GND_nets 0] -type pgpin -pin VSS -singleInstance $i
    }

    sroute -deleteExistingRoutes -noBlockPins -noPadRings -noCorePins -noStripes -padPinAllGeomsConnect -padPinMinLayer 4 -padPinMaxLayer 4 -jogControl { preferWithChanges differentLayer } -nets {VDD1 VDD2 VSS1 VSS2}



            the above script will connect the list of instances to the defined global nets.

    Regards
    Deepak.

    • 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