Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 14601
  • 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

problem encountered in setting up the mpsc front end?

wonyoung Kim
Hello, I'm running a bunch of Cadence simulations from UNIX terminals using the ocean -restore -nograph oceanscript.ocn command. I run 10 different ocean scripts that use the same netlist, but different variable values. Most of them run well, but for some of them I get the following error message in my output log. problem encountered in setting up the mpsc front end Then the simulation terminates even before entering the transient simulation. Could anyone help me fix this problem? Thanks, Wonyoung

  • Are you running them at the same time? If so, it's likely that the runSimulation script is being updated from one session before another session invokes it - and that would confuse the communication channels.

    Regards,

    Andrew.

  • Thanks so much Andrew. I think that was the problem. I copied the netlist files to different directories and changed my ocean scripts accordingly, and that fixed the problem.

    I have one more question. I'm running multiple simulations from the UNIX terminal using the command ocean -restore -nograph oceanscript.ocn. The strange thing is that even though I'm using '-restore', I sometimes get and error message saying 'X connection to host broken' I find it strange that it's trying to connect to X windows even in -nograph mode. Is there a way to completely block the ocean script from attempting to connect to X windows?

    Thanks,

    Wonyoung
    Andrew Beckett said:

    Are you running them at the same time? If so, it's likely that the runSimulation script is being updated from one session before another session invokes it - and that would confuse the communication channels.

    Regards,

    Andrew.

  • When you run "-nograph" it launches an X server behind the scenes which doesn't display anything. In IC5141 and releases up to and including IC613 it starts a program called "Xndx". From IC614 forwards, it actually runs a vnc server.

    It has to do this (or rather it's much simpler to do this) because then all the UI functions still work - you don't have to code in lots of places for whether the display is there or not.

    Sometimes if you get these X errors you can just run "Xndx" before you start ".. -nograph" (or if using IC614, use "cdsVncserver :80" before you run with -nograph). This will pre-start the X server which swallows the X traffic - and that can improve matters. That said, I've not had to do this for some time.

    It's probably advisable to create a service request via http://support.cadence.com to discuss this with an application engineer.

    Regards,

    Andrew.

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.