• 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. How to handle multiple physical IO pins for a single port...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 91
  • Views 17261
  • 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

How to handle multiple physical IO pins for a single port?

archive
archive over 18 years ago

When I P&R a huge block, there are situations that I need to place several physical IO pins for a single top level port/net, usually, on different sides of the block for the purpose of easing the higher level connection.   FE looks like only understand one physical IO pin for each port/net and when I did trial route, I found only one physical pin per net(port) was hooked up.  In this way, it coundn't estimate the real routing congestion through the whole block when I have hundreds of such kind cases of multiple IO pins (for each net/port).

How can I let FE know that there are several physical IO pins for a signle port and therefore, it will connect all of them together when it route the block for me?


Originally posted in cdnusers.org by tzhou@micron.com
  • Cancel
Parents
  • mtran
    mtran over 16 years ago

    Was there a solution to this problem? I ran into the same issue with FE 6.2 USR2.

    FE does not route to the ,extra* pins from a DEF (5.5) generated from an abstract. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • mtran
    mtran over 16 years ago

    Was there a solution to this problem? I ran into the same issue with FE 6.2 USR2.

    FE does not route to the ,extra* pins from a DEF (5.5) generated from an abstract. 

    • 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