• 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. IPC communication between Python and Cadence

Stats

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

IPC communication between Python and Cadence

Vijay Srini
Vijay Srini over 14 years ago

Hi All,

 I am trying to open a IPC channel between python and cadence. I managed to get one way communication from either to the other, but unable to get two way communication.

 Please help to point me in the right direction!

 

 Thanks in advance,

 

Vijay

  • Cancel
  • dmay
    dmay over 14 years ago

    I've done it this way:

    Skill:
    pyIpc = ipcBeginProcess("my.py " "" 'myIpcDataHandler 'myIpcErrHandler 'myIpcFinishHandler "/tmp/py.log")
    procedure(myIpcDataHandler(ipcId data)
      let((result)
        ;printf("in myIpcDataHandler with %L\n" data)
        foreach(d parseString(data "\n")
            unless(errset(result=evalstring(d))
                 printf("ERROR: %L\n" errset.errset)
                 ipcWriteProcess(ipcId sprintf(nil "ERROR %L\n" errset.errset))
            ) ; unless
        )
      )
    )

    procedure(myIpcErrHandler(ipcId data)
        println(list("ERROR: myIpcErrHandler called with:" ipcId data))
    )

    procedure(myIpcFinishHandler(ipcId data)
      let((exitStatus)
        printf("Finished at %s: %L %L  " getCurrentTime() ipcId data)
        exitStatus = ipcGetExitStatus(ipcId)
        printf("Return value = %L\n" exitStatus)
        if(exitStatus==0 then
            printf("The IPC call has finished!!\n")
        else
            printf("**ERROR: operation failed\n")
        )
      )
    )

    procedure(mySkillCommand(data)
        println(data)
        ipcWriteProcess(pyIpc "Skill says hello")
    )

    Python file my.py:
    import sys
    data = 'Hello from the Python world'
    sys.stdout.write('mySkillCommand("%s")\n' % data)
    sys.stdout.flush()
    returnData = sys.stdin.readline()
    #Write to a file since stdout goes to Cadence
    outFile = open('/tmp/myPy.out','w')   
    outFile.writelines( returnData )
    outFile.close()

    When done, /tmp/py.log shows commands sent from Python to skill through stdout and /tmp/myPy.out shows the Skill response.

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Vijay Srini
    Vijay Srini over 14 years ago

    Hi Derek,

     

    Thank you for your quick help. Everything goes fine but I am not able to read the returnData. The log file has only the "mySkillCommand..."

    I seem to have some issue with read timing.

    I tried doing it another way like the following:

    Python:

    import sys
    import os
    sys.stdout.flush()

    os.write(3,"(println \"Hello World!!\")")
    os.write(3,"(println \"Second time, Hello World!!\")")
    os.write(3,"(3+3)")

    a="(nil)"

    while "(nil)" in a:

        a="Start:",os.read(4,4096)

     

    SKILL:

    cid = ipcSkillProcess("python ~/scripts/skill/ipc_py/test2.py")

     

     I still have some timing issue, which improved with that while loop. Cadence seemed to return "(nil)" each time the read timing missed. Is there anyway to permanently resolve this issue?

     

     

    Thanks,

    Vijay

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dmay
    dmay over 14 years ago

    I had trouble with ipcSkillProcess and the 3&4 streams. That is why I chose to use ipcBeginProcess and used stdin and stdout instead. Also, in the Python, I limited my code to one readLine and had my skill code only send a string that contained one \n as the terminating character. This helped me with my communication problems. What I found was that if I sent multiple carriage returns, I needed a readline for each one. If I only performed one readline, then the next one was queued up for next time. If I used a while or a readLines, the Python would hang waiting on the stdin to finish. Maybe you can send it an EOF type character to get the Python to continue. I just coded around it so that Cadence always sent only one line back to Python for every command Python sent to Cadence. This was sufficient for me.

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Vijay Srini
    Vijay Srini over 14 years ago

    Hi Derek,

     

    Thanks for the explanation! Caught the reason why your way failed for me. I had terminated the return with a "\n". So the readline was failing. I added the newline character and now it seems to be working fine.

     

    Thanks a lot for your help!

     

    Thanks once again,

     

    Vijay

    • 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