All,
I agree, A_gnd should be a Terminal_type and added to the Allowed
Terminal_type Associations table and follow the same rules as in the
Interconnect Modeling syntax:
3 A_gnd
Bob
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Wednesday, October 23, 2019 5:55 PM
To: IBIS-Interconnect
Subject: [ibis-interconn] Re: New EMD Example
Randy,
Thanks for the new example. I agree that A_gnd should be a terminal_type.
I think it may have started as a qualifier because if we have signal names
or
bus label names we have more options that need to be defined. But A_gnd
is just A_gnd, so none of that extra baggage is needed for it.
Thanks,
Arpad
===========================================================
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Randy Wolff
Sent: Wednesday, October 23, 2019 5:38 PM
To: IBIS-Interconnect <ibis-interconn@xxxxxxxxxxxxx>
Subject: [ibis-interconn] New EMD Example
The updated example fixes some syntax after our latest discussions:
1. Uncoupled models now use A_gnd as a reference:
[EMD Model] UDQ0
File_IBIS-ISS z11bx16_2cob_ddp_iss_files/z11bx16_2cob_ddp_UDQ0.iss UDQ0
Number_of_terminals = 3
1 Pin_I/O pin_name A3
2 Pin_I/O pin_name U1.51
3 Pin_Rail A_gnd
[End EMD Model]
This highlights a difference in syntax between EMD and BIRD189. In BIRD189,
A_gnd is scoped as a terminal_type. In EMD, A_gnd is scoped as a
terminal_type_qualifier. I'm not sure why this is, and I propose A_gnd be
scoped as a terminal_type:
3 A_gnd
2. Bus_label syntax used in Terminal lines. Some could alternatively
use signal_name qualifier.
85 Pin_Rail bus_label U0.VDD
86 Pin_Rail bus_label U1.VDD
87 Pin_Rail bus_label U0.VDDDLL
88 Pin_Rail bus_label U1.VDDDLL
89 Pin_Rail bus_label U0.VDDQ
90 Pin_Rail bus_label U1.VDDQ
91 Pin_Rail bus_label U0.VPP-B1
92 Pin_Rail bus_label U1.VPP-B1
93 Pin_Rail bus_label U0.VPP-R9
94 Pin_Rail bus_label U1.VPP-R9
95 Pin_Rail bus_label U0.VREFCA
96 Pin_Rail bus_label U1.VREFCA
97 Pin_Rail bus_label U0.VSS
98 Pin_Rail bus_label U1.VSS
155 Pin_Rail bus_label VDD
156 Pin_Rail bus_label VDDDLL
157 Pin_Rail bus_label VDDQ
158 Pin_Rail bus_label VPP-B1
159 Pin_Rail bus_label VPP-R9
160 Pin_Rail bus_label VREFCA
161 Pin_Rail bus_label VSS
3. Limited bus_labels defined in [EMD Pin List] and [Designator Pin
List]. This assumes support for bus_label to be the same as signal_name
when not defined.
4. Added [EMD Set] for on-die decoupling models. One [EMD Model]
included for each die (U0 and U1) within the same Set. This is a choice to
include the on-die decoupling in the EMD instead of adding it with BIRD189
syntax inside the .ibs file. Mostly done to provide example of syntax with
multiple EMD Sets within a EMD Group.
[EMD Group] MT40A1G16KNR_Full_Pkg_ISS
| EMD Set file_reference
MT40A1G16KNR_Full_Pkg_ISS NA
OnDie_Decoupling NA
[End EMD Group]
|***************************************************************************
| EMD Set for OnDie_Decoupling
|***************************************************************************
|
[EMD Set] OnDie_Decoupling
[Manufacturer] Micron Technology, Inc.
[Description] VDDQ-VSS On-Die Decoupling Models
|
[EMD Model] U0_z11b_ondie_decoupling_alldq
File_IBIS-ISS z11bx16_2cob_ddp_iss_files/z11b_ondie_decoupling_alldq.iss
z11b_ondie_decoupling_alldq
Number_of_terminals = 3
1 Pin_Rail signal_name U0.VDDQ
2 Pin_Rail signal_name U0.VSS
3 Pin_Rail A_gnd
[End EMD Model]
|
[EMD Model] U1_z11b_ondie_decoupling_alldq
File_IBIS-ISS z11bx16_2cob_ddp_iss_files/z11b_ondie_decoupling_alldq.iss
z11b_ondie_decoupling_alldq
Number_of_terminals = 3
1 Pin_Rail signal_name U1.VDDQ
2 Pin_Rail signal_name U1.VSS
3 Pin_Rail A_gnd
[End EMD Model]
|
[End EMD Set]
5. Subcircuit name added to all EMD Models in File_IBIS-ISS
subparameter. Missing in previous example.
Regards,
Randy
