================================================================================ IBIS INTERCONNECT TASK GROUP Mailing list: ibis-interconnect@freelists.org ================================================================================ Attendees from July 26, 2023 Meeting (* means attended at least using audio) ANSYS Curtis Clark Broadcom James Church Intel Corp. Michael Mirmak Michael Brownell Keysight Technologies Ming Yan Marvell Steve Parker MathWorks Walter Katz* Micron Technology Justin Butterfield Siemens EDA Arpad Muranyi*, Randy Wolff* ST Microelectronics Aurora Sanna Teraspeed Labs Bob Ross* University of Illinois Jose Schutt-Aine Zuken USA Lance Wang* Randy Wolff called the meeting to order and took minutes. No patents were declared. During review of the July 12 minutes, Randy Wolff noted multiple misspellings (including "adeed", "comrpession", and "recircuate"); Lance moved to approve the minutes with spelling corrections. Bob seconded. No objections were raised. AR review: - Michael to check with Walter Katz regarding slides for his port-naming proposal [AR] - Done - Arpad to revise the pole-residue TSIRD draft and recirculate it [AR] - He was waiting for comments before continuing. Randy suggested he email the current draft to the task group list to remind people of the proposal. Arpad took the AR to send out the draft with a call for comments [AR]. Discussion on port naming proposals: Walter shared his presentation from the DesignCon 2022 IBIS Summit: https://urldefense.proofpoint.com/v2/url?u=https-3A__ibis.org_summits_apr22_katz.pdf&d=DwIGaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=pm-gpp52pBnLLUTWlv8SEP0jyzItZFJpEDfxBr1gqiprKaoui7fp-KMKM_HaRUFi&s=ImO_pe-_mkokUEuXjpQGbdfFZPiVvt449-u617gXEXY&e= Walter noted that he did not include near/far designations in his proposal. These terms get confused with crosstalk terms (NEXT/FEXT). Memories can have multiple ends for multiple die on the same bus. Walter is talking with customers to gather other information that may be needed for port naming. He said some information requested by Michael such as interconnect or active device designations could be useful. Walter thought adding physical measurement information or logical information is useful. He wanted to see port naming allow for swathing. Arpad noted he preferred to keep all information in the Touchstone file, agreeing with Walter. Arpad made a lot of EMD models lately, so his comments related to that experience. In an EMD file we need to know how the ports are connected in a specific way. If we want to know how the file should be connected, what is the usefulness of end naming such as A, B, C, etc.? Walter noted the physical name (Phy-name) would be useful for EMD. Pre-layout analysis makes use of logical names. The end designation is helpful for connectors to know the sides or locations on motherboards or daughter boards. Arpad noted the need for a generic/flexible and a general naming convention. A connector is an example of a flexible naming convention. Randy added that he thought the most useful reason for the "end" information was in generating a schematic symbol to group certain ports together. Walter stated that the "differential" information is useful for the EDA tool when generating information about the S-parameter such as analysis reports. Lance noted the "end" information seems to already be included in the physical name in one example. Is end redundant? Walter noted we may not want to support having both physical and logical names, and in this case the end information would not be seen in other names. Arpad shared his slides "Anatomy of the HL_Portmap Syntax". He showed that a naming convention without ground references makes it impossible to connect some package models to IBIS buffer models without the buffer grounds left floating. The HyperLynx naming convention adds designations for signal and ground and group naming and definitions for merged pins. A "connect" syntax describes extended nets. Walter noted most people are doing ground based simulation. The power port grouping could be useful, although he didn't object to having ground grouping. Arpad moved to adjourn. Randy seconded. The meeting adjourned. ================================================================================ Bin List: 1) [Complete draft Touchstone document separating version 1.0 and 2.0 into their own chapters] - REMOVED 2) Create structures to encapsulate Touchstone 1.0 data in Touchstone 2+ specifications - TABLED 3) Complete draft Touchstone 2.0 document containing TSIRD3 and TSIRD4 draft (Muranyi) – COMPLETED IN DRAFT 10 4) Complete pole-residue format BIRD draft (Muranyi) 5) Complete port naming proposal (Katz) 6) Create alternatives to the Touchstone 1.0 option line before the "R" character - TABLED 7) Complete ISS-IRD 1 Draft - Enable Cascading of S-parameters Through W-element (Mirmak) - TABLED 8) Complete/revise Touchstone 3.0 draft outline (Mirmak) – dependent on several items above Tabled ARs: - Arpad to give an example of the physical connectivity needed for EMD automation.