• 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. load a skill into the terminal

Stats

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

load a skill into the terminal

Titi
Titi over 16 years ago

Hello, i try to load a skill (toto.il) into the terminal wish has launched my icfb.

I try it with an Opusserver but i can't load toto.il directly, i try to load it by using a variable "command" , when i set manualy (into icfb) command to "toto.il", all is ok, the script is launched. But i can'tset the variable command to "toto.il" into the terminal, i think the probleme is due to the string, the return is always "" or nil.

This is my syntax : 

echo "command = "toto.il" " | opusClient (This command always return nil)
echo "(load command)" | opusClient

 Have you a solution instead of my solution with opusServer ??

 Thanks.

  • Cancel
Parents
  • skillUser
    skillUser over 16 years ago

    Hi,

    I'm not entirely sure I understand your question, but I'm assuming that you want a DFII session to read a SKILL syntax file from the command line.  One way to do this is to use the "-restore" command line option:

     -restore filename   Restores a saved session from filename.

    E.g.

    icfb -restore toto.il

    Or you can read in SKILL in the .cdsinit file.  Or maybe you are trying to read SKILL syntax at a unix-like prompt?  There is the executable "skill" which when started gives you a prompt and accepts SKILL syntaxbut it does not contain all of the contexts that are loaded in icfb, icms etc. so it will not understand db*, le*, or sch* functions etc. Of course you could also starticfb etc. without graphics which will also give you a command line prompt in your terminal, for example:

     icfb -nograph

    I don't think that you can pipe SKILL commands at the command line prompt into a DFII executable (if this is what you are trying to do?), but you can start an external process from within DFII and communicate with it.  Here you would use the ipcBeginProcess and other ipc* prefix functions for 2-directional communication.

    If this is not what you are looking for, please re-word your  request and try again.

    Hope it helps.

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

    Hi,

    I'm not entirely sure I understand your question, but I'm assuming that you want a DFII session to read a SKILL syntax file from the command line.  One way to do this is to use the "-restore" command line option:

     -restore filename   Restores a saved session from filename.

    E.g.

    icfb -restore toto.il

    Or you can read in SKILL in the .cdsinit file.  Or maybe you are trying to read SKILL syntax at a unix-like prompt?  There is the executable "skill" which when started gives you a prompt and accepts SKILL syntaxbut it does not contain all of the contexts that are loaded in icfb, icms etc. so it will not understand db*, le*, or sch* functions etc. Of course you could also starticfb etc. without graphics which will also give you a command line prompt in your terminal, for example:

     icfb -nograph

    I don't think that you can pipe SKILL commands at the command line prompt into a DFII executable (if this is what you are trying to do?), but you can start an external process from within DFII and communicate with it.  Here you would use the ipcBeginProcess and other ipc* prefix functions for 2-directional communication.

    If this is not what you are looking for, please re-word your  request and try again.

    Hope it helps.

    • 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