Stats

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

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

Parents

  • 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

Reply

  • 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

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.