Overview

Source Code & Library

The files containing the level 1 and level 200 code are "device_juncap.c" and "device_juncap2.c" respectively. If you use the included solver, please make sure that you compile on a system that supports Fortran 77.

The source code for Juncap level 200 has been automatically generated from a Verilog-A description of the model.

The models are included in a dynamically loaded library called SiMKit. SiMKit is related to the following circuit simulators used within NXP:

  • Pstar, the circuit simulator from NXP
  • Spectre, the circuit simulator from Cadence
  • ADS, the circuit simulator from Agilent.
  • You can read how to download and install the libraries here.

Model definition of Juncap

The definition of the Juncap model Level 1 and level 200 are available in PDF format in the documentation tab.

Juncap, level 1. This model describes
  • Depletion capacitance
  • Ideal diode current
  • Reverse leakage current due to Shockley-Read-Hall generation

Juncap, level 200. This model is a major update of the JUNCAP level 1 model. It models all the effects already present in level 1, and has many new features:

  • Depletion capacitance
  • Ideal diode current
  • Shockley-Read-Hall recombination and generation currents (in forward and reverse regimes)
  • Trap-assisted tunnelling (in forward and reverse regimes)
  • Band-to-band tunnelling
  • Avalanche breakdown
  • Shot noise

The SiMKit C-code for Juncap level 200 has been automatically generated from a Verilog-A description of the model. The functionality of this SiMKit C-code is the same as that of the Verilog-A. The Verilog-A code of Juncap level 200 can be downloaded from the TU Delft PSP website.

Juncap level 200

Since the updates for SiMKit 3.1 (May 2008) the code history is included in the model history. Older code history can be found below.

Below is an overview of the relation between level and code versions.


Juncap 200 SiMKit
level.version.implementation code revision release date
200.5.0 - 4.8.1 2017-02-10
200.4.0 - 4.7 2016-06-16
200.4.0 - 4.6 2015-12-18
200.4.0 - 4.5 2015-05-22
200.4.0 - 4.4 2015-01-06
200.4.0 - 4.3 2014-08-05
200.4.0 r14265 4.2 2014-01-21
200.4.0 1.179 4.1 2013-07-12
200.4.0 1.172 4.0.1 2013-01-25
200.3.5 1.171 4.0 2012-07-25
200.3.4 1.125 3.8 2012-02-02
200.3.4 1.118.2.1 3.7 2011-08-04
200.3.4 1.109 3.6 2011-01-18
200.3.4 1.101 3.5.2 2010-10-12
200.3.4 1.84 3.4 2009-12-17
200.3.3 1.83 3.2, 3.3 2009/06/25
200.3.2 1.77 3.1.2 2008/07/24
200.3.1 1.76 3.1 2008/05/21
200.3.0 1.65.2.3 3.0.3 2008/01/31
200.2.1 1.49 2.5 2007/04/30
200.2.0 1.39 2.4 2006/10/23
200.1.2 1.27.2.1 2.3.2 2006/07/07
200.1.1 1.27 2.3 2006/03/16
200.1.0 1.23 2.2 2005/08/03
200.0.1 1.14 2.11 2005/04/11


2017/02 Release of Juncap 200.5.0
2015/05 The diode_region parameter is available.
2015/01 Speed improvement (up to 3%) for juncap by avoiding unnecessary computation of some absolute values.
2014/01 Improved region settings resulting in faster simulations (up to a factor of 3) with APS in some cases.
  An initialization error was corrected, resulting in safer and better convergence in some cases.
  Some non-initialized variables were not calculated for some corner cases, leading to unpredictable results. This was corrected.
2013/01 Release of Juncap 200.4.0
2012/07 Release of Juncap 200.3.5
 
  • The interface of the simkit model has been changed.
2011/08 Release of Juncap 200.3.4
 
  • The scaled parameters of the model Juncap2 are added to the DC operating point information.
  • When the instance parameter MULT is set to zero, the model evaluation is done more efficiently. All OP output for the device is set to zero in this case.
2010/10 Release of Juncap 200.3.4
 
  • Juncap 200 has been implemented in a thread-safe way
2008/12 Release of Juncap model, 200.3.3
 
  • Fixed bug in FJUNQ-based selection-criterion in JUNCAP-express charge model.
2008/05 Release of Juncap model, 200.3.1
  minor code changes
2008/01 Release of Juncap model, 200.3.0
  The newly introduced express-option of the JUNCAP2 model, invoked bysetting SWJUNEXP=1, allows the user to trade some simulation accuracyfor simulation speed. In transient analyses, a simulation time reductionof up to a factor of 5 (of the simulation time associated with JUNCAP2)has been demonstrated with a very limited loss of accuracy. This isachieved by a creating a strongly simplified IV-model, combined with amore extensive initialisation code.
2006/10 Release of Juncap model, 200.2.0
 
  • The band-to-band tunneling equations have been modified. At temperatures lower than the reference temperature, Vj can become lower than VBIR. This caused numerical problems in the model, which in turn resulted sometimes in convergence problems in the simulator. An alternative formulation of the equations has been implemented that avoids these problems.
  • Some minor bugfixes.
2005/08 Release of Juncap model, 200.1.0
2005/03 Release of Juncap model, 200.01.0, test version
1988/10 Introduction of the Juncap model, level 1.

Juncap level 1

Below is an overview of the relation between level and code versions.


Juncap 1 SiMKit
level.version.implementation code revision release date
1.1.8 - 4.8.1 2017-02-10
1.1.8 - 4.7 2016-06-16
1.1.8 - 4.6 2015-12-18
1.1.8 - 4.5 2015-05-22
1.1.8 - 4.4 2015-01-06
1.1.8 - 4.3 2014-08-05
1.1.8 - 4.2 2014-01-10
1.1.8 1.191 4.1 2013-07-12
1.1.8 1.185 4.0 2012-07-25
1.1.7 1.134 3.8 2012-02-02
1.1.7 1.130.2.1 3.7 2011-08-04
1.1.7 1.121.2.4 3.6 2011-01-18
1.1.6 1.110 3.5.2 2010-10-12
1.1.5 1.86 3.4 2009-12-17
1.1.4 1.84 3.3 2009/06/25
1.1.3 1.82.2.3 3.2 2008/07/24
1.1.2 1.80 3.1.2 2008/12/02
1.1.2 1.80 3.1 2008/05/21
1.1.1 1.77.2.1 3.0.3 2008/01/31
1.1.1 1.66 2.5 2007/04/30
1.1.0 1.59 2.4 2006/10/23
1.0.0 1.53 2.3 2006/03/16

2015/05 The diode_region parameter is available.
2015/01 Speed improvement (up to 3%) for juncap by avoiding unnecessary computation of some absolute values.
2014/01 Improved region settings resulting in faster simulations (up to a factor of 3) with APS in some cases.
An initialization error was corrected, resulting in safer and better convergence in some cases.
Some non-initialized variables were not calculated for some corner cases, leading to unpredictable results. This was corrected.
2012/07 Release of Juncap 1.1.8
 
  • The interface of the model has been changed.
2011/01 Release of Juncap 1.1.7
 
  • A new instance parameter PRINTSCALED has been added to this model. When PRINTSCALED is set to any value other than zero (the default) the model will print the scaled parameters of the model when the DC operating point information is printed.
  • Minor code change:
    Situations where “pow()”, calculating x^y with y==0.5 are now avoided by using the sqrt() function.
2010/10 Release of Juncap 1.1.6
  Juncap has been implemented in a thread-safe way
2009/06 Release of Juncap model,1.1.4
  Minor code changes
2008/12 Release of Juncap model,1.1.3
  Extended the model with type parameter. The default for type is such that backwards compatibility is guaranteed.
1988/10 Introduction of the Juncap model, level 1.

Juncap level 200

The table below outlines the major changes to the file called "device_juncap2.c", which can be found in the source code.


2008/01/31 Juncap model 200.3.0
  Code changes
 
  • See 200.3 in the model history above
  • New flexible topology architecture implemented
  • Small improvement in noise implementation for non-correlated noise sources
2007/04/30 Juncap model 200.2.1 is identified in the code as revision 1.49. All code differences with the previous version (200.2.0) can be found in this diff file
  Code changes
 
  • In Pstar and ADS a specific bug could cause a memory fault when PAC or Pnoise analysis was used. This bug has been solved.
  • Several actions for speeding up the model evaluation.
2006/10/23 Juncap model 200.2.0, which is identified in the code as revision 1.39. All code differences with the previous version (200.1.0) can be found in this diff file
  Implemented Model changes
 
  • See release 200.2 in the model history above
  Other code changes
  None
2006/07/07 Juncap model 200.1.2, which is identified in the code as revision 1.27.2.1. All code differences with the previous version (200.1.1) can be found in this diff file
  Other code changes
  Some minor modifications
2006/03/16 Juncap model 200.1.1, which is identified in the code as revision 1.27. All code differences with the previous version (200.1.0) can be found in this diff file
  Implemented model changes
  Other code changes
  Some minor modifications
2005/08/03 Juncap model 200.1.0, which is identified in the code as revision 1.23. All code differences with the previous version (200.0.1) can be found in this diff file
  Implemented model changes
  Efficient limiting functions have been implemented
  Other code changes
  None
2005/04/11 Juncap model 200.0.1 identified in the code as revision 1.14.
  Release of Juncap model, level 200
Known bugs

There are no known bugs in the Juncap model.

Juncap level 1

The table below outlines the major changes to the file called "device_m3100i.c", which can be found in the source code

2007/04/30 Juncap model 1.1.1 is identified in the code as revision 1.66. All code differences with the previous version (1.1.0) can be found in this diff file.
  Code changes:
 
  • In the past, differences were seen in the leakage current of the Juncap for different Spectreversions. The leakage current in the Juncap is now correct for all Spectre versions.
  • Three new OP parameters have been added to the Juncap device:lx1, the total current; lx3, the total charge; lx5, the total capacitance
  • In SiMKit 2.4 there were circumstances under which the Juncap conductance became zero. This problem has been solved in SiMKit 2.5 by placing a parallel gmin resistance.
2006/10/23 Juncap model 1.1.0, which is identified in the code as revision 1.59. All code differences with the previous version (1.0.0) can be found in this diff file.
   
 
  • Parameters VDB (diffusion voltage of bottom area), VDS (diffusion voltage of Locos-edge), VDG (diffusion voltage of gate edge) now give clipping warnings.
  • Implementation for MULT=0 is more efficient.
Known bugs

There are no known bugs in the Juncap model.