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

  • Achilles,

    The compiled model interface is a product which provides the means to create such shared libraries - in other words, it describes the available API in the simulator, and the interface to which the compiled model code must conform. There is no public API for any other tool to use these shared libraries - they are solely for the use of Cadence simulators, so there is absolutely no benefit in any user knowing how to interface to them.

    From your example (which I will edit to remove the contents, as I doubt you are allowed to post it on a public web site as it is probably the property of Infineon - please be careful about posting proprietary information such as this without permission from the vendor), it is a 3 terminal subckt. Equally possible would  be a 4 terminal, or 5 terminal, or 6 terminal model - depending on the discrete component. If you have different types of devices, there is always likely to be some customization to the symbol and CDF needed to suit that.

    Given that most of the transistor models that users would use with analogLib components are on-chip (rather than discrete), it makes sense for the examples to all match those. And it's trivial to take the examples in analogLib and adapt them to whatever you actually need - all you have to do is copy the nmos or pmos component and change the CDF and remove the bulk terminal on the spectre view (or you could copy the symbol across to the spectre view, say).

    Best Regards,

    Andrew.

Reply

  • Achilles,

    The compiled model interface is a product which provides the means to create such shared libraries - in other words, it describes the available API in the simulator, and the interface to which the compiled model code must conform. There is no public API for any other tool to use these shared libraries - they are solely for the use of Cadence simulators, so there is absolutely no benefit in any user knowing how to interface to them.

    From your example (which I will edit to remove the contents, as I doubt you are allowed to post it on a public web site as it is probably the property of Infineon - please be careful about posting proprietary information such as this without permission from the vendor), it is a 3 terminal subckt. Equally possible would  be a 4 terminal, or 5 terminal, or 6 terminal model - depending on the discrete component. If you have different types of devices, there is always likely to be some customization to the symbol and CDF needed to suit that.

    Given that most of the transistor models that users would use with analogLib components are on-chip (rather than discrete), it makes sense for the examples to all match those. And it's trivial to take the examples in analogLib and adapt them to whatever you actually need - all you have to do is copy the nmos or pmos component and change the CDF and remove the bulk terminal on the spectre view (or you could copy the symbol across to the spectre view, say).

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