Time: Tuesday, January 26, 2021 at Noon US Pacific Time
=====
---------------------------------------------------------------------
---------------------------------------------------------------------
Join Microsoft Teams
Meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZjAwNDViYzctMTlkNy00NjE4LTgyMjctMzVhYjVlM2E0MGRk%40thread.v2/0?context=%7b%22Tid%22%3a%22fcbfc6fa-e20b-4a1d-b629-1b8e17697dbc%22%2c%22Oid%22%3a%227735c7ad-2577-4290-9e27-bce52c296030%22%7d>
+1 267-768-8015<tel:+1%20267-768-8015,,379363787> United States, Philadelphia
(Toll)
Conference ID: 379 363 787#
Local
numbers<https://dialin.teams.microsoft.com/d1ae197a-e3fc-4c53-90b6-39fdeba65bc1?id=379363787>
| Learn more about
Teams<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FJoinTeamsMeeting&data=02%7C01%7Crrwolff%40micron.com%7C76bf342695a241afa49b08d8664f0014%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0%7C637371836775527369&sdata=8V%2BqNyUEJCn4cdcg2sKkrsHv6fVFKr5pG8WV7z4sdxw%3D&reserved=0>
| Meeting
options<https://teams.microsoft.com/meetingOptions/?organizerId=7735c7ad-2577-4290-9e27-bce52c296030&tenantId=fcbfc6fa-e20b-4a1d-b629-1b8e17697dbc&threadId=19_meeting_ZjAwNDViYzctMTlkNy00NjE4LTgyMjctMzVhYjVlM2E0MGRk@thread.v2&messageId=0&language=en-US>
Join with a video conferencing device
106010980@xxxxxxxxxxxx<mailto:106010980@xxxxxxxxxxxx> VTC Conference ID:
1123888539
Alternate VTC dialing
instructions<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.bluejeans.com%2Fknowledge%2Fvtc-dial-in-options-for-teams&data=02%7C01%7Crrwolff%40micron.com%7C76bf342695a241afa49b08d8664f0014%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0%7C637371836775527369&sdata=4TYYlPRC4LhCRmxsk19DhP%2B6L2g19sOrX0m3Y42gV1I%3D&reserved=0>
---------------------------------------------------------------------
---------------------------------------------------------------------
Agenda
======
1) Opens
2) Roll call
3) Review of ARs:
Fangyi: Email his "AMI Redriver Flow" presentation to the ATM list
- done
Arpad: Ask Steve Parker to post the presentation to the ATM archives
- done (Fangyi did that in his email)
Curtis: Start an email thread about whether the BIRD204 modifications
can be handled in Editorial
- done
Any other AR-s?
4) Call for any IBIS related patent disclosures
5) Approval of minutes
6) Redriver flow issues
- Straw poll on Fangyi's proposal
- Decide who will be writing the BIRD
a) Intel's Redriver Flow presentation (Intel)
b) 166.4 Resolving problems with Redriver Init Flow (Walter)
c) BIRD190 (Ambrish)
d) 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)
7) Potential issues with BIRD204 (Walter)
- decide whether using the word "shall" requires a BIRD
Original words in BIRD204:
For "Times" and "Wave" options, if the Clock does not have a DLL or has a DLL
without an AMI_GetWave, then the EDA tool should effectively insert a
passthrough Clock AMI_GetWave function to create the wave or clock_times output
vector required by the Data AMI_GetWave clock_times input.
Proposal 1 (using shall):
For the "Wave" option, if the Clock does not have a DLL or has a DLL without an
AMI_GetWave, then the EDA tool should effectively insert a passthrough Clock
AMI_GetWave function to make the clock waveform available for the Data
AMI_GetWave clock_times input. For the "Times" option, the Clock shall have a
DLL with an AMI_GetWave that returns clock_times.
Proposal 2 (without shall):
"For the "Times" option, it is highly advisable to provide an AMI_GetWave
function in the Clock executable model that returns clock_times because the EDA
tool may not have the same information and/or algorithms that the author of the
AMI model or the manufacturer of the actual device has, potentially making the
clock times generated by the EDA tool different or less accurate. In addition,
the information whether the Clock executable model returns clock times or not
is not available to the EDA tool until the simulation is well under way or
finished, which poses additional complications during the simulations when the
Clock executable model does not return clock times."
8) Clarification for DC_Offset (Hansel)
- update?
9) GDDR6x signaling update (Randy)
- update?
10) Supporting PI modeling/simulation in IBIS (Zhiping)
- update?
11) Motion to adjourn?
Topic bin list:
===============
- Parameter directionality summary (Mike M.)
- Removing the single-ended input threshold requirements for
differential buffers (Mike M.?)
- Removing the single-ended characterization load requirements for
differential buffers (Mike M.?)
- Fix all the referencing problems in the current specification
(after Randy's C_comp proposal and BIRD189 are done)
(BIRD181.1 Bob, Mike L.)
- 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?
(important topic - 2018 ASIA IBIS Summit presentations)
(the spec. may not need to be changed for this)
- Digital signing of DLL/SO files. Should it be mentioned in the
spec, or required?
Tabled ARs:
===========
Tabled topics:
==============
12) Support for RDL in IBIS (Walter)
13) Jitter HF/LF components and Jitter Amplification (Mike M.)
14) Other DDR5 related topics
- rise fall asymmetry
15) 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
16) How to handle missing min/max data? (Arpad)
- what should be the governing rule for synchronizing
typ/min/max data?
Pending BIRDs awaiting discussion:
==================================
166.4 Resolving problems with Redriver Init Flow
190 Clarification for Redriver Flow
TBD New proposal for Redriver Flow (may replace BIRD166)
Thanks,
Arpad
=====================================================================
