Title: List of Bugs in BSIM4.0.0 & Proposed Bug Fixes
=====================================================

  Weidong Liu, Xiaodong Jin, Mark Cao, and Chenming Hu
  Project Director: Prof. Chenming Hu


  The following is a list of the bugs found in BSIM4.0.0 along with
the proposed bug fixes, which have been evaluated by BSIM team and
the bug reporters. However, these bugs and fixes are not the finalized
ones and have to be further evaluated and approved by Compact Model
Council (CMC) member companies (Please see "CMC's Bug Reporting and
Resolution Procedure" attached at the bottom of this file). Thus, they
should not be included in any commercial production releases.

  Any new bugs found in BSIM4.0.0 in the future, along with proposed
corresponding bug fixes, will be added in this file.

  The finalized bug fixes approved by CMC member companies will
be posted on this web site in a separate file under the BSIM4.0.0
section.


Bug 1:
------
  Bug reporters: Weidong Liu, Xiaodong Jin, Mark Cao, and Chenming Hu
  C files involved: b4check.c
  C code containing the bug:

        if ((here->BSIM4rgateMod == 2) || (here->BSIM4rgateMod == 3))
        {   if ((here->BSIM4trnqsMod == 1) || (here->BSIM4acnqsMod == 1))
            fprintf(fplog, "Warning: You've selected both Rg and charge
                    deficit NQS; select one only.\n");
            printf("Warning: You've selected both Rg and charge deficit
                    NQS; select one only.\n");
        }

  Proposed bug fix:

        if ((here->BSIM4rgateMod == 2) || (here->BSIM4rgateMod == 3))
        {   if ((here->BSIM4trnqsMod == 1) || (here->BSIM4acnqsMod == 1))
            {   fprintf(fplog, "Warning: You've selected both Rg and charge
                        deficit NQS; select one only.\n");
                printf("Warning: You've selected both Rg and charge deficit
                       NQS; select one only.\n");
            }
        }


Bug 2:
------
  Bug reporters: Kiran Kumar Gullapalli (Motorola Inc.)
  C files involved: b4ld.c
  C code with the bug:

        (*(here->BSIM4SPbpPtr) -= gjbs + gstotb + Gmbs - gcsbb - gbspb
                                - sxpart * ggtb - T1 * dsxpart_dVb) + gIstotb;

  Proposed bug fix:

        (*(here->BSIM4SPbpPtr) -= gjbs + gstotb + Gmbs - gcsbb - gbspb
                                - sxpart * ggtb - T1 * dsxpart_dVb + gIstotb);


Bug 3:
------
  Bug reporters: Keith Green, Paul Ehnis, Brian Mounce, William Liu, Britt Brooks,
                 and Tom Vrotsos
  Files involved: b4ld.c
  Bug description: Thermal noise current spike when tnoiMod=0.
  
  Proposed bug fix: Long-channel Vdsat used to eliminate the spike.



Bug 4:
------
  Bug reporters: Keith Green, William Liu, Paul Ehnis, Brian Mounce, Britt Brooks,
                 and Tom Vrotsos
  Files involved: b4check.c
  Bug description: The maximum number of device fingers (NF) are limited to 500.
 
  Proposed bug fix: The limit is removed and if NF too large and makes Weff <= 0.0,
                 a fatal error will be issued.



CMC's Bug Reporting and Resolution Procedure:
---------------------------------------------
Date: Mon, 03 Apr 2000 09:03:33 -0500
From: Keith Green <kgreen@msp.sc.ti.com>
To: liuwd@bert.EECS.Berkeley.EDU
Subject: CMC's Bug Reporting Procedure for BSIM3/4

CMC Members,

In case any bugs are found in BSIM4.0.0 here is the CMC's bug reporting
and resolution procedure:

1. User reports bug to simulator vendor.
2. Spice provider reports bug to Berkeley with recommended fix, test
   case and significance.
3. Berkeley will immediately post on the website with the recommended fix.
4. Berkeley will notify CMC, BSIM3/4 mailing list and FSA
5. CMC members review bug and proposed fixes
6. At the next CMC meeting the CMC will decide on what action to take on
   each bug. A revision number (e.g. v3.2.1) will be assigned to the code
   with the accepted bug fixes.
7. Berkeley will post the list of approved bug fixes on the website along
   with the revision number assigned. Where appropriate this may include
   sections of revised code but Berkeley will not post a complete new
   release of the code for each minor version. For example v3.2.1 might be
   specified as equivalent to v3.2 with the bug fixes posted on a particular
   Web page.

Best Regards,
Keith