" *Error* asiGetDesignLibName: no applicable method for the class - list" during parametric simulation in ADE

Yayla,

The only record I have found of that error occuring was when the simulator was not in the path - and that was hotfixed in 5.10.41.500.6.147 and IC6.1.4.500.11 (and IC615) to give a more meaningful error message.

However, that can't be it in your case because the simulation is running.

I don't see that your OCEAN script can have anything to do with this if you're running in ADE.

Please report this to customer support. Note in general it's a good idea to list the specific version of the IC tools (and probably simulator for good measure) when you talk about problems such as this on the forum, as described in the Forum Guidelines.

Regards,

Andrew.

 Hi Andrew,

These are the information about my tool versions:

o IC 5.10.41.500.6.143.

o Cadence Virtuoso Spectre Circuit Simulator Version 10.1.1.200

How can I check whether the simulatior is in the path or not, Andrew?

Thanks,

 yayla

Hi Yayla,

A quick answer is to use "which spectre" to see if it is in your path or not, and then "spectre -W" to check the version in case you pick up the wrong one (IC5141 has a version of spectre built-in, so you want to set you path so that MMSIM101 is found first).

Regards,

Lawrence.

Hi Yayla & Andrew,

Are there any conclusion/solution about this issue?

I met similar issue as you are. I saw the error "asiPrint: no applicable method for the classes“ when I click "Netlist & Run"(or "netlist"), however, netlist can be extracted and simulation can be run successfully. Do you have any insight?

Really appreciate your support!

Amanda

Amanda,

Your problem is different from the earlier post in the thread - it's a different function, and at a different phase. The general "no applicable method for the class" message comes from SKILL++ when you are trying to call a method with an object of a class that has no method defined for it (or for a parent class).

The best thing to do is contact customer support. The next best thing is to specify which IC subversion you're using (type getVersion(t) in the CIW) and the spectre (if it was spectre) subversion from the simulator log file (or by typing "spectre -W" in a terminal window). If it's another simulator, please specify which one. Then enter in the CIW:

sstatus(errsetTrace t)
_stacktrace=50

and then run the netlist and run to reproduce the error, and post the stack trace here (along with the version information described above).

Note that I can't guarantee to respond quickly here (I have the day job to do!), whereas if you provide this information to customer support somebody should be assigned to work on it.

Regards,

Andrew.