• 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. Skill script for uniquification of cells

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 142
  • Views 14029
  • 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

Skill script for uniquification of cells

Paramjeet
Paramjeet over 6 years ago

Hi,

Can someone share the skill code for uniquification of cells of cadence library with some user provided specific prefix.

The prefix to be combination of alphabet and numeric.

Thanks

  • Cancel
Parents
  • RiadKaced
    RiadKaced over 6 years ago

    Hi Paramjeet,

    I'd love to help you with the SKILL code, I just want to get the spec right. Can you provide a little more details of the problem you are trying to solve?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Paramjeet
    Paramjeet over 6 years ago in reply to RiadKaced

    Hello RiadKaced,

    Thanks for your response. Actually what we need is that we have certain cadence libraries which we are using for building the IP. Then we are sending across the entire collateral to SoC team for their usage. There are collisions at SoC level due to same names. So to avoid that we want to uniquify all libs with a specific prefix everytime before sending data to SoC team. Say for example for first release we can give prefix as release1_<cellname>, and then on final release we can give prefix as final_releaseV04_<cell name>. This prefix we want for all cells of all cadence libs we have. The final cadence libs we give to SoC team should have all those fixes appended. This entire thing require the prefixing of all cells and their correct change in the references wherever they are used in the entire cadence lib.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Paramjeet
    Paramjeet over 6 years ago in reply to RiadKaced

    Hello RiadKaced,

    Thanks for your response. Actually what we need is that we have certain cadence libraries which we are using for building the IP. Then we are sending across the entire collateral to SoC team for their usage. There are collisions at SoC level due to same names. So to avoid that we want to uniquify all libs with a specific prefix everytime before sending data to SoC team. Say for example for first release we can give prefix as release1_<cellname>, and then on final release we can give prefix as final_releaseV04_<cell name>. This prefix we want for all cells of all cadence libs we have. The final cadence libs we give to SoC team should have all those fixes appended. This entire thing require the prefixing of all cells and their correct change in the references wherever they are used in the entire cadence lib.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • RiadKaced
    RiadKaced over 6 years ago in reply to Paramjeet

    Sure, that requires a bit of coding but that's feasible. What about the libName ? Do you keep the original name for the libraries or do you want to prefix the libs as well. Also, I guess Cadence libraries (analogLib, basic ...ect) and other reference libraries (say IO, StandardCell libs ...etc) are excluded from this stuff, right ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Paramjeet
    Paramjeet over 6 years ago in reply to RiadKaced

    For lib names I prefer to keep them same and same for reference libraries.

    • 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