Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 6275
  • 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

ADE XL doesn't work. ERROR (ADEXL-5025)

habet

Hello everyone,

I am using Cadence IC6.1.5-64b.500.9  (64-bit addresses) for my design.
The simulation with ADE L works well. I want to use ADE XL to do monte carlo simulation so, it doens't work. I tried a single run with ADE XL, it doesn't work also and it gives this message's error.
ERROR (ADEXL-5025): Preparation to run the simulation is failed for the run Interactive.24, point 1, test
 Error while preparing to run the simulation.
 Cannot copy "netlist into run netlist" from "/home/xxx/simulation/TEST/emeteur_commun/adexl/results/data/Interactive.24/1/TEST:emeteur_commun:1/netlist" to "/home/xxx/simulation/TEST/emeteur_commun/adexl/results/data/Interactive.24/psf/TEST:emeteur_commun:1/netlist", cpDataDir call returned 0

 For details open log: /home/xxx/Qubic4X_wrk/logs_xxx/Job8.log for the point: (0 1)
 did someone met this problem ?
Thank you for your help.
Abdel

Parents

  • Following up with my solution to this problem. I had assumed that cpDataDir was a SKILL command and was thus implemented internally. Turn out this is not the case--this is a simple problem of incomplete tool paths. As per Cadence customer service, in a csh environment, the system path should look like the following:

    set path = ( $MMSIMHOME/tools/bin \ $CDSHOME/tools/bin \ $CDSHOME/tools/dfII/bin \ $CDSHOME/tools/plot/bin \ $CDSHOME/tools/etc \ /usr/local/bin $path )

    In my bash environment, my setup is the same but with different syntax:

     

    • export CDSHOME=/root/cadence/installs/IC615
    • export MMSIMHOME=/root/cadence/installs/MMSIM111
    • export PATH=$PATH:$MMSIMHOME/tools/bin
    • export PATH=$PATH:$CDSHOME/bin
    • export PATH=$PATH:$CDSHOME/tools/bin
    • export PATH=$PATH:$CDSHOME/tools/dfII/bin
    • export PATH=$PATH:$CDSHOME/tools/plot/bin
    • export PATH=$PATH:$CDSHOME/tools/etc/bin

     

    The key is that the cpDataDir executable is located in $CDSHOME/tools/dfII/bin.

    Best of luck to any Googlers!

Reply

  • Following up with my solution to this problem. I had assumed that cpDataDir was a SKILL command and was thus implemented internally. Turn out this is not the case--this is a simple problem of incomplete tool paths. As per Cadence customer service, in a csh environment, the system path should look like the following:

    set path = ( $MMSIMHOME/tools/bin \ $CDSHOME/tools/bin \ $CDSHOME/tools/dfII/bin \ $CDSHOME/tools/plot/bin \ $CDSHOME/tools/etc \ /usr/local/bin $path )

    In my bash environment, my setup is the same but with different syntax:

     

    • export CDSHOME=/root/cadence/installs/IC615
    • export MMSIMHOME=/root/cadence/installs/MMSIM111
    • export PATH=$PATH:$MMSIMHOME/tools/bin
    • export PATH=$PATH:$CDSHOME/bin
    • export PATH=$PATH:$CDSHOME/tools/bin
    • export PATH=$PATH:$CDSHOME/tools/dfII/bin
    • export PATH=$PATH:$CDSHOME/tools/plot/bin
    • export PATH=$PATH:$CDSHOME/tools/etc/bin

     

    The key is that the cpDataDir executable is located in $CDSHOME/tools/dfII/bin.

    Best of luck to any Googlers!

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.