Time: Tuesday, January 4, 2022 at Noon US Pacific Time
=====
---------------------------------------------------------------------
---------------------------------------------------------------------
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the
meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_NDRhOWE3MDctMTllNi00MDc3LTk3NmEtNTJiNWM5ZTAyNWM3%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>
Join with a video conferencing device
106010980@xxxxxxxxxxxx<mailto:106010980@xxxxxxxxxxxx>
Video Conference ID: 117 144 478 7
Alternate VTC dialing
instructions<https://support.bluejeans.com/knowledge/vtc-dial-in-options-for-teams>
Or call in (audio only)
+1 267-768-8015,,144959995#<tel:+12677688015,,144959995#> United States,
Philadelphia
Phone Conference ID: 144 959 995#
Find a local
number<https://dialin.teams.microsoft.com/d1ae197a-e3fc-4c53-90b6-39fdeba65bc1?id=144959995>
| Reset PIN<https://mysettings.lync.com/pstnconferencing>
Learn More<https://aka.ms/JoinTeamsMeeting> | Meeting
options<https://teams.microsoft.com/meetingOptions/?organizerId=7735c7ad-2577-4290-9e27-bce52c296030&tenantId=fcbfc6fa-e20b-4a1d-b629-1b8e17697dbc&threadId=19_meeting_NDRhOWE3MDctMTllNi00MDc3LTk3NmEtNTJiNWM5ZTAyNWM3@thread.v2&messageId=0&language=en-US>
---------------------------------------------------------------------
---------------------------------------------------------------------
Happy New Year!
Agenda
======
1) Opens
2) Roll call
3) Review of ARs:
Any other AR-s?
4) Call for any IBIS related patent disclosures
5) Approval of minutes
6) Updates on any of the following topics:
- Power Supply Induced Jitter (PSIJ) study (Randy)
- GDDR6x signaling with IBIS-AMI (Walter)
- Supporting PI modeling/simulation in IBIS (Zhiping)
7) List of potential new topics mentioned in previous meetings:
- AMI file root name checking
- Update outstanding BIRDs with new IBIS v7.1 page numbers
8) Address issues listed in Known Issues document:
- “If present under File_IBIS-ISS, Terminal_type A_gnd may be
used any number of times on any of the terminal lines.”
(pg. 339 & 379)
- The [Pin] keyword does not include the “alphanumeric”
restriction, which should be added for consistency with other
keywords
- The EMD [Designator Pin List] keyword does not allow signal_type
to be ‘NC’ and it requires all pin_names from referenced IBIS
Components to be listed. We might want to add ‘NC’ and remove
this requirement.
9) New potential technical issue:
- AMI Rx models are not required to return clock times. In SerDes
simulations the EDA tool can apply its own CDR to the signal
relatively easily to generate clock times (although it is
questionable whether this CDR would behave the same way as the
CDR of the actual device). However, in the case of clocked Rx
AMI models, it doesn’t make sense to expect the EDA tool to
derive the clock times from the Rx AMI model’s output data
signal with a CDR (to build the eye diagram) if the Rx model
doesn’t return clock times. In addition, the clock input to
the data Rx AMI model may not be useful either for building the
eye diagram because the Rx data AMI model could potentially
modify those clock times internally. For these reasons it might
be better to make the clock times output required for (at least)
the clocked Rx AMI models (but maybe also for regular SerDes Rx
AMI models).
10) 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.?)
- 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:
==============
11) BIRD213.1 draft 6 (PAMn) (Walter)
12) Jitter HF/LF components and Jitter Amplification (Mike M.)
13) Other DDR5 related topics
- rise fall asymmetry
14) 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
e) Fix all the referencing problems in the current specification
(after Randy’s C_comp proposal and BIRD189 are done)
(BIRD181.1 Bob, Mike L.)
15) 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
Thanks,
Arpad
=====================================================================
