• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. model file

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14774
  • 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

model file

auto dipper
auto dipper over 11 years ago
Hi Aandrew .

as per your comment @

i have started that conversation in this new post. i hope this is the way you desired ? below is the question i had posted in the previous post related to this topic.

"Hi all,

I have an accademic level spice model file for nmos and pmos. I want toinclude this file in the model library path for simulation purposes.Although i have included it in ADE by Setup-> model libraries buti am still getting the below error after netlist & run -

“ERROR(SFE-23): "input.scs" 39: M0 is an instance of an undefinedmodel equal_vt0”

whereequal_vt0.m is the name of the model file."

-------------------------------------------

Actually i have included the models for ami06N & ami06P so errors with respect to those have got removed but i want to replace all the ami06N nmos4 models with a nmos model whose model file is as attached with this comment. So how can it be done. I tried to use a general nmos from AnalogLib and enter parameters (source permeter etc..) into it as per this file but then i got the error as i mentioned first in this comment.

Regards
  • equal_vt0.txt
  • View
  • Hide
  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    But you still have:

    .model equal_vt0 nmos4 ...

    but it should be (as I said earlier in this confusing thread):

    .model equal_vt0 nmos ...

    It's not surprising that it doesn't work since spectre has no primitive called "nmos4".

    Andrew 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information