• 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. Custom IC SKILL
  3. Pin placement speed up

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 144
  • Views 11598
  • 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

Pin placement speed up

Dimitris Ant
Dimitris Ant over 4 years ago

Hi,

I have a skill code to create large layout arrays of my instances. So far i created sub arrays and use them to create larger arrays and in this way the procedure becomes very fast. However, i have a pin which is different for every cell in my array so i have to sweep the whole array and place it on every cell. Is there a way to instantiate these pins on the final array in a faster method or in a parallel way so the execution time becomes faster? I thought of a mosaic but i need to maintain connectivity information with the schematic.

For example i have a subarray with pin A<1:10>, i place 10 subarrays so i have  A<1:100> on the final array. When it comes to big numbers, X*X placement is time consuming.

  • Cancel
  • psill000
    psill000 over 4 years ago

    You should be able to get the pin name and shape using this database path 
    ~>instTerms~>term~>net~>name
    ~>instTerms~>term~>pins~>fig

    If you dont see the nets, you may need to do a Update Components and Nets

    Heres some more info on pins
    community.cadence.com/.../get-schematic-to-layout-bound-stdcells-for-array


    Paul

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to psill000

    I don't really see why this should be slow - if it's an array, I'd expect the pins to be regularly spaced. 

    Without seeing the code, it's rather hard to know why it would be slow. You can't place them in parallel (various parts of the system involved are are single-threaded), but this doesn't sound a particularly expensive task so I would expect it to be very fast if the code was written correctly.

    It may be easier to deal with this through customer support so that you can share your code and the data you're using so that we can give advice on how best to improve it.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 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