• 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. where and how to get stored skill files in cadence

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 16756
  • 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

where and how to get stored skill files in cadence

raegaan
raegaan over 5 years ago

Hello

Can someone help me on how/where can I find the stored skill codes in cadence virtuoso??

Thanks and regards

Raegaan

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Raegaan,

    I don’t understand your question. What do you mean by “the stored skill codes”?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • raegaan
    raegaan over 5 years ago in reply to Andrew Beckett

    By stored skill codes I mean , the codes for each form or pcell that is ready to use.

    regards

    Raegaan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to raegaan

    Your question still doesn't make any sense. I don't know what "each for or pcell that is ready to use" means.

    If you're asking where the source code for Cadence tools is, then we don't provide that. We provide all the code needed to generate the forms that are part of the tools in a binary form so you can't see the source. If you're asking where the source code for parameterised cells as part of a process design kit is, then usually that's not provided by the foundry either - they either encrypt any code or have it shipped in a context file (which is a binary representation).

    If you're asking about code you've written (which I doubt, because of your question), then you'd know where it is. If you're asking about code written for local utilities at your site, you'd need to speak to whomever is responsible for that.

    To answer the question about the <virtuoso_install_dir> in your response to Lawrence's attempt to answer your very vague question, you can find that by typing cdsGetInstPath() in the CIW. It's the directory containing the software installation for Virtuoso.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to raegaan

    Your question still doesn't make any sense. I don't know what "each for or pcell that is ready to use" means.

    If you're asking where the source code for Cadence tools is, then we don't provide that. We provide all the code needed to generate the forms that are part of the tools in a binary form so you can't see the source. If you're asking where the source code for parameterised cells as part of a process design kit is, then usually that's not provided by the foundry either - they either encrypt any code or have it shipped in a context file (which is a binary representation).

    If you're asking about code you've written (which I doubt, because of your question), then you'd know where it is. If you're asking about code written for local utilities at your site, you'd need to speak to whomever is responsible for that.

    To answer the question about the <virtuoso_install_dir> in your response to Lawrence's attempt to answer your very vague question, you can find that by typing cdsGetInstPath() in the CIW. It's the directory containing the software installation for Virtuoso.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • raegaan
    raegaan over 5 years ago in reply to Andrew Beckett

    hi

    Thanks got what I wanted

    raegaan

    • 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