• 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. mosfet model spice/pspice

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 124
  • Views 4543
  • 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

mosfet model spice/pspice

RobinCommander
RobinCommander over 5 years ago

I am simulating a discrete mos device in Spectre.

If I treat it as a spice model the drain-source current is much too low (mA vs amps expected). If I treat it as a pspice model it is good. The model is not supposed to Pspice specific and works OK in other simulators.

Any ideas what might be going on?

.MODEL PMOS PMOS LEVEL = 3 U0 = 400 VMAX = 1E+006 ETA = 0.001
+ TOX = 6E-008 NSUB = 1E+016 KP = 26.45 KAPPA = 19.32 VTO = -0.6929

  • Cancel
Parents
  • wgtkan
    wgtkan over 5 years ago

    Hello Robin,

    Even though it says level 3 model, it is missing lots of level 3 model parameters such as GAMMA (the bulk threshold parameter), the Sheet Resistance(RSH), lateral diffusion length (LD), the bulk junction potential (PB), 

    the surface mobility (U0), and the capacitances, CGSO, CGDO, CJSW, CJ and without these values specified it will take on the default values.  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to wgtkan

    Robin,

    U0 is in the model file (I believe U0 and UO are aliases) - however, Spectre reports that there's an inconsistency between kp and uo.

    Notice from spectre during initial setup.
    PMOS: Values of `kp' and `uo' are not consistent.
    PMOS: `cgso' is not specified. 0.1um * Cox is used.
    PMOS: `cgdo' is not specified. 0.1um * Cox is used.

    Anyway, what I did to check was the following:

    // pick one or the other
    pspice_include "forum75mod.sp"
    //include "forum75mod.sp"

    M1 (d g vdd vdd) PMOS w=10u l=2u
    Vdd (vdd 0) vsource dc=5
    Vd (d 0) vsource dc=3
    Vg (g 0) vsource dc=3

    dc dc
    models info what=models where=file

    This produced forum75.info.models which listed the model parameters, and I did a diff:

    UNIX> diff forum75.info.models_spectre forum75.info.models_pspice
    13c13
    < uo = 459.583 Mcm^2/V*s
    ---
    > uo = 600 cm^2/V*s
    124c124
    < compatible = spectre
    ---
    > compatible = pspice

    So the difference is in the compatibility layer for MOS3 related to how UO is handled. Whilst the model is not specifically for PSPICE, the chances are it is for a SPICE typically used for discrete devices and those are likely to be compatible with PSPICE.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RobinCommander
    RobinCommander over 5 years ago in reply to Andrew Beckett

    Andrew,

    Thanks. The value 600 cm^2/V*s for uo seems to be a spice default for this value. I tried removing KP and/or U0 from the model and setting U0 to 600 but I couldn't get the correct behaviour so I shall just carry on treating it as a pspice model.

    Regards,

    Robin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to RobinCommander

    Robin,

    That would generally be my advice when using a SPICE model of a discrete component; usually using PSPICE compatibility mode is the best solution then.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Andrew Beckett

    Hi Robin,

    In addition, I looked in the Spectre Circuit Simulator Components and Device Models Reference manual (<SPECTREinstDir>/doc/spectremod/spectremod.pdf) in the Common MOSFET Equations chapter (chapter 12). There's a section Parameters Common to Levels 1-3 Only which (near the end of that section, on page 1033/1034 in SPECTRE181 or 1034/1035 in SPECTRE191) which describes what happens when both uo and kp are specified, and the difference between spectre and other SPICE simulators (it doesn't explicitly mention PSPICE, because PSPICE compatibility is more recent than the model manual has been updated, but it's similar).

    Hope that helps too,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RobinCommander
    RobinCommander over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    That gave me some idea of what is going on. I think Vdsat modelling is involved as the Vdsat value in the simulator was 2e-5 when I treated it as a spice model. Setting VMAX=3e12 in the model gave approximately the right behaviour but could have other effects so I will stick with using the original model as a Pspice model.

    Thanks,

    Robin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • RobinCommander
    RobinCommander over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    That gave me some idea of what is going on. I think Vdsat modelling is involved as the Vdsat value in the simulator was 2e-5 when I treated it as a spice model. Setting VMAX=3e12 in the model gave approximately the right behaviour but could have other effects so I will stick with using the original model as a Pspice model.

    Thanks,

    Robin

    • 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.

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

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