• 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. Undefined function ipcBeginProcess error during XStream...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 14073
  • 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

Undefined function ipcBeginProcess error during XStream Out

crizos
crizos over 7 years ago

Dear all,

I have created a PCell whose callbacks invokes functions from the ipc family. During the instantiation there are no errors or evaluation fails, but when I try to run Xstream Out the following error rises:

*Error* eval: undefined function - ipcBeginProcess

ipcBeginProcess is the first call of the ipc family.

The recommended solution from strmOut.log states to "either is a syntax error or an unsupported XStream function." and to "Either correct the pcell SKILL code or ignore the error by enabling the 'ignorePcellEvalFail' option for XStream Out."

Is there a way to use the ipc family without prompting the 'ignorePcellEvalFail' by custom fixing this issue or bypassing the support to these functions?

If this is not possible, is there any other way to use a valid to Xstream Out processing, similar to the ipc family?

In addition, streaming out from virtual memory does not apply to my project as a solution.

Note that the ipc is being used for commuting data between Skill and Python procedures.

Many thanks,

Chris

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

    Hi Chris,

    sh(), system, and csh() should be possible as these are available in core SKILL. ipcBeginProcess is not a legal function to use in a pcell (this is documented in the PCell documentation as core SKILL plus db, dd, tech/tf, cdf, rod and some pc functions; also abe functions in later IC617/ICADV123 ISRs).

    Using the ignorePcellEvalFail is a bad idea - you'd just end up streaming out potentially incorrect or incomplete pcell layouts. The only workaround without changing your code is to stream out from virtual memory.

    Andrew.

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

    Hi Chris,

    sh(), system, and csh() should be possible as these are available in core SKILL. ipcBeginProcess is not a legal function to use in a pcell (this is documented in the PCell documentation as core SKILL plus db, dd, tech/tf, cdf, rod and some pc functions; also abe functions in later IC617/ICADV123 ISRs).

    Using the ignorePcellEvalFail is a bad idea - you'd just end up streaming out potentially incorrect or incomplete pcell layouts. The only workaround without changing your code is to stream out from virtual memory.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • crizos
    crizos over 7 years ago in reply to Andrew Beckett

    Hi Andrew, thank you for the answer.

    Indeed, from the commands you propose system can help but only if the command's output can be redirected back to the CIW. I saw it into the manual and by action that this command prints the output at the UNIX terminal, but I was wondering, is there a way to redirect it back to the CIW?

    Thanks in advance,

    Chris

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to crizos

    Hi Chris,

    You could use:

    myFile=makeTempFileName("/tmp/myFile")
    cmd="/bin/ls -l /bin"
    system(strcat(cmd " > " myFile))
    port=infile(myFile)
    when(port
      while(gets(line port)
        printf("%s" line)
      )
      close(port)
      deleteFile(myFile)
    )

    Regards,

    Andrew.

    • 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