• 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. ADE Explorer - Corner Simulations failing remotely

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 4224
  • 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 Explorer - Corner Simulations failing remotely

Conorp
Conorp over 5 years ago

I'm using cadence_ic 6.1.8.090 but have also used 6.1.8.060 in testing. I ran the following with ADE Explorer and ADE Assembler.

I am trying to run multiple corner simulations remotely. I can run a single corner remotely with no issues, however once I try to run remotely with more than a single corner or monte carlo then I encounter the following error:

\o Loading viva.cxt

\e *Error* Error during configuration of remote session.

\e ("error" 0 t nil ("*Error* The default SKILL generic function has not been defined for the function \"asiGetAnalogSimulator\". Ensure that this function is called with the correct argument(s) (tool).\n"))

\e

\e

\o

\o *Error*   Error ID  = 5000

\o *Error*   Error Msg = Error while configuring the job.

I've tried adding envSetVal("adexl.icrpStartup" "newCdsXVNCForeachICRP" 'boolean t) but this doesn't appear to help. When I run a single point remotely (not monte carlo) this error does not appear in the log.

Many thanks,

Conor

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Conor,

    Try setting this in the CIW before you start ADE:

    envSetVal("adexl.icrpStartup" "showJobStdout" 'boolean t)
    envSetVal("adexl.icrpStartup" "showJobStderr" 'boolean t)

    Then when the "ICRP" starts it should print messages in the CIW (and log file) about what's going on. Please provide those here.

    You may also just be able to check typing "virtuoso -nograph" in a terminal window and seeng if that fails.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Conor,

    Try setting this in the CIW before you start ADE:

    envSetVal("adexl.icrpStartup" "showJobStdout" 'boolean t)
    envSetVal("adexl.icrpStartup" "showJobStderr" 'boolean t)

    Then when the "ICRP" starts it should print messages in the CIW (and log file) about what's going on. Please provide those here.

    You may also just be able to check typing "virtuoso -nograph" in a terminal window and seeng if that fails.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Conorp
    Conorp over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    I tried "virtuoso -nograph" and that started successfully. I added the two debug lines you mentioned but I didn't seem to get any extra log output until I added the following to my .cdsinit:

    (when (axlIsICRPProcess)  _axlDebugTimeFlag = t  (sstatus errsetTrace t)  _stacktrace = 50  _axlCallbkDebugFlag = t ;uncomment this if debugging callbacks )

    I didn't see any error messages printed in the CIW with all filters off. The following is what appears in the Job Log, I've removed some of the paths and replaced them with <PATH>. I tried to format it to make it a little more readable...

    _axlGetResultsBasePathFromToolArgList
    1.
    basePath: "<PATH>/test_2020_03_20/maestro/results/maestro"
    toolArgList ( ("cell" "test_2020_03_20")
    ("faultdutlcv" "//")
    ("faultrungroup" "")
    ("faultssetupdir" "<PATH>/maestro/faultSetup")
    ("fenixMode" "explorer")
    ("historyentry" "Interactive.13")
    ("isROHistory" "0")
    ("lib" "MOSCharacterisation")
    ("localpsfdir" "/tmp/<PATH>")
    ("mode" "Single Run, Sweeps and Corners")
    ("netlistdelstrategy" "SaveAll")
    ("oceanScripts" "")
    ("overwritehistory" "0")
    ("path" "$AXL_SETUPDB_DIR/test_states")
    ("prerunscript" "0")
    ("prerunscriptfile" "")
    ("projdirloc" "<PATH>")
    ("quickplotenable" "t,4000")
    ("rawdatadelstrategy" "SaveAll")
    ("rdbaccessmode" "ByMPS")
    ("referencenetlistdir" "")
    ("relxanalysis" "1")
    ("relxanalysisenabled" "0")
    ("relxbasedir" "<PATH>")
    ("resultsloc" "<PATH>")
    ("runCallbacks" "1")
    ("sdbCell" "test_2020_03_20")
    ("sdbLib" "MOSCharacterisation")
    ("sdbView" "maestro")
    ("setupdbloc" "<PATH>")
    ("sim" "spectre")
    ("simdatasavemode" "All")
    ("state" "Interactive.13")
    ("testname" "MOSCharacterisation:test_2020_03_20:1")
    ("troubleshoothistoryflag" "0")
    ("uselocalpsfdir" "false")
    ("usenmpforfileencoding" "0")
    ("useseparatehistorymanagement" "0")
    ("view" "schematic")
    ("resdbpath" "<PATH>/maestro/results/maestro/Interactive.13.rdb")
    ("resultdirpath" "<PATH>/maestro/results/maestro/Interactive.13/1/MOSCharacterisation:test_2020_03_20:1") ("toolname" "ADE")
    ("netlistchecksoflcvs" "")
    ("parallelnumprocs" "")
    ("querymode" "")
    ("issupportwarn" 0)
    ("issupportsuspend" 0)
    ("warndiskthreshholdvalue" 100.0)
    ("diskthreshholdvalue" 100.0)
    ("simvisiondisplay" ":4.0")) session sevSession1
    \o Mar 24 10:43:41 2020 DAVINCI DEBUG: ------------ 4 ----------------
    \o Mar 24 10:43:41 2020 DAVINCI DEBUG: ------------ 5 ----------------
    \o Mar 24 10:43:41 2020 DAVINCI DEBUG: ------------ 5.1 ----------------
    \o Mar 24 10:43:41 2020 DAVINCI DEBUG: ------------ 5.2 ----------------
    \e *Error* The default SKILL generic function has not been defined for the function "asiGetAnalogSimulator". Ensure that this function is called with the correct argument(s) (tool).
    \e
    \e <<< Stack Trace >>>
    \e (... in asiGetAnalogSimulator generic ...)
    \e (... in _axlSimulatorInInteractiveMode ...)
    \e (... in unknown ...)
    \e (... in _axlLoadStateFromXml ...)
    \e (... in unknown ...)
    \e (... in _axlConfigureNewADESession ...)
    \e (... in unknown ...)
    \e (... in _axlConfigureForADE ...)
    \e (... in unknown ...)
    \e (... in unknown ...)
    \e funobj@0x21ebc318()
    \e (... in _axlConfigure ...)
    \e (... in _axlToolConfigureMethod (axlToolAdeAbstract t t t) ...)
    \e (... in unknown ...)
    \e (... in _axlToolConfigureCore ...)
    \e (... in _axlCallInICXPClientContextMethod (axlICRPClient t) ...)
    \e (... in unknown ...)
    \e (... in _axlCallInICXPClientContext ...)
    \e (... in _axlToolConfigure ...)
    \e _axlToolConfigure(
    2
    ( ("cell" "test_2020_03_20")
    ("faultdutlcv" "//")
    ("faultrungroup" "")
    ("faultssetupdir" "<PATH>/test_2020_03_20/maestro/faultSetup")
    ("fenixMode" "explorer") ... )

    ( ("resdbpath" "<PATH>/test_2020_03_20/maestro/results/maestro/Interactive.13.rdb")
    ("resultdirpath" "<PATH>/maestro/results/maestro/Interactive.13/1/MOSCharacterisation:test_2020_03_20:1")
    ("toolname" "ADE")
    ("netlistchecksoflcvs" "")
    ("parallelnumprocs" "") ... )

    nil nil ... )

    \e *Error* Error during configuration of remote session.
    \e ("error" 0 t nil ("*Error* The default SKILL generic function has not been defined for the function \"asiGetAnalogSimulator\". Ensure that this function is called with the correct argument(s) (tool).\n"))

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Conorp

    Conor,

    I don't think these debug flags will help particularly in this case - it just crowds the output. Are you running with a "local" job policy or something else?

    Either way, to be honest, this would make far more sense to debug via customer support - that way we can have a screen-sharing session with you to debug the problem, which will be far more effective than back-and-forth here.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Conorp
    Conorp over 5 years ago in reply to Andrew Beckett

    You're absolutely right, I'll look into setting that up now.

    Many thanks for your time.

    All the best,

    Conor

    • 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