******************************************************************************
********************* IBIS GOLDEN PARSER BUG REPORT FORM *********************
******************************************************************************

INSTRUCTIONS

To report a bug in the IBIS golden parser.  Please fill out the top part
of the following form and send the complete form to ibischk-bug@vhdl.org.

A list of reported bugs will be maintained on vhdl.org.

******************************************************************************

PARSER VERSION NUMBER:
      Found in IBISCHK3 V3.2.9  (Rechecked with IBISCHK V4.1)

PLATFORM (SPARC, HP700, PC, etc.):
      Checked on SPARC

OS AND VERSION:
      Solaris

REPORTED BY:
 Bob Haller SiSoft, and IBIS Quality Committee Members
 Eckhard Lenski Siemens, Mike LaBonte Cisco 
 Bob Ross Teraspeed, Kim Helliwell

DATE:
      2 Aug 2005 original report

DESCRIPTION OF BUG:

  If an ibis file has a Vmeas outside Vih/Vil no warning is issued. 
In most cases this is representative of a flawed IBIS File.

We recognize that we are comparing output parameters to input parameters. 
This may be considered unusual, but is legitimate for an I/O.  This 
parser check only applies to I/O's. 

      The IBIS parser is missing checks that could uncover a flawed IBIS file.
The IBIS Quality Committee proposes that a new Parser warning message be 
created. The "Caution" would be created to add a class of checks to 
significantly enhance the present IBIS Parsers capability. The new checks would 
be enabled with a command line switch to minimize additional spurious warnings for 
traditional IBIS model users, but will aid the model creator, reviewer and 
advanced users with enhanced automatic IBIS parser checking capability.

One reason why the Vinl and Vinh enclose Vmeas check is a caution is because 
there are legitimate cases, but predominently its a mistake if this is done.


4.2.3  {LEVEL 1}  [Model] Vinl and Vinh enclose Vmeas

  For I/O buffers Vinl and Vinh values should be below and above,
  respectively, Vmeas. Exceptions to this should be explained in a
  comment. It's uncommon.

  +++ IBISCHK NOTES +++++++++++++++++++++++++++++++++++++++++++++++++++++
  Proposal: ibischk caution message if Vmeas not between Vinh or Vinl
    in I/O models.
  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


INSERT IBIS FILE DEMONSTRATING THE BUG:

     The attached test case summarizes one of the new requirements called 
out in the IBIS Quality specification that are not adaquately checked by 
the 4.1 IBIS parser. The Attached IBIS file should be used to test 
parser conformance to this new requirement. This IQ committee believes that 
this check is representative of the new category Caution.

[IBIS Ver]    4.1
[File Name]   iq_caution_bug.ibs
[File Rev]    1.0
[Date]        8/02/2005
[Notes]       IBIS Model for IQ caution bug
|
[Component] test
[Manufacturer] SiSoft
[Package]
R_pkg 284m   NA      NA
L_pkg 7.89nH NA      NA
C_pkg 1.35pF NA      NA
[Pin]   signal_name      model_name        R_pin L_pin C_pin
|Ball   Pad Name         CellName
1      IQ_bug    DATA         NA NA NA
|
| BUG
| Vmeas is above Vinh in this model. Although it is possible that
| such a test ficture could be intended, that is unlikely enough
| to warrant cautioning the model maker. IBISCHK4 V4.1.1 ignores
| this anomoly.
|
[Model]     DATA
Model_type  I/O
Vmeas = 1.65V
Vinh = 1.6V
Vinl = 0.9V
C_comp 2.1454p 2.0873p 2.2382p
[Voltage Range] 2.5 2.25 2.75
[Pulldown]
-2.5                -.0012              -700.01e-6          -.0016
4.95                .1248               .1512               .1069
[Pullup]
-2.45               .0016               900.e-6             .0037
5.                  -.1285              -.1313              -.109
[Ramp]
dV/dt_r .9201/203.57p .6785/334.7p 1.0863/153.65p
dV/dt_f .9507/110.26p .7187/186.76p 1.0916/92.507p
[END]

******************************************************************************
******************** BELOW FOR ADMINISTRATION AND TRACKING *******************
******************************************************************************

BUG NUMBER: 

SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT]  (ENHANCEMENT)

PRIORITY: [HIGH, MEDIUM, LOW]                               LOW

STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG]             (OPEN)

FIXED VERSION:

FIXED DATE:

NOTES ON BUG FIX: 

 
******************************************************************************
******************************************************************************