• 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
  • Stephane A
    Stephane A over 15 years ago

    Dear all, dear Andrew,

    Thanks to your post, I started to write Skill and Perl programs to have a Perl sript send commands to ICFB.

    I tried 3 methodologies:

    1/ icpBeginProcess with a call back that directly calls the Perl program.

    2/ ipcSkillProcess with a call back that directly call thePerl program through the "3" chanel ID.

    3/ A Linux socket through the tcl script of Andrew above (it uses ipcBeginProcess and Linux socket).

     

    All of these solution works, but all share the same issue: even though I flush the Perl script output buffer (STDOUT or "3" or socket handle) it happens almost randomly that the commands recovered by ICFB is too long and ends cutted in the middle of skill commands.

    It happens when the Perl script sends hundreds of commands at once in a loop, like:

    SKILL test.il:

     procedure(socketHandler(ipcId data)
      printf("COMMAND: %L\n" data)
      evalstring(data)
    )

    ipcBeginProcess("./test.pl" "" 'socketHandler)

    PERL test.pl (draws a red disk in the current layout windows):

     #!/usr/bin/perl

    #Flushes the perl STDOUT buffer after each print:
    $|=1;

    print "cv=deGetEditCellView() ";
    print "cw=hiGetCurrentWindow() ";
    print "geDeleteAllHilightSet(cv) ";
    print "hiZoomIn(cw list(-10:-10 10:10)) ";
    print "hlSetId = geCreateHilightSet(cv \'(\"y1\" \"drawing\")) ";
    print "hlSetId->enable = t ";

    for ($j = 1; $j <= 3.141*2000; $j++) {
      $x2=10*cos($j/1000);
      $y2=10*sin($j/1000);
      print "geAddHilightLine(hlSetId list(0:0 $x2:$y2)) ";
    }

    print "hiRedraw(cw) ";

    After running this test script, the pie drawn has missing parts (missing rays).

    Does anyone have a clue how to solve this?

    Stéphane.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Stephane A
    Stephane A over 15 years ago

    Dear all, dear Andrew,

    Thanks to your post, I started to write Skill and Perl programs to have a Perl sript send commands to ICFB.

    I tried 3 methodologies:

    1/ icpBeginProcess with a call back that directly calls the Perl program.

    2/ ipcSkillProcess with a call back that directly call thePerl program through the "3" chanel ID.

    3/ A Linux socket through the tcl script of Andrew above (it uses ipcBeginProcess and Linux socket).

     

    All of these solution works, but all share the same issue: even though I flush the Perl script output buffer (STDOUT or "3" or socket handle) it happens almost randomly that the commands recovered by ICFB is too long and ends cutted in the middle of skill commands.

    It happens when the Perl script sends hundreds of commands at once in a loop, like:

    SKILL test.il:

     procedure(socketHandler(ipcId data)
      printf("COMMAND: %L\n" data)
      evalstring(data)
    )

    ipcBeginProcess("./test.pl" "" 'socketHandler)

    PERL test.pl (draws a red disk in the current layout windows):

     #!/usr/bin/perl

    #Flushes the perl STDOUT buffer after each print:
    $|=1;

    print "cv=deGetEditCellView() ";
    print "cw=hiGetCurrentWindow() ";
    print "geDeleteAllHilightSet(cv) ";
    print "hiZoomIn(cw list(-10:-10 10:10)) ";
    print "hlSetId = geCreateHilightSet(cv \'(\"y1\" \"drawing\")) ";
    print "hlSetId->enable = t ";

    for ($j = 1; $j <= 3.141*2000; $j++) {
      $x2=10*cos($j/1000);
      $y2=10*sin($j/1000);
      print "geAddHilightLine(hlSetId list(0:0 $x2:$y2)) ";
    }

    print "hiRedraw(cw) ";

    After running this test script, the pie drawn has missing parts (missing rays).

    Does anyone have a clue how to solve this?

    Stéphane.

     

    • 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