****************************************************************************** ********************* 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 info@ibis.org. A list of reported bugs is maintained at http://ibis.org/bugs/ibischk/ . ****************************************************************************** PARSER VERSION NUMBER: 7.2.0 PLATFORM (SPARC, HP700, PC, etc.): PC OS AND VERSION: Windows 10 REPORTED BY: Randy Wolff, Arpad Muranyi; Siemens EDA DATE: June 14, 2023 DESCRIPTION OF BUG: False IBIS Ver Compatibility Error for EMD and IBIS File Checking For IBISCHK720, the parser is enforcing a rule based on BUG228; however, the IBIS 7.2 specification does not state the IBIS files referenced by EMD must have [IBIS Ver] set to 7.0 or higher. The parser should relax this rule to be compliant with the specification. Other Error reporting behavior of BUG228 also needs to be changed and is shown below. The following message is reported for an IBIS file referenced by an EMD file with the IBIS file [IBIS Ver] less than 7.0: E5810 - The file bug244.ibs has [IBIS Ver] <3.2>; however, IBIS 7.0 compatibility is required for IBIS files referenced by EMD Note, if [IBIS Ver] is changed to 7.0, no Error is reported. This indicates that the files are compatible. ********************** Existing BUG228 behavior shown below: >ibischk7_64.exe -numbered bug228.ibs IBISCHK7 V7.2.0 Checking bug228.ibs for IBIS 7.0 Compatibility... E0730 - Component 'BUG228': Pins '1' and '2' with model 'GND' have the same 'Pulldown_ref' 'VSS' but different signal_names 'VSS' and 'VSSQ' E5808 - Component BUG228: signal_name VSSQ (associated with Pin 2, Pulldown_ref VSS) conflicts with signal_name VSS also associated with bus_label VSS Errors : 2 File Failed **** Here is the EMD file parser output: >ibischk7_64.exe -numbered -emd bug228file.emd IBISCHK7 V7.2.0 Checking bug228file.emd for IBIS 7.1 Compatibility... Checking bug228.ibs for IBIS 7.0 Compatibility... E0730 - Component 'BUG228': Pins '1' and '2' with model 'GND' have the same 'Pulldown_ref' 'VSS' but different signal_names 'VSS' and 'VSSQ' E5808 - Component BUG228: signal_name VSSQ (associated with Pin 2, Pulldown_ref VSS) conflicts with signal_name VSS also associated with bus_label VSS Errors : 2 File Failed Errors : 2 File Failed **** With bug228.ibs file edited to have [IBIS Ver] of 3.2 instead of 7.0, the output of the parser is this: >ibischk7_64.exe -numbered bug228.ibs IBISCHK7 V7.2.0 Checking bug228.ibs for IBIS 3.2 Compatibility... Errors : 0 File Passed **** Finally, the parser output on the EMD file referencing this modified 3.2 Version IBIS file: >ibischk7_64.exe -numbered -emd bug228file.emd IBISCHK7 V7.2.0 Checking bug228file.emd for IBIS 7.1 Compatibility... Checking bug228.ibs for IBIS 3.2 Compatibility... E5810 - The file bug228.ibs has [IBIS Ver] <3.2>; however, IBIS 7.0 compatibility is required for IBIS files referenced by EMD E5808 - Component BUG228: signal_name VSSQ (associated with Pin 2, Pulldown_ref VSS) conflicts with signal_name VSS also associated with bus_label VSS Errors : 2 File Failed Errors : 2 File Failed ********************** The suggested fix is to change the default parser behavior when checking EMD files to the following: 1. Check each referenced IBIS file for IBIS 7.0 compatilibity of BIRD184.2 rules. 2. If errors E0730 and/or E5808 are not found, then E5810 is not triggered (no Errors). 3. If errors E0730 and/or E5808 are found, output these errors along with E5810. Note in step 3 that E0730 is never currently displayed and needs to be if it occurs. The E5810 message should also be modified. Since E5810 should only be triggered by E5808 and/or E0730, it can continue to be displayed before these Errors but should better explain why E5810 and/or E0730 are being displayed. Suggested new text is: “E5810 - The file XYZ.ibs has [IBIS Ver] <#.#>; however, IBIS files referenced by EMD require compatibility with IBIS 7.0 Pin Mapping and bus_label rules. Checking for IBIS 7.0 compatibility results in the following error(s):” **** INSERT IBIS FILE DEMONSTRATING THE BUG: ********** bug244.emd ********** [IBIS Ver] 7.2 [File Name] bug244.emd [File Rev] 0.0 [Date] 1 June 2023 | [Begin EMD] E1 [Manufacturer] None | [Number of EMD Pins] 3 [EMD Pin List] signal_name signal_type bus_label 1 Input 2 VDD POWER 3 VSS GND [End EMD Pin List] [EMD Parts] P7 bug244.ibs DDR4_8Gb_x8 [End EMD Parts] [EMD Designator List] U6 P7 [End EMD Designator List] [Designator Pin List] signal_name signal_type bus_label U6.K9 VDD POWER U6.M8 VSS GND U6.N9 Input [End Designator Pin List] [EMD Group] G1 S1 NA [End EMD Group] [End EMD] [EMD Set] S1 [EMD Model] M1 File_TS test.s2p Number_of_terminals = 3 1 Pin_I/O pin_name 1 2 Pin_I/O pin_name U6.N9 3 A_gnd [End EMD Model] [End EMD Set] | [End] ********** bug244.ibs ********** [IBIS Ver] 3.2 | [IBIS Ver] 7.0 | This IBIS Ver produces 0 Error (File is compatible) [File Name] bug244.ibs [File Rev] 1.0 [Date] June 5, 2023 | |****************************************************************************** | [Component] DDR4_8Gb_x8 [Manufacturer] Test [Package] |Variable Typ Min Max R_pkg 0 0 0 L_pkg 8n 5n 10n C_pkg 5p 4p 7p | [Pin] signal_name model_name R_pin L_pin C_pin K9 VDD POWER 0.0 8n 5p M8 VSS GND 0.0 8n 5p N9 INPUT1 Bug244_IN 0.0 8n 5p | [Pin Mapping] pulldown_ref pullup_ref gnd_clamp_ref power_clamp_ref ext_ref K9 NC VDD M8 VSS NC N9 NC NC VSS VDD | [Model] Bug244_IN Model_type Input Vinh = 2.0 Vinl = 0.8 C_comp 0.1p 0.1p 0.1p | typ min max [Voltage Range] 3.3 3.0 3.6 | [End] ************************************************************ test.s2p (More complete file than in Version 7.1.1 QA suite) ************************************************************ !2-port network, S-parameter !Default MA format, GHz frequencies, 50 ohm reference, S-parameters [Version] 2.0 # [Number of Ports] 2 [Two-Port Data Order] 12_21 [Number of Frequencies] 2 [Network Data] 0.0 1.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 1.0 1.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 [End] ****************************************************************************** ******************** BELOW FOR ADMINISTRATION AND TRACKING ******************* ****************************************************************************** BUG NUMBER: 244 SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT] MODERATE PRIORITY: [HIGH, MEDIUM, LOW] MEDIUM STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG] CLOSED FIXED VERSION: 7.2.1 FIXED DATE: December 8, 2023 NOTES ON BUG FIX: Classified at the June 23, 2023 IBIS Open Forum Meeting To be fixed in the next release A simple clarification BIRD should be issued that states a requirement. ****************************************************************************** ******************************************************************************