Randy,
Agree with deleting the highlighted portion. It is a subset of the general
comment rule that comments can be inserted anywhere on a line that follows
any permitted syntax content.
Also, I am suggesting that all I/O pin_names be listed in the [Designator
Pin List] and require signal_name entries.
For certain features, the signal_name entries on the EMD .emd file need to
be the same for possible connectivity alignment (particularly if
Aggressor_Only is used). That means that an attached .ibs file can have a
different signal_name, but the .emd file must reassign it.
We still will support pin_name <emd_pin_name> to pin_name
<Uxx.different_pin_name> connections, but need to navigate both the [EMD Pin
List] and [Designator Pin List] tables for identical signal_names to deduce
primary connections.
(I do not think we should bring in a new qualifier: Pin_I/O signal_name
<entry> into the syntax, but that is an option.)
Bob
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Randy Wolff
(Redacted sender "rrwolff" for DMARC)
Sent: Tuesday, October 1, 2019 7:59 AM
To: Walter Katz; IBIS-Interconnect
Subject: [ibis-interconn] Re: [EXT] EMD Draft 21
Hi Walter,
I'm working on my stacked-die example using the EMD syntax. Here's some
feedback I have so far as I've been reading through Draft 21.
Given that we have this rule:
Only one [Begin EMD]/[End EMD] keyword pair is allowed in a .emd file.
I don't think the highlighted text is necessary:
Keyword: [End EMD]
Required: Yes
Description: Marks the end of a module.
Usage Rules: This keyword must come at the end of each complete module
description.
Optionally, A comment may be added after the [End EMD] keyword to clarify
which module model has ended.
Example:
[End EMD] | End: 16Meg X 8 SIMM Module
Also, I think that the Example on pages 25-26 can be modified to include the
[Designator Pin List] section instead of the commented [Component] pin list.
Replace:
| The following will not exist, but is used to explain the examples below
| [Component Pin List] signal_name signal_type
| U1.1 VDD POWER VDD1
| U1.2 VDD POWER VDD2
| U1.3 VSS GND
| U1.4 VSS GND
| U2.1 VDD POWER VDD1
| U2.2 VDD POWER VDD1
| U2.3 VSS GND
| U2.4 VSS GND
With:
[Designator Pin List] signal_name signal_type bus_label
U1.1 VDD POWER VDD1
U1.2 VDD POWER VDD2
U1.3 VSS GND
U1.4 VSS GND
U2.1 VDD POWER VDD1
U2.2 VDD POWER VDD1
U2.3 VSS GND
U2.4 VSS GND
With this change, I think it's necessary to expand the [Designator Pin List]
to include the signal pins on U1 and U2, for at least DQ1 that has the [EMD
Model].
Thanks,
Randy
From: ibis-interconn-bounce@xxxxxxxxxxxxx
<ibis-interconn-bounce@xxxxxxxxxxxxx> On Behalf Of Walter Katz
Sent: Wednesday, September 25, 2019 10:06 AM
To: IBIS-Interconnect <ibis-interconn@xxxxxxxxxxxxx>
Subject: [EXT] [ibis-interconn] EMD Draft 21
EMD Draft 21
Walter Katz
<mailto:wkatz@xxxxxxxxxx> wkatz@xxxxxxxxxx
Office 978.461-0449 x 133
Mobile 720.417-3762