The Designer's Guide Community Forum

The Designer's Guide Community Forum
https://designers-guide.org/forum/YaBB.pl
Simulators >> Circuit Simulators >> Re: Error with spectre
https://designers-guide.org/forum/YaBB.pl?num=1106430105

Message started by L.O.R. on Jan 22^nd, 2005, 1:41pm

Title: Re: Error with spectre
Post by L.O.R. on Jan 22^nd, 2005, 1:41pm

Has anybody know where to find the logfile when spectre refuses to run and generate this error?
Error found by spectre.
Failed to run the analyses in the control file.

I encountered this problem when I tried to run some parameters sweep using Ocean. The first simulation requested via the "run()" works fine, however, the subsequent requests for simulation results in Spectre producing the above error message.

Does anyone know where I can find the logfile or other places where I might find out what is the generating this error generated by Spectre? Thanks!

P.S. Simulation was carried out in Ocean's text interface and Cadence 5.0.33 was used.

P.S. Similar ocean scripts had been used in previous installation of Cadence without ever encoutering this error.

Title: Re: Error with spectre
Post by Andrew Beckett on Jan 23^rd, 2005, 12:19pm

I've seen this problem when using spectre's assert statements, and then doing a parametric analysis.

If so, it was fixed as a result of PCR 686439 in subversion 5.0.33.500.1.12

Are you using a subversion before that? (Note, if the
subversion only has 5 sets of numbers, it is before that,
since the numbering scheme changed to insert an
additional digit indicating which USR the ISR is based on).

Regards,

Andrew.

Title: Re: Error with spectre
Post by L.O.R. on Jan 24^th, 2005, 2:37am

The cadence that I using is 5.0.33_USR2.34.8 and looking through the model files, I found an assert statement embedded in the VBIC model used for the NPN bipolar junction transistor.

Do you know any workaround solution to this problem?
Thanks!

Title: Re: Error with spectre
Post by Andrew Beckett on Jan 24^th, 2005, 3:48pm

Well, try commenting out the assert to see if that fixes it. If it does, log it with Cadence Customer Support... (although you might want to try the latest ISR first).

Clearly something was left unfixed by the PCR I was mentioning, or it's a different (but possibly related) problem.

Regards,

Andrew.

Title: Re: Error with spectre
Post by Andrew Beckett on Jan 24^th, 2005, 3:49pm

Actually you could probably also put a checklimit statement in an include file to tell it to turn off all assertion checks. Do spectre -h checklimit for more details (I'm off the Cadence network at the moment so can't easily check).

Andrew.