Stats

Locked Locked
Replies 5
Subscribers 126
Views 11174
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ADE XL Not including Spectre Models

I have checked google and the forums and I can't seem to find a solution that I am not already implementing.

I am unable to get ADE XL to include the spectre models provided by the PDK when running simulation. I am able to get it to include models for different PDKs but not the one I am using (I need this PDK rather than the others because of the bounds of the application and what the PDK supports). The model files definitely do exist as I can find them in the PDK's directory, and I have the required statement in the .cdsenv to include them, but when I go to run ADE XL, the models are not included in the input.scs. When I open the input.scs it is just missing the include statements in the header.

Is there a setting I am missing in ADE XL that tells it to build the input.scs with the models included?

For specifics:

This is an example error statement I am getting through ADE XL, however, I get it for every component in the circuit and subcircuits:

ERROR (SFE-23): "input.scs" 14: The instance `T3' is referencing an undefined model or subcircuit, `lvtpfet'. Either include the file containing the definition of `lvtpfet', or define `lvtpfet' before running the simulation.

I am using SPECTRE161, EDI142. IC618, and oa_v22.60.007

Parents

Holz over 4 years ago

Hi,

have you checked in your test editor

Setup-> model libraries, is the spectre model in it?
Cancel
Vote Up 0 Vote Down

Cancel
Zachary Nelson over 4 years ago in reply to Holz

It is not getting filled. When I open other technologies those fields are filled automatically.

I tried setting it myself but it looks like the transistors I am using inherit from another spectre model in the PDK.
Cancel
Vote Up 0 Vote Down

Cancel
Holz over 4 years ago in reply to Zachary Nelson

I had the same problem yesterday. For me, the spectre model is in /GF/22FDX-EXT/V1.0_2.0b/Models/Spectre/models because I'm using GF lib. I just add it into model libraries and it works
Cancel
Vote Up 0 Vote Down

Cancel
Zachary Nelson over 4 years ago in reply to Holz

I am using an ibm library, unfortunately, this doesn't seem to solve it for me.
Cancel
Vote Up 0 Vote Down

Cancel
Andrew Beckett over 4 years ago in reply to Zachary Nelson

Whether Setup->Model Libraries is completed for you is a function of the PDK; usually there's an envSetVal or asiSetEnvOptionVal to set modelFiles in the libInit.il of the technology or device library. However, some PDKs do not do this at all. You should take that up with the foundry - and also, if the model setup isn't working even if you fill it out yourself, then that's also a question for the foundry (unless it's covered in their documentation of course).

Regards,

Andrew
Cancel
Vote Up 0 Vote Down

Cancel

Reply

Andrew Beckett over 4 years ago in reply to Zachary Nelson

Whether Setup->Model Libraries is completed for you is a function of the PDK; usually there's an envSetVal or asiSetEnvOptionVal to set modelFiles in the libInit.il of the technology or device library. However, some PDKs do not do this at all. You should take that up with the foundry - and also, if the model setup isn't working even if you fill it out yourself, then that's also a question for the foundry (unless it's covered in their documentation of course).

Regards,

Andrew
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.