• 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. Automation using SKILL language

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 15410
  • 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

Automation using SKILL language

vjain
vjain over 10 years ago

how to do automation of custom design flow using cadence SKILL language? Please share...

  • Cancel
Parents
  • skillUser
    skillUser over 10 years ago

    Despite the very vague and open-ended question I'll take a stab at an answer...

    You could look through the CDS.log file for some of the actions being performed; if you are unfamiliar with the commands involved when you see them in the log file, you can mark "START" and "STOP", for example, before and after the operations you are trying to capture (by typing something like these strings in the CIW), then you can identify the sections you are interested in.  The problem is that many of the commands used will be "hi" (human interface) versions of commands intended for interactive use, rather than automation/batch mode processing.  So you will need to identify if there are non-hi equivalents of the commands (many commands do have non-hi versions). Ultimately one or more operations would probably need to be gathered into procedures for ease-of-reuse.  This outlines one approach to one aspect of automation, but as Andrew said, your question is too imprecise to guess what you want.

    If you have a specific task in mind, start asking about that - there might even be an existing example that you can use or leverage...

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 10 years ago

    Despite the very vague and open-ended question I'll take a stab at an answer...

    You could look through the CDS.log file for some of the actions being performed; if you are unfamiliar with the commands involved when you see them in the log file, you can mark "START" and "STOP", for example, before and after the operations you are trying to capture (by typing something like these strings in the CIW), then you can identify the sections you are interested in.  The problem is that many of the commands used will be "hi" (human interface) versions of commands intended for interactive use, rather than automation/batch mode processing.  So you will need to identify if there are non-hi equivalents of the commands (many commands do have non-hi versions). Ultimately one or more operations would probably need to be gathered into procedures for ease-of-reuse.  This outlines one approach to one aspect of automation, but as Andrew said, your question is too imprecise to guess what you want.

    If you have a specific task in mind, start asking about that - there might even be an existing example that you can use or leverage...

    Regards,

    Lawrence.

    • 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