The Designer's Guide Community Forum

The Designer's Guide Community Forum
https://designers-guide.org/forum/YaBB.pl
Modeling >> Semiconductor Devices >> use of BSIM4 source code
https://designers-guide.org/forum/YaBB.pl?num=1196175062

Message started by tariavo on Nov 27^th, 2007, 6:51am

Title: use of BSIM4 source code
Post by tariavo on Nov 27^th, 2007, 6:51am

Hi, do you use BSIM4 code for calculation of MOSFET params?
I've found the inclusion of 'spice.h' and others headers that are not in BSIM's code distribution.
Where can it be found?

Title: Re: use of BSIM4 source code
Post by krishnap on Nov 28^th, 2007, 3:21am

it is cumbersome to use BSIM equations for hand calculation of MOS parameters.
However these are implemented in the spice tool and model card is input to these equations,
so that simulation results are almost closer to silicon behaviour.

Title: Re: use of BSIM4 source code
Post by tariavo on Nov 28^th, 2007, 4:16am

i dont mean the _hand_ calculation of MOSFET's params - i want to calculate it without any 3rd party tool.
(really i calculated it by hand, but there were some departures between real and calculated params and i decided to use BSIM source code)
For these reasons I'd like to use BSIM4 source code but some questions arised:
BSIM4 source code include headers with (routine?) definitions =>
what do BSIM need for its work?

Title: Re: use of BSIM4 source code
Post by Geoffrey_Coram on Nov 28^th, 2007, 7:56am

You can get the source code of spice (spice3f5.tar.gz or spice3f5.tgz) somewhere, try a Google search. It's open-source software from Berkeley.

That said, I don't think you should need any of the definitions in that file to evaluate the model equations -- other than, say, a thermal noise function that might take the resistance or conductance and multiply by 4 k T.

Title: Re: use of BSIM4 source code
Post by Marq Kole on Mar 19^th, 2008, 1:36pm

Hi,

Yes, you do need access to the SPICE3 code to compile the BSIM4 model - the spice.h is retrieved from the Berkely SPICE3F5. If you would use ngspice instead the same header file would probably be available.

Cheers,
Marq