• 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. connecting a power pad to a macro pin

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 92
  • Views 15740
  • 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

connecting a power pad to a macro pin

gops
gops over 15 years ago
In my design, there is an One time programmable Memory (OTP).It has 4 power supply pins, VDD, VSS,VPP. The connection of VDD and VSS is similar to the VDD and VSS of the standard cells.( I have connected them with global net connect and sroute) But for VPP , I have used dedicated core power pads(VDD core), but the problem is I cant connect these pads to the VPP pin > My requirement is I need to connect the VDDCORE (cell type) pad named PotpVPP(instance name) to VPP pin of the OTP named tsmc_13_nv_otp(cell type) with u_otp(instance name) .Is this possible using global net connect? In short how can i connect the VDD pin of a particular power pad ( PotpVPP) to the macro pin named VPP
  • Cancel
Parents
  • gops
    gops over 15 years ago
    Hi,
     
    When I tried the commands I got the following warnings and errors.Please see below( copied from log file)
     
    <CMD> globalNetConnect VPP -type pgpin -pin VPP -singleInst u_sp/otp/u_otp0 -override -verbose

    0 new pwr-pin connection was made to global net 'VPP'.

    <CMD> globalNetConnect VPP -type pgpin -pin VPP -singleInst VPP -override -verbose

    0 new pwr-pin connection was made to global net 'VPP'.

    sroute -connect { blockPin padPin } -layerChangeRange { 1 6 } -blockPinTarget { nearestRingStripe nearestTarget } -padPinPortConnect { allPort oneGeom } -deleteExistingRoutes -checkAlignedSecondaryPin 1 -blockPin useLef -allowJogging 1 -crossoverViaBottomLayer 1 -allowLayerChange 1 -targetViaTopLayer 6 -crossoverViaTopLayer 6 -targetViaBottomLayer 1 -nets { VPP }

    Begin power routing ...

    **WARN: (SOCSR-1256): Net VPP does not have CORE class pad pins to be routed.

    Please check net list or port class.

    Net VPP does not have AREAIO class pad pins to be routed.

    Please check net list or port class.

    Number of Block ports routed: 0 open: 2

    End power routing: cpu: 0:00:00, real: 0:00:00, peak: 485.00 megs.


    thanks

    gopakumar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • gops
    gops over 15 years ago
    Hi,
     
    When I tried the commands I got the following warnings and errors.Please see below( copied from log file)
     
    <CMD> globalNetConnect VPP -type pgpin -pin VPP -singleInst u_sp/otp/u_otp0 -override -verbose

    0 new pwr-pin connection was made to global net 'VPP'.

    <CMD> globalNetConnect VPP -type pgpin -pin VPP -singleInst VPP -override -verbose

    0 new pwr-pin connection was made to global net 'VPP'.

    sroute -connect { blockPin padPin } -layerChangeRange { 1 6 } -blockPinTarget { nearestRingStripe nearestTarget } -padPinPortConnect { allPort oneGeom } -deleteExistingRoutes -checkAlignedSecondaryPin 1 -blockPin useLef -allowJogging 1 -crossoverViaBottomLayer 1 -allowLayerChange 1 -targetViaTopLayer 6 -crossoverViaTopLayer 6 -targetViaBottomLayer 1 -nets { VPP }

    Begin power routing ...

    **WARN: (SOCSR-1256): Net VPP does not have CORE class pad pins to be routed.

    Please check net list or port class.

    Net VPP does not have AREAIO class pad pins to be routed.

    Please check net list or port class.

    Number of Block ports routed: 0 open: 2

    End power routing: cpu: 0:00:00, real: 0:00:00, peak: 485.00 megs.


    thanks

    gopakumar
    • 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