Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14250
  • 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

delay in simulation initialization in ADE-XL

aditeman

Hi Andrew,

We have a small but aggravating issue in running simulations on ADE-XL with IC6.1.5/MMSIM 10.11

When we run a simulation by pressing the green "play" button in the old fashioned test editor (opened from ADE-XL), the simulation starts to run instantly, as expected.

But when we run a simulation by pressing the green "play" button in the ADE-XL GUI (which is the prefered way, to get all the benefits of ADE-XL), there is a delay that can take anywhere from a few seconds to a few minutes (!!!) until the actual simulation starts to run. Looking at the processes on our RHEL5 server, we see that a script called runICRP is created and sourced, which gets "stuck" on loading virtuoso -noautostart -log ... 

Is there any way to make this run faster? Is it something in our setup?

 By the way, I don't think this problem existed in prior versions of IC...

Thanks,

 

Adi 

  • Adi,

    It might be something in your .cdsinit which is causing it to get stuck. Try putting this in your .cdsinit :

    envSetVal("adexl.icrpStartup"  "binaryName" 'string "virtuoso -nocdsinit")

    It's possible that might break things if you have things in your .cdsinit which are needed for ADE to function correctly. Another possibility would be to surround parts of your .cdsinit with:

    if(axlIsICRPProcess() then
       ;do the bits that must be setup for ADE to work
    else
       ; do stuff that doesn't need to be done for ADE/netlisting to work. e.g. layout stuff
    )

    If this doesn't help, I'd suggest contacting customer support - we can work this through with you.

    Regards,

    Andrew.

  • Thanks, Andrew.

    I will for sure give it a try, although I think I know what everything is in my .cdsinit

     

    Adi 

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.