Stats

  • Locked Locked
  • Replies 9
  • Subscribers 126
  • Views 16318
  • 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

Are there any semiconductor vendor-supplied models in IC stream?

achilles

I am thinking these files contain standard models; how do we know the names of the models included? and how do we use them? 

cmi.pic.o  libphilips_sh.so  libinfineon_sh.so  libstmodels_sh.so  libsparam_sh.so  defaultConfig

 Thanks,

 

Parents

  • Hi Achilles,

    Why does there need to be a "published interface" for these files? They are part of the software installation, and simply part of the way that the simulator executable is delivered. There is a C Model Interface which is available to customers who purchace it (it's a licensed product) which allows custom models to be written, but that's relatively rare and typically only used by large customers who have existing proprietary device models (not proprietary device model parameters, but proprietary model implementations). 

    We don't document any of the other shared libraries which are part of the software installation, so there's no reason why these should be either. The "interface" to them is to define (for example):

    model nch psp102 type=n tox=3e-9 ...

    Just as you would any other model.

    The reason why the analogLib components netlist four terminals (even for the 3 terminal components) is because in spectre all (as far as I know) MOS models have 4 terminals. Some models (e.g. jfet, bjt etc) have an optional 4th terminal - but from looking at mos1, mos2, mos3, bsim3v3, bsim4, psp102, they all expect a bulk node. Which model are you using that requires only 3?

    analogLib is really just a sample library. Most design kits would provide specific components to netlist whatever model names that are being provided by that design kit, but it's straightforward enought to customise to suit your needs.

    Regards,

    Andrew.

     

Reply

  • Hi Achilles,

    Why does there need to be a "published interface" for these files? They are part of the software installation, and simply part of the way that the simulator executable is delivered. There is a C Model Interface which is available to customers who purchace it (it's a licensed product) which allows custom models to be written, but that's relatively rare and typically only used by large customers who have existing proprietary device models (not proprietary device model parameters, but proprietary model implementations). 

    We don't document any of the other shared libraries which are part of the software installation, so there's no reason why these should be either. The "interface" to them is to define (for example):

    model nch psp102 type=n tox=3e-9 ...

    Just as you would any other model.

    The reason why the analogLib components netlist four terminals (even for the 3 terminal components) is because in spectre all (as far as I know) MOS models have 4 terminals. Some models (e.g. jfet, bjt etc) have an optional 4th terminal - but from looking at mos1, mos2, mos3, bsim3v3, bsim4, psp102, they all expect a bulk node. Which model are you using that requires only 3?

    analogLib is really just a sample library. Most design kits would provide specific components to netlist whatever model names that are being provided by that design kit, but it's straightforward enought to customise to suit your needs.

    Regards,

    Andrew.

     

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.