=============================================================================== IBIS INTERCONNECT TASK GROUP Mailing list: ibis-interconnect@freelists.org ================================================================================ Attendees from August 28, 2024 Meeting (* means attended at least using audio) ANSYS Curtis Clark, Juliano Mologni Broadcom James Church Intel Corp. Michael Mirmak* [Michael Brownell] Xiaoning Ye Keysight Technologies Ming Yan Marvell Steve Parker MathWorks Walter Katz* Micron Technology Justin Butterfield Siemens EDA Weston Beal, Arpad Muranyi*, Randy Wolff ST Microelectronics Aurora Sanna Synopsys Ted Mido, Edna Moreno University of Illinois Jose Schutt-Aine Zuken USA Lance Wang* Michael Mirmak called the meeting to order. No patents were declared. During review of the minutes, Arpad Muranyi moved to approve the minutes. Lance Wang seconded the motion. The minutes were approved without objection. During the AR review, Arpad noted that his AR from the last meeting was still open. He asked about meeting recordings and the timeline for keeping the recordings. Michael replied that one could establish a retention policy. The ultimate goal is not to keep the recordings at all, but to use the transcribed recordings to enable AI to produce summaries and minutes. Michael reviewed the port mapping draft, focusing on port/diff_port corrections from the last meeting. While the example was corrected, there was some discussion of "Net" and its meaning. Extended net, according to Walter Katz, has a series device between two separate nets (with different names). On case sensitivity: Arpad noted that keywords are insensitive but parameters are sensitive in IBIS. Michael took the AR to find out about case sensitivity in Touchstone. Michael noted that the team needs to sort out "subparameter" vs. "parameter" definitions in the text. Arpad added that the difference between "Side" and "Left_side", etc. is unclear. Walter suggested that one could change the text to Left_symbol, etc. IEEE 370 uses a table of Left Side and Right Side for cable/connector identifiers, matrix-style. This is similar to NNFF terminology, for instance. Michael added that Side is a grouping mechanism for topology descriptions, not schematics. Michael asked about S and P being missing. Example 3 is closest to using all features. Walter stated that GNDs are automatically rails. Example 5 is in error: VDD should use Type P. Arpad asked about Vtt with terminations: how are these to be interpreted? Walter stated that they should be identified as P. Michael asked whether both sides of a Vtt-connected resistor are P. Arpad replied that one side is P, and one side is S. The team discussed which parameters are required for Ports, including Net. Michael asked whether at least two ports should be required to be associated with each net. Arpad asked whether one can have a dead-end net. Michael noted that Diff_port is the only exception. Arpad asked whether, if Logical is not present, whether nothing would show up in an associated schematic. Michael confirmed this would be true. Walter suggested one could also use Physical, but also use Side:Net. Arpad added that he was concerned about "Logical" identifiers really being Symbol_label, Schematic_label, or something similar. He added that we had two usage cases for these labels: one was labeling for connectivity to the outside world (functional). The other is just for label/naming purposes. Connectivity relates to only the functional side. Arpad accepted an AR to provide revised label suggestions. [AR] In the next meeting, the team will review the use of references in Example 3, plus Group numbering. Arpad moved to adjourn the meeting. Lance seconded. The meeting adjourned without objection. The next meeting will be held September 3, 2024. ================================================================================ Bin List: 1) Complete port naming proposal (Katz et al) 2) Complete/revise Touchstone 3.0 draft outline (Mirmak) 3) Complete ISS-IRD 1 Draft - enable cascading of S-parameters through W-element (Mirmak) - TABLED Tabled ARs: - Arpad to give an example of the physical connectivity needed for EMD automation.