Main Page | Report this Page
Computers Forum Index  »  Computer - Cadence  »  AHDLCMI Module Problem...
Page 2 of 2    Goto page Previous  1, 2

AHDLCMI Module Problem...

Author Message
Andrew Beckett...
Posted: Tue Oct 27, 2009 5:50 pm
Guest
Debjit wrote, on 10/27/09 10:24:
Quote:
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.
 
Riad KACED...
Posted: Thu Oct 29, 2009 1:02 pm
Guest
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.
 
Debjit...
Posted: Fri Oct 30, 2009 9:07 am
Guest
On Oct 29, 6:02 pm, Riad KACED <riad.ka... at (no spam) gmail.com> wrote:
Quote:
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.

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.
 
Riad KACED...
Posted: Fri Oct 30, 2009 6:11 pm
Guest
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.
 
Debjit...
Posted: Sat Oct 31, 2009 2:08 pm
Guest
On Oct 30, 11:11 pm, Riad KACED <riad.ka... at (no spam) gmail.com> wrote:
Quote:
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.

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.
 
Debjit...
Posted: Thu Nov 12, 2009 6:05 am
Guest
On Oct 31, 7:08 pm, Debjit <debjit... at (no spam) gmail.com> wrote:
Quote:
On Oct 30, 11:11 pm, Riad KACED <riad.ka... at (no spam) 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.

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.


Hi Riad,

Sorry for the late post. I was out of station in the previous week.
This error message is generated whenever I try to run the spectre from
MMSIM package in GUI. The following details are given below:

spectre -W returns "sub-version 7.1.1.239.isr15"
icfb -W returns "sub-version 5.10.41.500.6.139"

Should you need any more info please feel free to ask me. The
userCmdLineOptions in the ADE->Setup->Environment is specified as "
+lqt 900 +lqs 30" .


*Error* Errors encountered during simulation. The simulator run log
has not been generated.
\e Possible cause could be an invalid command line option for the
version of the simulator
\e you are running. Choose Setup->Environment and verify that the
command line options
\e specified in the userCmdLineOption field are supported for the
simulator.
\e Alternatively, run the simulator standalone using the runSimulation
file in the netlist
\e directory to know the exact cause of the error.


Thanks and Regards

Cheersss!!!


Debjit
 
Andrew Beckett...
Posted: Thu Nov 12, 2009 11:19 pm
Guest
Debjit wrote, on 11/12/09 06:05:
Quote:

Hi Riad,

Sorry for the late post. I was out of station in the previous week.
This error message is generated whenever I try to run the spectre from
MMSIM package in GUI. The following details are given below:

spectre -W returns "sub-version 7.1.1.239.isr15"
icfb -W returns "sub-version 5.10.41.500.6.139"

Should you need any more info please feel free to ask me. The
userCmdLineOptions in the ADE->Setup->Environment is specified as "
+lqt 900 +lqs 30" .


*Error* Errors encountered during simulation. The simulator run log
has not been generated.
\e Possible cause could be an invalid command line option for the
version of the simulator
\e you are running. Choose Setup->Environment and verify that the
command line options
\e specified in the userCmdLineOption field are supported for the
simulator.
\e Alternatively, run the simulator standalone using the runSimulation
file in the netlist
\e directory to know the exact cause of the error.


Thanks and Regards

Cheersss!!!


Debjit

Hi Debjit,

In the CIW, try doing:

sh("xterm -e csh -f &")

and then cd to the simulation directory, and do the ./runSimulation

That way you should be seeing the environment that virtuoso is seeing -
otherwise your shell environment may be altering things and giving a false
impression. Also check the versions of spectre used in such cases.

Regards,

Andrew.
 
 
Page 2 of 2    Goto page Previous  1, 2
All times are GMT
The time now is Fri Nov 27, 2009 4:21 pm