• 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. Unplaced IO pins

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 91
  • Views 17546
  • 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

Unplaced IO pins

Greatrebel
Greatrebel over 15 years ago
Hi All, When I used checkDesign command in Encounter, I found there were a lot of unplaced IO pins. The number of unplaced IO pins is equal to the number of ports in my top-level design. I am wondering how to fix those unplaced IO pins or just leave them alone if it is not a big issue for P&R. Thanks in advanced
  • Cancel
  • Kari
    Kari over 15 years ago

     Are your IO pads placed yet? Once the IO pads are placed, I believe the pins should be right on top of the IO PAD pins.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Greatrebel
    Greatrebel over 15 years ago

     Hi Kari,

    I have already placed IO pads. I have a IO assignment file and use the command of loadIoFile to load that file. It works fine. But after that, when I type checkDesign, I still got a number of unplaced pins. I am wondering do I need to write something in IO assignment file for placing pins of top module,

     Thanks 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 15 years ago

     Hmmm. It's been a while since I've done a top-level design. Are the number of unplaced pins equal to the number of signal IOs? If you go on through placement and route, do these pins get placed later or do they cause routing issues?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Greatrebel
    Greatrebel over 15 years ago

     Those unplaced pins are still there after routing, but I did not get an error for routing. The number of unplaced pins is not equal to the number of signal IOs but the port number of top module, since some ports have more than one bit.Does these unplaced pins really need to be clean out?

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 15 years ago

     If Verify Geometry and Verify Connectivity are clean, and your signoff DRC/LVS are clean, then you're probably fine, but it would always bother me where these things are coming from. The only thing I can suggest is to look at the names of the unplaced pins, see if they make sense in your netlist, or if they should be placed on an IO pad. Maybe these are leftover in a floorplan after the netlist got changed? Are they actual physical shapes, or just logical pin markers? Do they connect to any nets?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Greatrebel
    Greatrebel over 15 years ago

     hi  Kari,

     

    I checked the report from checkDesign. All those unplaced IO pins are the pins of top module in the netlist. They have been connected to IO instances directly in the netlist. In PnR view, I saw those pins are bonded with IO instances' pins like PAD. Each of the unplaced pins are just shown as a yellow triangle.

     

    thanks

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 15 years ago

     I think everything will be fine then. :-)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Greatrebel
    Greatrebel over 15 years ago

    Hi Kari

     Thank you very much!

    • 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