Hi All,
For today's discussion:
The addition of File_Ts0 to BIRD 189 is fundamentally flawed in the current
draft of BIRD 189.x. It follows the IBIS-ISS concept of exactly n nodes
specified for the S-element where the data is defined for an n-port. These n
ports are then defined as between each of the n nodes and the node 0. This is
equivalent to an S-element where n+1 nodes are specified and the user connects
the n+1st node to node 0.
The problem in the current draft is that the node 0 does not have to be present
among the entire set of interconnect model terminals. If the node 0, to which
the S-element is effectively connected, is not required to be included in the
interconnect model terminals then the only correct and unambiguous use of
File_Ts0 is that the data contained in the Touchstone file must be such that:
If the same Touchstone file is used for an S-element with n+1 nodes than for
any loading conditions (the external circuitry outside of that S-element) and
at all frequencies present in the file the current entering (or leaving) the
N+1st node is zero.
Radek
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] ;
On Behalf Of Muranyi, Arpad
Sent: Tuesday, November 7, 2017 9:07 AM
To: ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] IBIS-ATM teleconference - Agenda for November 7, 2017
Time: Tuesday, November 7, 2017 at Noon US Pacific Time
=====
WebEx:
======
https://sisoft.webex.com/sisoft/j.php?MTID=m1775c35b7d9a55735fbb2c67876222ba<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsisoft.webex.com%2Fsisoft%2Fj.php%3FMTID%3Dm1775c35b7d9a55735fbb2c67876222ba&data=02%7C01%7C%7C72a226e0f6b44616204408d526020958%7C63545f2732324d74a44dcdd457063402%7C1%7C0%7C636456712555122100&sdata=lhviqMZHPOwk%2BIaNhr73V5v1Lc7S6mnNRFyKkjw6lwQ%3D&reserved=0>
Meeting Number: 735 161 627
Meeting Password: IBIS
Audio:
======
Voice dial-in: (800) 637-5822
International: +1 (647) 723-3937 <--- (For Canada)
0114501530 <--- (For Sweden)
0201400572 <--- (For Sweden Toll Free)
069509594672 <--- (For Germany)
08001014542 <--- (For Germany Toll free)
Access Code: 685-0440
Mentor Global Crossing Teleconference commands for audio:
http://www.globalcrossing.com/customer/collaboration/cust_ready_access_tips.aspx<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.globalcrossing.com%2Fcustomer%2Fcollaboration%2Fcust_ready_access_tips.aspx&data=02%7C01%7C%7C72a226e0f6b44616204408d526020958%7C63545f2732324d74a44dcdd457063402%7C1%7C0%7C636456712555122100&sdata=3vyGZmWNlaWmB4I2gbreNpKNaAmZOJK%2BTNoG4I%2B76c0%3D&reserved=0>
---------------------------------------------------------------------
---------------------------------------------------------------------
Agenda
======
1) Opens
2) Roll call
3) Review of ARs:
Bob and Radek:
Produce a new draft of BIRD189.5 containing the two-column format
for Unused_port_terminations.
- done
Any other AR-s?
4) Call for any IBIS related patent disclosures
5) Approval of minutes
6) File_TS0 restrictions (Radek)
- discussion
7) BIRD165.1_draft1 Parameter Passing Improvements for
[External Circuit]s (Arpad)
- discussion
8) Buffer impedance / C_comp improvements (Randy)
- discussion
9) Single ended applications of algorithmic modeling (All)
- do we need to make any changes in the spec?
- we need Fangyi's presence to discuss his concerns
- discussion
a) single ended filter needs different algorithms
- EQ effecting Vref
b) rise/fall may be asymmetric
- gets worse at higher data rate
c) loss of information when using difference signals only
d) power aware simulation (SSO effects)
Tabled topics:
==============
10) New BIRDs from Editorial Task Group? (Bob/Radek)
a. Specify buffer reference terminals for pins ([Pin Reference])
b. Simulation (aka DIA) vs. DUT (depends on #a)
c. C_comp and package reference in simulation clarifications
(depends on #a)
d. Make changes to the [Receiver Threshold], once a. and b. are resolved
10) 166.4 Resolving problems with Redriver Init Flow (Walter)
11) BIRD190 (Ambrish)
12) BIRD161.2 Supporting Incomplete and Buffer-only
[Component] Descriptions (Mike M.)
13) Fangyi's Redriver flow BIRD draft (Fangyi)
- add equations
- consider rewriting the AMI "front end" in the spec (flows)
(when this proposal is added to the spec)
14) How to handle missing min/max data? (Arpad)
- what should be the governing rule for synchronizing
typ/min/max data?
Pending BIRDs, expected to be rejected:
=======================================
125.1 Make IBIS-ISS Available for IBIS Package Modeling
145.3 Cascading IBIS I/O buffers with [External Circuit]s using the [Model
Call] keyword
163 Instantiating and Connecting [External Circuit] Package Models with
[Circuit Call]
164 Allowing Package Models to be defined in [External Circuit]
Pending BIRDs, expected to be accepted (currently in discussion):
=================================================================
189.5 Interconnect Modeling Using IBIS-ISS and Touchstone
Pending BIRDs awaiting discussion:
==================================
165 Parameter Passing Improvements for [External Circuit]s
166.4 Resolving problems with Redriver Init Flow
181.1 I/V Table Clarifications
190 Clarification for Redriver Flow
TBD New proposal for Redriver Flow (may replace BIRD166)
TBD C_comp modeling with IBIS-ISS
Thanks,
Arpad
=====================================================================
