Time: Tuesday, June 26, 2018 at Noon US Pacific Time
=====
WebEx:
======
https://sisoft.webex.com/sisoft/j.php?MTID=m1775c35b7d9a55735fbb2c67876222ba
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
---------------------------------------------------------------------
---------------------------------------------------------------------
Agenda
======
1) Opens
- Our next meeting would be on July 3. Should we cancel it?
2) Roll call
3) Review of ARs:
Mike L.: Update the IBIS 6.1 known issues list to include adding Value
entries to the PAM4 thresholds Usage Out example on pg. 235-236.
Mike M.: Submit his "Enabling [Rgnd] and [Rpower] for Input Model_type"
v2 to the Open Forum as a BIRD (done - BIRD195).
Arpad: Send an email to the Open Forum noting that the ATM had voted to
submit BIRD195
Any other AR-s?
4) Call for any IBIS related patent disclosures
5) Approval of minutes
6) Complex C_comp modeling (Randy)
- discussion?
7) Motion to adjourn?
Topic bin list:
===============
- Updating the input thresholds/measurement target information in
IBIS to include an eye diagram specification in the IBIS file
(including BER)
- Removing the single-ended input threshold requirements for
differential buffers
- Removing the single-ended characterization load requirements for
differential buffers
- Guidance for power-aware vs. AMI models - do we have rules for
how a power-aware (and therefore potentially non-LTI) buffer
analog data set should be used with IBIS-AMI algorithmic data?
- Fix all the referencing problems in the current specification
(after Randy's C_comp proposal and BIRD189 are done)
- IBIS-AMI Post Simulation Processing (FEC) (Mike L.)
Tabled topics:
==============
8) 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)
9) 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) 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)
13) 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.6 Interconnect Modeling Using IBIS-ISS and Touchstone
Pending BIRDs awaiting discussion:
==================================
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
=====================================================================
