• 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. Sending SKILL commands to a running instance of ICFB

Stats

  • Locked Locked
  • Replies 18
  • Subscribers 145
  • Views 29736
  • 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

Sending SKILL commands to a running instance of ICFB

gsimard
gsimard over 16 years ago

Hi all !

 

 I was wondering if it would be possible to send SKILL instructions to a running instance of ICFB, just as if I was typing them in the console of the ICFB, but from an external process. The idea is to use my favorite editor (emacs) and being able to interact with the ICFB process (sending code, retrieving replies, in the best scenario).

 

Thank you for any advice !

Guillaume

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

    Indeed, Lawrence is on the money. What you're seeing with the port:"/tmp/..." bit is merely the print representation of the object. There's no guarantee that the print representation of any object can be used as input syntax. Think of db objects, and so on. There are odd cases (for example, there's the funobj() function which can be used to retrieve a function object given its id, but even then these have to be used with caution because the id won't stay the same in different sessions.

    That said, there's nothing to stop you writing a SKILL++ package using closures which could be used for opening and closing ports - and this could store internally (in private, non-global data) the mapping between file names and ports, so you could then have a function to retrieve the port given the filename. 

    I just threw this together:

    /* abPort.ils
    
    Author     A.D.Beckett
    Group      Custom IC (UK), Cadence Design Systems Ltd.
    Language   SKILL
    Date       Jul 16, 2009 
    Modified   
    By         
    
    Package to manage ports...
    
    ***************************************************
    
    SCCS Info: @(#) abPort.ils 07/16/09.18:53:08 1.1
    
    */
    
    (importSkillVar abPort)
    (setq abPort
    (let ((portStorage (makeTable 'portStorage nil)))
      (defun infilePort (@rest args)
        (setarray portStorage (car args) (apply infile args))
        )
      (defun outfilePort (@rest args)
        (setarray portStorage (car args) (apply outfile args))
        )
      (defun closePort (port)
        (remove (get_filename port) portStorage)
        (close port)
        )
      (defun getPort (fileName)
        (arrayref portStorage fileName)
        )
      (list 
        nil 
        'infile infilePort 
        'outfile outfilePort
        'close closePort
        'get getPort
        )
      )
    )
    
    

    To use it, you'd do:

    prt=abPort->outfile("/tmp/stuff")

    If you've lost contact with your variable, you can then do:

    abPort->get("/tmp/stuff")

    and get the port back again for the given fileName.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 16 years ago

    Indeed, Lawrence is on the money. What you're seeing with the port:"/tmp/..." bit is merely the print representation of the object. There's no guarantee that the print representation of any object can be used as input syntax. Think of db objects, and so on. There are odd cases (for example, there's the funobj() function which can be used to retrieve a function object given its id, but even then these have to be used with caution because the id won't stay the same in different sessions.

    That said, there's nothing to stop you writing a SKILL++ package using closures which could be used for opening and closing ports - and this could store internally (in private, non-global data) the mapping between file names and ports, so you could then have a function to retrieve the port given the filename. 

    I just threw this together:

    /* abPort.ils
    
    Author     A.D.Beckett
    Group      Custom IC (UK), Cadence Design Systems Ltd.
    Language   SKILL
    Date       Jul 16, 2009 
    Modified   
    By         
    
    Package to manage ports...
    
    ***************************************************
    
    SCCS Info: @(#) abPort.ils 07/16/09.18:53:08 1.1
    
    */
    
    (importSkillVar abPort)
    (setq abPort
    (let ((portStorage (makeTable 'portStorage nil)))
      (defun infilePort (@rest args)
        (setarray portStorage (car args) (apply infile args))
        )
      (defun outfilePort (@rest args)
        (setarray portStorage (car args) (apply outfile args))
        )
      (defun closePort (port)
        (remove (get_filename port) portStorage)
        (close port)
        )
      (defun getPort (fileName)
        (arrayref portStorage fileName)
        )
      (list 
        nil 
        'infile infilePort 
        'outfile outfilePort
        'close closePort
        'get getPort
        )
      )
    )
    
    

    To use it, you'd do:

    prt=abPort->outfile("/tmp/stuff")

    If you've lost contact with your variable, you can then do:

    abPort->get("/tmp/stuff")

    and get the port back again for the given fileName.

    Regards,

    Andrew.

    • 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