AHDLCMI Module Problem

D

Debjit

Guest
Hi All,

I am using RHEL 5.3 and Cadence IC5141. My simulator is
spectreVerilog. I have to simulate a lot of verilog-A files in my
simulation. Whenever I try to simulate the spectre terminates without
simulation and prompts the following message in the spectre.out. The
message is ---:



Opening directory
/home/debjit/ICFB/lp3919_c3_10R2/buck_osctop_edc02/veriloga/
veriloga.va.ahdlcmi/
(770)
Compiling ahdlcmi module library.
Failed to compile ahdlcmi module library, see
/home/debjit/ICFB/lp3919_c3_10R2/buck_osctop_edc02/veriloga/
veriloga.va.ahdlcmi/
for details
Could not open ahdlcmi module library
/home/debjit/ICFB/lp3919_c3_10R2/buck_osctop_edc02/veriloga/
veriloga.va.ahdlcmi/obj/Linux2.6.18-164.el5xen+gcc/optimize/
libahdlcmi.so
/home/debjit/ICFB/lp3919_c3_10R2/buck_osctop_edc02/veriloga/
veriloga.va.ahdlcmi/obj/Linux2.6.18-164.el5xen+gcc/optimize/
libahdlcmi.so:
cannot open shared object file: No such file or directory
Opening directory
/home/debjit/ICFB/lp3919_c3_10R2/state/veriloga/
veriloga.va.ahdlcmi/
(770)
Compiling ahdlcmi module library.
Failed to compile ahdlcmi module library, see
/home/debjit/ICFB/lp3919_c3_10R2/state/veriloga/
veriloga.va.ahdlcmi/
for details
Could not open ahdlcmi module library
/home/debjit/ICFB/lp3919_c3_10R2/state/veriloga/
veriloga.va.ahdlcmi/obj/Linux2.6.18-164.el5xen+gcc/optimize/
libahdlcmi.so
/home/debjit/ICFB/lp3919_c3_10R2/state/veriloga/
veriloga.va.ahdlcmi/obj/Linux2.6.18-164.el5xen+gcc/optimize/
libahdlcmi.so:
cannot open shared object file: No such file or directory
Opening directory
/home/debjit/ICFB/lp3919_c3_10R2/mydiode/veriloga/
veriloga.va.ahdlcmi/
(770)
Compiling ahdlcmi module library.
Failed to compile ahdlcmi module library, see
/home/debjit/ICFB/lp3919_c3_10R2/mydiode/veriloga/
veriloga.va.ahdlcmi/
for details
Could not open ahdlcmi module library
/home/debjit/ICFB/lp3919_c3_10R2/mydiode/veriloga/
veriloga.va.ahdlcmi/obj/Linux2.6.18-164.el5xen+gcc/optimize/
libahdlcmi.so
/home/debjit/ICFB/lp3919_c3_10R2/mydiode/veriloga/
veriloga.va.ahdlcmi/obj/Linux2.6.18-164.el5xen+gcc/optimize/
libahdlcmi.so:
cannot open shared object file: No such file or directory


This problem does not arise in case of RHEL 4. But I have no choice
other than to use RHEL 5. Can you please suggest where is the problem?

Thanks in advance.

Cheersss!!!!
Debjit.
 
Hi Debjit,

Would you mind doing the following please ?
1. Go to your library manager and go to file -> Opens Shell window.
2. Please post the output of the following commands you type in the
shell window opened in 1:
Command1: spectre -W
Command 2: icfb -W

This would help us getting an idea of the tools you are using.

Meanwhile, it might be useful for you to search this form as well.
This is what I could find ...
http://groups.google.com/groups/search?as_q=libahdlcmi&as_epq=&as_oq=&as_eq=&num=10&scoring=&lr=&as_sitesearch=&sitesearch=groups.google.com&as_qdr=&as_mind=1&as_minm=1&as_miny=2009&as_maxd=1&as_maxm=1&as_maxy=2009&as_ugroup=&as_usubject=&as_uauthors=&safe=off

Cheers,
Riad.
 
On Oct 25, 4:53 pm, Riad KACED <riad.ka...@gmail.com> wrote:
Hi Debjit,

Would you mind doing the following please ?
1. Go to your library manager and go to file -> Opens Shell window.
2. Please post the output of the following commands you type in the
shell window opened in 1:
Command1: spectre -W
Command 2: icfb -W

This would help us getting an idea of the tools you are using.

Meanwhile, it might be useful for you to search this form as well.
This is what I could find ...http://groups.google.com/groups/search?as_q=libahdlcmi&as_epq=&as_oq=...

Cheers,
Riad.
Click to expand...



Hi Riad,

I do not mind at all. I'm very fortunate that I am getting your help.
The two outputs are given below:
for spectre -W it is "sub-version 5.10.41.121508 "
and for icfb -W it is "sub-version 5.10.41.500.6.138".
I am providing the kernel information for RHEL also. The uname -a
gives the output "Linux avlsi-2 2.6.18-92.el5PAE #1 SMP Tue Apr 29
13:31:02 EDT 2008 i686 i686 i386 GNU/Linux". Here avlsi-2 is the host
name.

Thanks in advance for your help.


Cheers !!!!
Debjit.
 
On Oct 26, 12:28 pm, Debjit <debjit...@gmail.com> wrote:
On Oct 25, 4:53 pm, Riad KACED <riad.ka...@gmail.com> wrote:



Hi Debjit,

Would you mind doing the following please ?
1. Go to your library manager and go to file -> Opens Shell window.
2. Please post the output of the following commands you type in the
shell window opened in 1:
Command1: spectre -W
Command 2: icfb -W

This would help us getting an idea of the tools you are using.

Meanwhile, it might be useful for you to search this form as well.
This is what I could find ...http://groups.google.com/groups/search?as_q=libahdlcmi&as_epq=&as_oq=...

Cheers,
Riad.

Hi Riad,

I do not mind at all. I'm very fortunate that I am getting your help.
The two outputs are given below:
for spectre -W it is "sub-version  5.10.41.121508 "
and for icfb -W it is "sub-version 5.10.41.500.6.138".
I am providing the kernel information for RHEL also. The uname -a
gives the output "Linux avlsi-2 2.6.18-92.el5PAE #1 SMP Tue Apr 29
13:31:02 EDT 2008 i686 i686 i386 GNU/Linux". Here avlsi-2 is the host
name.

Thanks in advance for your help.

Cheers !!!!
Debjit.
Click to expand...
Hi Riad,

As an additionla informationb I like to mention that I am using
spectre from IC5141 package not from MMSIM package. And I am using the
verilog simulator from the IUS package. The verilog -version returns
the following: "Tool: VERILOG-XL 08.20.001-p".
Please suggest.
If I have toi install some specific Cadence package please suggest
that too. I have access to download.cadence.com, hence I can download
the softwares and can install them.
 
Hi Debjit,

Thanks for the info.
I'm glad you have realized you are using Spectre from IC5141, which is
actually not the right thing to do.
The Spectre executable in IC5141 stream is there for legacy reasons
only. It is a very old one and is very likely to put you in pain as
you are currently seeing.
Since you have access to downloads, I would advise using late ISRs of
MMSIM71. MMSIM71 is easy to install and does not any configuration.
You only need to link tools.lnx86 to tools after the install, i.e.
browse to the installation dir and type the following
LINUX> ln -s tools.lnx86 tools
Also ensure the MMSI71 streams gets invoked before the IC5141 stream
in the UNIX PATH variable.

Moving your Spectre model cards from IC5141 to MMSIM71 should be
smooth. Well I know of a little incompatibility moving to MMSIM71
though, it is a minor stuff related to dcmatch and is covered in
SourceLink solution 11544188 and 11587436.

Anyway, I think your Verilog-A errors are caused by your very old
Spectre version and switching to MMSIM71 would make it much better.
Likewise, you may need to upgrade to latest IUS82 s018 ISR or maybe
consider IUS92 which available through INCISIVE92 since last week
(look at SourceLink 11593850).
I can't remember the reason you stick at spectreVerilog instead of
moving to AMS Designer. But if you consider the Move to AMS Designer
then I will provide you with all the necessary help although I firstly
encourage you using your primary help sources, i.e. your NSC CAD guys
and Cadence Customer Support.

Cheers,
Riad.
 
On Oct 26, 6:17 am, Riad KACED <riad.ka...@gmail.com> wrote:
Hi Debjit,

Thanks for the info.
I'm glad you have realized you are using Spectre from IC5141, which is
actually not the right thing to do.
The Spectre executable in IC5141 stream is there for legacy reasons
only. It is a very old one and is very likely to put you in pain as
you are currently seeing.
Since you have access to downloads, I would advise using late ISRs of
MMSIM71. MMSIM71 is easy to install and does not any configuration.
You only need to link tools.lnx86 to tools after the install, i.e.
browse to the installation dir and type the following
LINUX> ln -s tools.lnx86 tools
Also ensure the MMSI71 streams gets invoked before the IC5141 stream
in the UNIX PATH variable.

Moving your Spectre model cards from IC5141 to MMSIM71 should be
smooth. Well I know of a little incompatibility moving to MMSIM71
though, it is a minor stuff related to dcmatch and is covered in
SourceLink solution 11544188 and 11587436.

Anyway, I think your Verilog-A errors are caused by your very old
Spectre version and switching to MMSIM71 would make it much better.
Likewise, you may need to upgrade to latest IUS82 s018 ISR or maybe
consider IUS92 which available through INCISIVE92 since last week
(look at SourceLink 11593850).
I can't remember the reason you stick at spectreVerilog instead of
moving to AMS Designer. But if you consider the Move to AMS Designer
then I will provide you with all the necessary help although I firstly
encourage you using your primary help sources, i.e. your NSC CAD guys
and Cadence Customer Support.

Cheers,
Riad.
Click to expand...
Do you have the C compiler installed in your workstation? (Both i386
and x86_64)
 
On Oct 26, 1:17 pm, Riad KACED <riad.ka...@gmail.com> wrote:
Hi Debjit,

Thanks for the info.
I'm glad you have realized you are using Spectre from IC5141, which is
actually not the right thing to do.
The Spectre executable in IC5141 stream is there for legacy reasons
only. It is a very old one and is very likely to put you in pain as
you are currently seeing.
Since you have access to downloads, I would advise using late ISRs of
MMSIM71. MMSIM71 is easy to install and does not any configuration.
You only need to link tools.lnx86 to tools after the install, i.e.
browse to the installation dir and type the following
LINUX> ln -s tools.lnx86 tools
Also ensure the MMSI71 streams gets invoked before the IC5141 stream
in the UNIX PATH variable.

Moving your Spectre model cards from IC5141 to MMSIM71 should be
smooth. Well I know of a little incompatibility moving to MMSIM71
though, it is a minor stuff related to dcmatch and is covered in
SourceLink solution 11544188 and 11587436.

Anyway, I think your Verilog-A errors are caused by your very old
Spectre version and switching to MMSIM71 would make it much better.
Likewise, you may need to upgrade to latest IUS82 s018 ISR or maybe
consider IUS92 which available through INCISIVE92 since last week
(look at SourceLink 11593850).
I can't remember the reason you stick at spectreVerilog instead of
moving to AMS Designer. But if you consider the Move to AMS Designer
then I will provide you with all the necessary help although I firstly
encourage you using your primary help sources, i.e. your NSC CAD guys
and Cadence Customer Support.

Cheers,
Riad.
Click to expand...
Hi Riad,

Yahoooo!!!! Its running without any ahdlcmi error. But one thing I
should say that it is giving the following problem when I ran from the
Cadence GUI. The CDS.log says that

"Possible cause could be an invalid command line option for the
version of the simulator
you are running. Choose Setup->Environment and verify that the command
line options
specified in the userCmdLineOption field are supported for the
simulator.
Alternatively, run the simulator standalone using the runSimulation
file in the netlist
directory to know the exact cause of the error."

But I was able to run the simulation from command line by running ./
runSimulation script. I have set the value as " +lqt 900 +lqs 30 " in
the userCmdLineOption field in Setup->Environment option. What should
be the value in that field?

The "spectre -W" now gives "sub-version 7.1.1.239.isr15". It is
faster also than the earlier one.

I cannot use AMS Designer primarily as NSC still do not uses it,
especially John's group. I am working in a project in collaboration
with John's group. But anyways, I will setup it after this project is
over. I will give you a shout at that time.

Can you please suggest the value in the "userCmdLineOption" field?

Thanks., but it is insufficient w.r.t your support.

Cheers !!!!!!
Debjit.
 
On Oct 26, 8:22 pm, Debjit <debjit...@gmail.com> wrote:
On Oct 26, 1:17 pm, Riad KACED <riad.ka...@gmail.com> wrote:



Hi Debjit,

Thanks for the info.
I'm glad you have realized you are using Spectre from IC5141, which is
actually not the right thing to do.
The Spectre executable in IC5141 stream is there for legacy reasons
only. It is a very old one and is very likely to put you in pain as
you are currently seeing.
Since you have access to downloads, I would advise using late ISRs of
MMSIM71. MMSIM71 is easy to install and does not any configuration.
You only need to link tools.lnx86 to tools after the install, i.e.
browse to the installation dir and type the following
LINUX> ln -s tools.lnx86 tools
Also ensure the MMSI71 streams gets invoked before the IC5141 stream
in the UNIX PATH variable.

Moving your Spectre model cards from IC5141 to MMSIM71 should be
smooth. Well I know of a little incompatibility moving to MMSIM71
though, it is a minor stuff related to dcmatch and is covered in
SourceLink solution 11544188 and 11587436.

Anyway, I think your Verilog-A errors are caused by your very old
Spectre version and switching to MMSIM71 would make it much better.
Likewise, you may need to upgrade to latest IUS82 s018 ISR or maybe
consider IUS92 which available through INCISIVE92 since last week
(look at SourceLink 11593850).
I can't remember the reason you stick at spectreVerilog instead of
moving to AMS Designer. But if you consider the Move to AMS Designer
then I will provide you with all the necessary help although I firstly
encourage you using your primary help sources, i.e. your NSC CAD guys
and Cadence Customer Support.

Cheers,
Riad.

Hi Riad,

Yahoooo!!!! Its running without any ahdlcmi error. But one thing I
should say that it is giving the following problem when I ran from the
Cadence GUI. The CDS.log says that

"Possible cause could be an invalid command line option for the
version of the simulator
you are running. Choose Setup->Environment and verify that the command
line options
specified in the userCmdLineOption field are supported for the
simulator.
Alternatively, run the simulator standalone using the runSimulation
file in the netlist
directory to know the exact cause of the error."

But I was able to run the simulation from command line by running ./
runSimulation script. I have set the value as " +lqt 900 +lqs 30 " in
the userCmdLineOption field in Setup->Environment option. What should
be the value in that field?

The "spectre -W" now gives "sub-version  7.1.1.239.isr15".   It is
faster also than the earlier one.

I cannot use AMS Designer primarily as NSC still do not uses it,
especially John's group. I am working in a project in collaboration
with John's group. But anyways, I will setup it after this project is
over. I will give you a shout at that time.

Can you please suggest the value in the "userCmdLineOption" field?

Thanks., but it is insufficient w.r.t your support.

Cheers !!!!!!
Debjit.
Click to expand...
Hi Riad,

I cannot get IUS92. How can I get it? Please suggest. I cannot get the
INCISIVE92 from Sourcelink also.
Thanks!!!!

Cheers!!!!!

Debjit.
 
On Oct 26, 8:48 pm, Debjit <debjit...@gmail.com> wrote:
On Oct 26, 8:22 pm, Debjit <debjit...@gmail.com> wrote:



On Oct 26, 1:17 pm, Riad KACED <riad.ka...@gmail.com> wrote:

Hi Debjit,

Thanks for the info.
I'm glad you have realized you are using Spectre from IC5141, which is
actually not the right thing to do.
The Spectre executable in IC5141 stream is there for legacy reasons
only. It is a very old one and is very likely to put you in pain as
you are currently seeing.
Since you have access to downloads, I would advise using late ISRs of
MMSIM71. MMSIM71 is easy to install and does not any configuration.
You only need to link tools.lnx86 to tools after the install, i.e.
browse to the installation dir and type the following
LINUX> ln -s tools.lnx86 tools
Also ensure the MMSI71 streams gets invoked before the IC5141 stream
in the UNIX PATH variable.

Moving your Spectre model cards from IC5141 to MMSIM71 should be
smooth. Well I know of a little incompatibility moving to MMSIM71
though, it is a minor stuff related to dcmatch and is covered in
SourceLink solution 11544188 and 11587436.

Anyway, I think your Verilog-A errors are caused by your very old
Spectre version and switching to MMSIM71 would make it much better.
Likewise, you may need to upgrade to latest IUS82 s018 ISR or maybe
consider IUS92 which available through INCISIVE92 since last week
(look at SourceLink 11593850).
I can't remember the reason you stick at spectreVerilog instead of
moving to AMS Designer. But if you consider the Move to AMS Designer
then I will provide you with all the necessary help although I firstly
encourage you using your primary help sources, i.e. your NSC CAD guys
and Cadence Customer Support.

Cheers,
Riad.

Hi Riad,

Yahoooo!!!! Its running without any ahdlcmi error. But one thing I
should say that it is giving the following problem when I ran from the
Cadence GUI. The CDS.log says that

"Possible cause could be an invalid command line option for the
version of the simulator
you are running. Choose Setup->Environment and verify that the command
line options
specified in the userCmdLineOption field are supported for the
simulator.
Alternatively, run the simulator standalone using the runSimulation
file in the netlist
directory to know the exact cause of the error."

But I was able to run the simulation from command line by running ./
runSimulation script. I have set the value as " +lqt 900 +lqs 30 " in
the userCmdLineOption field in Setup->Environment option. What should
be the value in that field?

The "spectre -W" now gives "sub-version  7.1.1.239.isr15".   It is
faster also than the earlier one.

I cannot use AMS Designer primarily as NSC still do not uses it,
especially John's group. I am working in a project in collaboration
with John's group. But anyways, I will setup it after this project is
over. I will give you a shout at that time.

Can you please suggest the value in the "userCmdLineOption" field?

Thanks., but it is insufficient w.r.t your support.

Cheers !!!!!!
Debjit.

Hi Riad,

I cannot get IUS92. How can I get it? Please suggest. I cannot get the
INCISIVE92 from Sourcelink also.
Thanks!!!!

Cheers!!!!!

Debjit.
Click to expand...
Hi Riad,

I am getting convergence errors whicle using this spectre from MMSIM
package. The convergence problem which was solved for spectre from
IC5141 package, they are arising again here.
I donot know. But can you suggest me that which filter is good, slew
filter or transition filter in verilog-A? It seems to me slew is
better but cannot confirm myself. Please suggest.

Cheerss!!!
Debjit.
 
Hi Debjit,

I have successfully downloaded INCISIVE 92 from sourcelink. Bear in
mind using a recent version of installScape to get Incisive. Also,
when you install iscape, you may need to configure your internet
connections, i.e the proxies, ports ... etc. Finally you just need to
install the 3 products as mentioned in the SL solutions to get IUS
from INCISIVE. Anyway, post your errors, this narrows down the issue.

I am using transition as a filter.

Again, please post your new MMSIM version and the convergence problems
you have.

PS: Debjit, please bear in mind I am not a Cadence employee and thus
can't help out of my working hours, i.e. 9:00 till 17:30 GMT. Sorry
for that :-(

Cheers,
Riad.
 
On Oct 27, 1:39 pm, Riad KACED <riad.ka...@gmail.com> wrote:
Hi Debjit,

I have successfully downloaded INCISIVE 92 from sourcelink. Bear in
mind using a recent version of installScape to get Incisive. Also,
when you install iscape, you may need to configure your internet
connections, i.e the proxies, ports ... etc. Finally you just need to
install the 3 products as mentioned in the SL solutions to get IUS
from INCISIVE. Anyway, post your errors, this narrows down the issue.

I am using transition as a filter.

Again, please post your new MMSIM version and the convergence problems
you have.

PS: Debjit, please bear in mind I am not a Cadence employee and thus
can't help out of my working hours, i.e. 9:00 till 17:30 GMT. Sorry
for that :-(

Cheers,
Riad.
Click to expand...
Hi Riad,

Please do not be sorry. I am indebted to you for your kind help.
I will try the INCISIVE once more.
I am trying to remove the error myself. If I fails then I will post it
again in this thread.

Thanks and Regards!!!!

Cheers!!!!

Debjit.
 
On Oct 27, 2:22 pm, Debjit <debjit...@gmail.com> wrote:
On Oct 27, 1:39 pm, Riad KACED <riad.ka...@gmail.com> wrote:



Hi Debjit,

I have successfully downloaded INCISIVE 92 from sourcelink. Bear in
mind using a recent version of installScape to get Incisive. Also,
when you install iscape, you may need to configure your internet
connections, i.e the proxies, ports ... etc. Finally you just need to
install the 3 products as mentioned in the SL solutions to get IUS
from INCISIVE. Anyway, post your errors, this narrows down the issue.

I am using transition as a filter.

Again, please post your new MMSIM version and the convergence problems
you have.

PS: Debjit, please bear in mind I am not a Cadence employee and thus
can't help out of my working hours, i.e. 9:00 till 17:30 GMT. Sorry
for that :-(

Cheers,
Riad.

Hi Riad,

Please do not be sorry. I am indebted to you for your kind help.
I will try the INCISIVE once more.
I am trying to remove the error myself. If I fails then I will post it
again in this thread.

Thanks and Regards!!!!

Cheers!!!!

Debjit.
Click to expand...
Hi Riad,

I am unable to solve the problem.
The spectre version I am using from the MMSIM71 is "sub-version
7.1.1.239.isr15". I am just copying the error message printed in
spectre.out.
The message is


Error found by spectre at time = 1.0955 ms during transient analysis
`tran'.
ERROR (SPECTRE-16192): No convergence achieved with the minimum
time step specified. Last acceptable solution computed at 1.0955 ms.

The values for those nodes that did not converge on the last Newton
iteration are given below. The manner in which the convergence
criteria were not satisfied is also given.
Failed test: | Value | > RelTol*Ref + AbsTol

Top 10 Solution too large Convergence failure:
I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
update too large: | -529.518 A | > 1.12477 mA + 100 pA
I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
update too large: | -18.0457 A | > 100 uA + 100 pA
I(I26.I3.I342:fl0v5_b1_flow) = -5.58994 mA, previously -6.57264
pA.
update too large: | 708.467 mA | > 105.59 uA + 100 pA
V(I26.I3.I286.a335) = 3.6 V, previously 3.6 V.
update too large: | 3.6 V | > 13.6 mV + 100 uV
V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
update too large: | 282.587 mV | > 10.0035 mV + 100 uV
V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
update too large: | 300 mV | > 13.6 mV + 100 uV
V(I26.I3.I286.I150.pd) = 3.59572 V, previously 3.59603 V.
update too large: | 44.2445 mV | > 13.5957 mV + 100 uV
Top 10 Residue too large Convergence failure:
I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
residue too large: | 3.6 V | > 3.6 mV + 100 uV
V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
residue too large: | -498.698 A | > 908.218 mA + 100 pA
V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
residue too large: | 157.197 A | > 1.86921 A + 100 pA
I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
residue too large: | 300 mV | > 6.9 mV + 100 uV


The following set of suggestions might help you avoid convergence
difficulties.

1. Evaluate and resolve any notice, warning, or error messages.
2. Use realistic device models. Check all component parameters,
particularly nonlinear device model parameters, to ensure that they
are reasonable.
3. Small floating resistors connected to high impedance nodes might
cause convergence difficulties. Avoid very small floating resistors,
particularly small parasitic resistors in semiconductors. Instead, use
voltage sources or iprobes to measure current.
4. Ensure that a complete set of parasitic capacitors is used on
nonlinear devices to avoid jumps in the solution waveforms. On MOS
models, specify nonzero source and drain areas.
5. Perform sanity check on the parameter values using the parameter
range checker (use ``+param param-limits-file'' as a command line
argument) and heed any warnings. Print the minimum and maximum
parameter value using the `info' analysis. Ensure that the bounds
given for instance, model, output, temperature-dependent, and
operating-point (if possible) parameters are reasonable.

6. Check the direction of both independent and dependent current
sources. Convergence problems might result if current sources are
connected such that they force current backward through diodes.

7. Enable diagnostic messages by setting option `diagnose=yes'.
8. Loosen tolerances, particularly absolute tolerances like
`iabstol' (on options statement). If tolerances are set too tight,
they might preclude convergence.
9. Try to simplify the nonlinear component models in order to avoid
regions in the model that might contribute to convergence problems.

Analysis `tran' was terminated prematurely due to an error.
finalTimeOP: writing operating point information to rawfile.

Error found by spectre during DC analysis, during info `finalTimeOP'.
ERROR: Error in cleaning up IPC code in an attempt to quit.
ERROR (SPECTRE-16329): Error in DC simulation for mixed-mode.

Analysis `finalTimeOP' was terminated prematurely due to an error.
designParamVals: writing netlist parameters to rawfile.

Aggregate audit (3:23:04 PM, Tue Oct 27, 2009):
Time used: CPU = 1.79 ks (29m 52.0s), elapsed = 1.82 ks (30m 23.5s),
util. = 98.3%.
Time spent in licensing: elapsed = 55.2 ms.
Peak memory used = 130 Mbytes.
spectre completes with 3 errors, 178 warnings, and 1436 notices.



Please suggest. Also please suggest why I am not able to simulate form
GUI. It says some wrong option in the userCmdLineOption in the Setup-
Environment in ADE window. I have written the detail in my early
thread. Please suggest..
Click to expand...


Thanks and Regards,

Cheersss!!!


Debjit.
 
On Oct 27, 3:24 pm, Debjit <debjit...@gmail.com> wrote:
On Oct 27, 2:22 pm, Debjit <debjit...@gmail.com> wrote:



On Oct 27, 1:39 pm, Riad KACED <riad.ka...@gmail.com> wrote:

Hi Debjit,

I have successfully downloaded INCISIVE 92 from sourcelink. Bear in
mind using a recent version of installScape to get Incisive. Also,
when you install iscape, you may need to configure your internet
connections, i.e the proxies, ports ... etc. Finally you just need to
install the 3 products as mentioned in the SL solutions to get IUS
from INCISIVE. Anyway, post your errors, this narrows down the issue.

I am using transition as a filter.

Again, please post your new MMSIM version and the convergence problems
you have.

PS: Debjit, please bear in mind I am not a Cadence employee and thus
can't help out of my working hours, i.e. 9:00 till 17:30 GMT. Sorry
for that :-(

Cheers,
Riad.

Hi Riad,

Please do not be sorry. I am indebted to you for your kind help.
I will try the INCISIVE once more.
I am trying to remove the error myself. If I fails then I will post it
again in this thread.

Thanks and Regards!!!!

Cheers!!!!

Debjit.

Hi Riad,

I am unable to solve the problem.
The spectre version I am using from the MMSIM71 is "sub-version
7.1.1.239.isr15". I am just copying the error message printed in
spectre.out.
The message is

Error found by spectre at time = 1.0955 ms during transient analysis
`tran'.
    ERROR (SPECTRE-16192): No convergence achieved with the minimum
time step specified.  Last acceptable solution computed at 1.0955 ms.

The values for those nodes that did not converge on the last Newton
iteration are given below.  The manner in which the convergence
criteria were not satisfied is also given.
            Failed test: | Value | > RelTol*Ref + AbsTol

 Top 10 Solution too large Convergence failure:
    I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
        update too large:  | -529.518 A | > 1.12477 mA + 100 pA
    I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
        update too large:  | -18.0457 A | > 100 uA + 100 pA
    I(I26.I3.I342:fl0v5_b1_flow) = -5.58994 mA, previously -6.57264
pA.
        update too large:  | 708.467 mA | > 105.59 uA + 100 pA
    V(I26.I3.I286.a335) = 3.6 V, previously 3.6 V.
        update too large:  | 3.6 V | > 13.6 mV + 100 uV
    V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
        update too large:  | 282.587 mV | > 10.0035 mV + 100 uV
    V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
        update too large:  | 300 mV | > 13.6 mV + 100 uV
    V(I26.I3.I286.I150.pd) = 3.59572 V, previously 3.59603 V.
        update too large:  | 44.2445 mV | > 13.5957 mV + 100 uV
 Top 10 Residue too large Convergence failure:
    I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
        residue too large: | 3.6 V | > 3.6 mV + 100 uV
    V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
        residue too large: | -498.698 A | > 908.218 mA + 100 pA
    V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
        residue too large: | 157.197 A | > 1.86921 A + 100 pA
    I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
        residue too large: | 300 mV | > 6.9 mV + 100 uV

The following set of suggestions might help you avoid convergence
difficulties.

 1. Evaluate and resolve any notice, warning, or error messages.
 2. Use realistic device models. Check all component parameters,
particularly nonlinear device model parameters, to ensure that they
are reasonable.
 3. Small floating resistors connected to high impedance nodes might
cause convergence difficulties. Avoid very small floating resistors,
particularly small parasitic resistors in semiconductors. Instead, use
voltage sources or iprobes to measure current.
 4. Ensure that a complete set of parasitic capacitors is used on
nonlinear devices to avoid jumps in the solution waveforms.  On MOS
models, specify nonzero source and drain areas.
 5. Perform sanity check on the parameter values using the parameter
range checker (use ``+param param-limits-file'' as a command line
argument) and heed any warnings.  Print the minimum and maximum
parameter value using the `info' analysis.  Ensure that the bounds
given for instance, model, output, temperature-dependent, and
operating-point (if possible) parameters are reasonable.

 6. Check the direction of both independent and dependent current
sources. Convergence problems might result if current sources are
connected such that they force current backward through diodes.

 7.  Enable diagnostic messages by setting option `diagnose=yes'.
 8. Loosen tolerances, particularly absolute tolerances like
`iabstol' (on options statement). If tolerances are set too tight,
they might preclude convergence.
 9. Try to simplify the nonlinear component models in order to avoid
regions in the model that might contribute to convergence problems.

Analysis `tran' was terminated prematurely due to an error.
finalTimeOP: writing operating point information to rawfile.

Error found by spectre during DC analysis, during info `finalTimeOP'.
    ERROR: Error in cleaning up IPC code in an attempt to quit.
    ERROR (SPECTRE-16329): Error in DC simulation for mixed-mode.

Analysis `finalTimeOP' was terminated prematurely due to an error.
designParamVals: writing netlist parameters to rawfile.

Aggregate audit (3:23:04 PM, Tue Oct 27, 2009):
Time used: CPU = 1.79 ks (29m  52.0s), elapsed = 1.82 ks (30m  23..5s),
util. = 98.3%.
Time spent in licensing: elapsed = 55.2 ms.
Peak memory used = 130 Mbytes.
spectre completes with 3 errors, 178 warnings, and 1436 notices.

Please suggest. Also please suggest why I am not able to simulate form
GUI. It says some wrong option in the userCmdLineOption in the Setup->Environment  in ADE window. I have written the detail in my early

thread. Please suggest..

Thanks and Regards,

Cheersss!!!

Debjit.
Click to expand...
Hi Riad,

Which paths of INCISIVE has to be added to the PATH variable? There is
IUS92. So, should I use that instead of IUS82? Does INCISIVE contains
icfb ?

Cheers !!!!!
Debjit.
 
Debjit wrote, on 10/27/09 10:24:
Hi Riad,

I am unable to solve the problem.
The spectre version I am using from the MMSIM71 is "sub-version
7.1.1.239.isr15". I am just copying the error message printed in
spectre.out.
The message is


Error found by spectre at time = 1.0955 ms during transient analysis
`tran'.
ERROR (SPECTRE-16192): No convergence achieved with the minimum
time step specified. Last acceptable solution computed at 1.0955 ms.

The values for those nodes that did not converge on the last Newton
iteration are given below. The manner in which the convergence
criteria were not satisfied is also given.
Failed test: | Value | > RelTol*Ref + AbsTol

Top 10 Solution too large Convergence failure:
I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
update too large: | -529.518 A | > 1.12477 mA + 100 pA
I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
update too large: | -18.0457 A | > 100 uA + 100 pA
I(I26.I3.I342:fl0v5_b1_flow) = -5.58994 mA, previously -6.57264
pA.
update too large: | 708.467 mA | > 105.59 uA + 100 pA
V(I26.I3.I286.a335) = 3.6 V, previously 3.6 V.
update too large: | 3.6 V | > 13.6 mV + 100 uV
V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
update too large: | 282.587 mV | > 10.0035 mV + 100 uV
V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
update too large: | 300 mV | > 13.6 mV + 100 uV
V(I26.I3.I286.I150.pd) = 3.59572 V, previously 3.59603 V.
update too large: | 44.2445 mV | > 13.5957 mV + 100 uV
Top 10 Residue too large Convergence failure:
I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
residue too large: | 3.6 V | > 3.6 mV + 100 uV
V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
residue too large: | -498.698 A | > 908.218 mA + 100 pA
V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
residue too large: | 157.197 A | > 1.86921 A + 100 pA
I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
residue too large: | 300 mV | > 6.9 mV + 100 uV


The following set of suggestions might help you avoid convergence
difficulties.

1. Evaluate and resolve any notice, warning, or error messages.
2. Use realistic device models. Check all component parameters,
particularly nonlinear device model parameters, to ensure that they
are reasonable.
3. Small floating resistors connected to high impedance nodes might
cause convergence difficulties. Avoid very small floating resistors,
particularly small parasitic resistors in semiconductors. Instead, use
voltage sources or iprobes to measure current.
4. Ensure that a complete set of parasitic capacitors is used on
nonlinear devices to avoid jumps in the solution waveforms. On MOS
models, specify nonzero source and drain areas.
5. Perform sanity check on the parameter values using the parameter
range checker (use ``+param param-limits-file'' as a command line
argument) and heed any warnings. Print the minimum and maximum
parameter value using the `info' analysis. Ensure that the bounds
given for instance, model, output, temperature-dependent, and
operating-point (if possible) parameters are reasonable.

6. Check the direction of both independent and dependent current
sources. Convergence problems might result if current sources are
connected such that they force current backward through diodes.

7. Enable diagnostic messages by setting option `diagnose=yes'.
8. Loosen tolerances, particularly absolute tolerances like
`iabstol' (on options statement). If tolerances are set too tight,
they might preclude convergence.
9. Try to simplify the nonlinear component models in order to avoid
regions in the model that might contribute to convergence problems.

Analysis `tran' was terminated prematurely due to an error.
finalTimeOP: writing operating point information to rawfile.

Error found by spectre during DC analysis, during info `finalTimeOP'.
ERROR: Error in cleaning up IPC code in an attempt to quit.
ERROR (SPECTRE-16329): Error in DC simulation for mixed-mode.

Analysis `finalTimeOP' was terminated prematurely due to an error.
designParamVals: writing netlist parameters to rawfile.

Aggregate audit (3:23:04 PM, Tue Oct 27, 2009):
Time used: CPU = 1.79 ks (29m 52.0s), elapsed = 1.82 ks (30m 23.5s),
util. = 98.3%.
Time spent in licensing: elapsed = 55.2 ms.
Peak memory used = 130 Mbytes.
spectre completes with 3 errors, 178 warnings, and 1436 notices.



Please suggest. Also please suggest why I am not able to simulate form
GUI. It says some wrong option in the userCmdLineOption in the Setup-
Environment in ADE window. I have written the detail in my early
thread. Please suggest..


Thanks and Regards,

Cheersss!!!


Debjit.
Click to expand...
Without seeing the models and testcase it's very hard to figure out what the
root cause of the convergence problem is. It could easily be something bad in
your VerilogA model, and pretty unlikely to be magically fixed just by using
another spectre version. Sometimes it may be that you got "lucky" in an earlier
version, but the fundamental model problem remains.

Andrew.
 
Hi Debjit,

You need 3 streams to be able to run DFII, Spectre Direct and AMS
Designer:
IC for DFII
MMSIM for Spectre
IUS to run AMS Designer, and startining from 92, you need INCISIVE.
NO, IUS does not contain icfb, you need IC5141/IC613 for icfb
(virtuoso in IC6).

ANyway, if you are under C-shell, you might need to setup your
environment with the following (+ Other stuff of yours)
I'll comment the below lines afterwards if needed, don't have the time
now I'm afraid ...

###
setenv CDS_Netlisting_Mode Analog
setenv MMSIMHOME PATH_TO_YOUR_MMSIM_INSTALL_DIR
setenv AMSHOME PATH_TO_YOUR_IUS_INSTALL_DIR
setenv CDSHOME PATH_TO_YOUR_CDS_INSTALL_DIR
setenv LD_LIBRARY_PATH ${MMSIMHOME}/tools/lib:${AMSHOME}/tools/lib:$
{CDSHOME}/tools/lib
set path=($path ${MMSIMHOME}/tools/dfII/bin ${MMSIMHOME}/tools/bin)
set path=($path ${AMSHOME}/tools/dfII/bin ${AMSHOME}/tools/bin)
set path=($path ${CDSHOME}/tools/dfII/bin ${CDSHOME}/tools/bin)
###

Cheers,
Riad.
 
On Oct 27, 6:50 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
Debjit wrote, on 10/27/09 10:24:



Hi Riad,

I am unable to solve the problem.
The spectre version I am using from the MMSIM71 is "sub-version
7.1.1.239.isr15". I am just copying the error message printed in
spectre.out.
The message is

Error found by spectre at time = 1.0955 ms during transient analysis
`tran'.
    ERROR (SPECTRE-16192): No convergence achieved with the minimum
time step specified.  Last acceptable solution computed at 1.0955 ms.

The values for those nodes that did not converge on the last Newton
iteration are given below.  The manner in which the convergence
criteria were not satisfied is also given.
            Failed test: | Value | > RelTol*Ref + AbsTol

 Top 10 Solution too large Convergence failure:
    I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
        update too large:  | -529.518 A | > 1.12477 mA + 100 pA
    I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
        update too large:  | -18.0457 A | > 100 uA + 100 pA
    I(I26.I3.I342:fl0v5_b1_flow) = -5.58994 mA, previously -6.57264
pA.
        update too large:  | 708.467 mA | > 105.59 uA + 100 pA
    V(I26.I3.I286.a335) = 3.6 V, previously 3.6 V.
        update too large:  | 3.6 V | > 13.6 mV + 100 uV
    V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
        update too large:  | 282.587 mV | > 10.0035 mV + 100 uV
    V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
        update too large:  | 300 mV | > 13.6 mV + 100 uV
    V(I26.I3.I286.I150.pd) = 3.59572 V, previously 3.59603 V.
        update too large:  | 44.2445 mV | > 13.5957 mV + 100 uV
 Top 10 Residue too large Convergence failure:
    I(I26.I3.I286.I40.controller2.mode_cont:pfm_pd_flow) = 0 A,
previously 259.32 aA.
        residue too large: | 3.6 V | > 3.6 mV + 100 uV
    V(I26.I3.I286.a303) = 3.6 V, previously 3.6 V.
        residue too large: | -498.698 A | > 908.218 mA + 100 pA
    V(I26.I3.I286.I150.pdz) = -3.46482 mV, previously 7.55211 nV.
        residue too large: | 157.197 A | > 1.86921 A + 100 pA
    I(I26.I3.I286.I40.controller2.mode_cont:reset_flow) = 1.02477 A,
previously -37.559 fA.
        residue too large: | 300 mV | > 6.9 mV + 100 uV

The following set of suggestions might help you avoid convergence
difficulties.

 1. Evaluate and resolve any notice, warning, or error messages.
 2. Use realistic device models. Check all component parameters,
particularly nonlinear device model parameters, to ensure that they
are reasonable.
 3. Small floating resistors connected to high impedance nodes might
cause convergence difficulties. Avoid very small floating resistors,
particularly small parasitic resistors in semiconductors. Instead, use
voltage sources or iprobes to measure current.
 4. Ensure that a complete set of parasitic capacitors is used on
nonlinear devices to avoid jumps in the solution waveforms.  On MOS
models, specify nonzero source and drain areas.
 5. Perform sanity check on the parameter values using the parameter
range checker (use ``+param param-limits-file'' as a command line
argument) and heed any warnings.  Print the minimum and maximum
parameter value using the `info' analysis.  Ensure that the bounds
given for instance, model, output, temperature-dependent, and
operating-point (if possible) parameters are reasonable.

 6. Check the direction of both independent and dependent current
sources. Convergence problems might result if current sources are
connected such that they force current backward through diodes.

 7.  Enable diagnostic messages by setting option `diagnose=yes'.
 8. Loosen tolerances, particularly absolute tolerances like
`iabstol' (on options statement). If tolerances are set too tight,
they might preclude convergence.
 9. Try to simplify the nonlinear component models in order to avoid
regions in the model that might contribute to convergence problems.

Analysis `tran' was terminated prematurely due to an error.
finalTimeOP: writing operating point information to rawfile.

Error found by spectre during DC analysis, during info `finalTimeOP'.
    ERROR: Error in cleaning up IPC code in an attempt to quit.
    ERROR (SPECTRE-16329): Error in DC simulation for mixed-mode.

Analysis `finalTimeOP' was terminated prematurely due to an error.
designParamVals: writing netlist parameters to rawfile.

Aggregate audit (3:23:04 PM, Tue Oct 27, 2009):
Time used: CPU = 1.79 ks (29m  52.0s), elapsed = 1.82 ks (30m  23.5s),
util. = 98.3%.
Time spent in licensing: elapsed = 55.2 ms.
Peak memory used = 130 Mbytes.
spectre completes with 3 errors, 178 warnings, and 1436 notices.

Please suggest. Also please suggest why I am not able to simulate form
GUI. It says some wrong option in the userCmdLineOption in the Setup-
Environment  in ADE window. I have written the detail in my early
thread. Please suggest..

Thanks and Regards,

Cheersss!!!

Debjit.

Without seeing the models and testcase it's very hard to figure out what the
root cause of the convergence problem is. It could easily be something bad in
your VerilogA model, and pretty unlikely to be magically fixed just by using
another spectre version. Sometimes it may be that you got "lucky" in an earlier
version, but the fundamental model problem remains.

Andrew.
Click to expand...
Hi Riad and Andrew,

Whats about the userCmdLineOption ? I cannoit run the spectre of MMSIM
from GUI. Please suggest.

Cheers!!!
Debjit.
 
Hi Debjit,

We keep answer your questions and you wouldn't answer ours, i.e. post
your verilog-A code ... etc. We might be waisting our time for a silly
mistake in your code, sorry for being a bit cheeky :-(

Why are you talking about userCmdLineOption now ? this is a field in
the GUI to provide spectre with additional arguments that are not
available from ADE.
I'm confused ...

Cheers,
Riad.
 
On Oct 29, 6:02 pm, Riad KACED <riad.ka...@gmail.com> wrote:
Hi Debjit,

We keep answer your questions and you wouldn't answer ours, i.e. post
your verilog-A code ... etc. We might be waisting our time for a silly
mistake in your code, sorry for being a bit cheeky :-(

Why are you talking about userCmdLineOption now ? this is a field in
the GUI to provide spectre with additional arguments that are not
available from ADE.
I'm confused ...

Cheers,
Riad.
Click to expand...
Hi Riad,

I cannot post the code in this open forum. But I can send you the code
in your gmail id. Will it be Ok? I have no problem sending the code to
you and Andrew. I will be very fortunate if you check the code. Please
reply.

But I am getting the userCmdLineOption in the ADE i.e. Setup - >
Environment. There are some defaults values in the field. But it is
not working for me whenever I am trying to simulate from GUI. But it
ran fine from command line by ./runSimulation. Please suggest.

Thanks and Regards,

Cheers!!!
Debjit.
 
Hi Debjit,

If you can't post your code, then you can't send it to me for the very
same reasons. I am not a Cadence employee and I did not sign any NDA
with you anyway. So please do not send anything at all. The best way
for you in this case is to get in touch with your cadence Customer
Support.

As per the second item, please (again) post your error. a statement
like 'ut it is not working' does not really help I'm afraid. If it is
not confidential, please post the following
1. spectre -W
2. the arguments your are using in the userCmdLineOption in the ADE
3. the runSimulation script
4. the error message.

Cheers,
Riad.
 
On Oct 30, 11:11 pm, Riad KACED <riad.ka...@gmail.com> wrote:
Hi Debjit,

If you can't post your code, then you can't send it to me for the very
same reasons. I am not a Cadence employee and I did not sign any NDA
with you anyway. So please do not send anything at all. The best way
for you in this case is to get in touch with your cadence Customer
Support.

As per the second item, please (again) post your error. a statement
like 'ut it is not working' does not really help I'm afraid. If it is
not confidential, please post the following
1. spectre -W
2. the arguments your are using in the userCmdLineOption in the ADE
3. the runSimulation script
4. the error message.

Cheers,
Riad.
Click to expand...
Hi Riad,

Ok I will post the items for the second error on Monday as I am out
for a few days from my university.

Thanks and Regards!!!

Cheers!!!
Debjit.
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top