The top of the log file should say something like
 Loaded shared object
   /path/to/libsimkit.so

if the installation was successful.  Also, if you type "spectre -help" at the command line, it should give you a list of available components, and
   Components marked with * are loaded from shared objects

Geoffrey_Coram wrote on Mar 7^th, 2012, 6:35am:

Thank you, Geoffrey_Coram.

In the top of the log, it said "
Cannot access shared object /home/psp_model/libsimkit_spectre_5.0.so.
Cannot access shared object /home/psp_model/libsmk_5.0.so."
Does it mean that the simkit is not intalled successfully? I checked the available components, and PSP102e with * is in the list. How can I use this component?

I am not sure the version of my Spectre, but it is with MMSIM710. Does it have the PSP102/103 built-in?

Plenty of questions...  
Thank you very much!

Geoffrey_Coram wrote on Mar 7^th, 2012, 6:36am:

Sharp deduction, yes, the full path is /home/lynn/psp_model/... . It was not the full path because I deleted some terms to shorten it, but I am sure the path is correct.

I find my Spectre supports psp102e, so I run my model without newly-installed SimKit and netlisting is done successful. But there is not drain current through the NMOS, and log says as :
"Notice from spectre during info `dcOpInfo'.
   No outputs were found. Loosening output filter criterion to `lvlpub'.

dcOpInfo: writing operating point information to rawfile.

Notice from spectre during info `modelParameter'.
   No outputs were found. Loosening output filter criterion to `lvlpub'.

modelParameter: writing model parameter values to rawfile.
..."

What does it imply? And what shall I do for this?

Thanks for your patience

Thanks Geoffrey,
Geoffrey_Coram wrote on Mar 8^th, 2012, 12:11pm:
I extracted model parameters following PSP manual, maybe some of the parameters I extracted are far from "reality". Now, the model works, although the current is too small than expected. I'd re-check the parameters. The problem "No outputs were found" is caused by my wrong  setting in Save Options in ADE.

Geoffrey_Coram wrote on Mar 8^th, 2012, 12:11pm:
I'd try SimKit of latest version later and check the installation flow.

Thank you Geoffrey, for your analysis and advice with patience these days. I really appreciate that.

Thanks Geoffrey,

I installed SimKit, and it proved that the installation failed because .cmiconfig file I created in Windows was not recognized by Linux. The SimKit 3.7 supports PSP103, so I switched to PSP103 while simulating afterwards.

Model unconvergence emerge when Trans simulation, and I think some PSP parameters are not properly extracted. Am I right? What else causes convergence problem?

Still on my way

Thanks, Geoffrey,

Geoffrey_Coram wrote on Mar 20^th, 2012, 7:17am:


The circuit is a simple NMOS-based LC VCO, and my model worked well in DC and S-parameter simulation, but failed in Tran simulation.

I can not extract parameters of body diodes since relative data were not available, so I set swjuncap = 0 . Are the diodes critical for convengence?

I checked the device terminals and RF parasitic subcircuit, and I think they were all set. However, I found the non-universality parameter XCOR is significantly affect the convergence.  XCOR I extracted is around 3, and model was not convergent in VCO trans sim, but I set XCOR below 1, it converged. Have you ever encounter this circumstance?

Thanks a lot~

Thanks Geoffrey,

The sample MOS I have is in GSG test structure with S and B connected to the ground. So the measurement with varied Vbs is not available. Maybe XCOR I extracted was far from reality, and caused convergence problem.  Does inappropriate XCOR cause convergence problem?

I am wondering whether the XCOR changes a lot over different process of the same fab. Because I have some data of .13um MOS and I think maybe I can use they to extract XCOR as a reference. Is it practicable?

Thank you~