All,
Some more corrections have been made to only the examples
in pages 16-28, and some columns have been adjusted in a
more consistent manner.
This is still subject to more review.
Bob
-----Original Message-----
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Monday, June 20, 2016 12:50 PM
To: IBIS-Interconnect
Subject: [ibis-interconn] Draft 36 - Example Modifications and [Interconnect
Model Sets] Inclusion
All
I worked only on the Examples pp. 16-28.
I added complete [Interconnect Model Sets] for each set,
By definition, they must include one or more IO paths and
optionally a PDN path. Where needed I added both the
GND and POWER paths for completeness.
I introduced a naming convention on page 16 for [Interconnect Model Sets]
so that the user would understand the choices. We can work on this.
I removed pkg and die in the names since that is ambiguous. Instead I used
buf, pad, or pin as part of the convention where needed since that is what
is
used in the[Begin Interconnect Model] location.
For .sNp references, I added the N+1 reference node per the Spec.
If a Buf was declared, I used a Buf_PD_ref node. Otherwise, I used
the Pin signal_name for GND reference since a Buf rail terminal
may not be known for pad-pin connections.
I also started aligning the columns for readability.
This may required more discussion and work.
Bob
--
Bob Ross
Teraspeed Labs
http://www.teraspeedlabs.com
bob@xxxxxxxxxxxxxxxxx
Direct: 503-246-8048
Office: 971-279-5325
Attachment:
InterconnectBIRD_36_br2.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
