================================================================================ IBIS INTERCONNECT TASK GROUP https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibis.org_interconnect-5Fwip_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=iQFVeiIJjSeQUIExns3kof5WxLa1NY6Wj8UUo2Uj2do&s=uR3KuEGl4JCYehaCoeUCyPmEUq1cufWMmQTg1yNFqoU&e= Mailing list: ibis-interconnect@freelists.org Archives at https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_archive_ibis-2Dinterconn_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=iQFVeiIJjSeQUIExns3kof5WxLa1NY6Wj8UUo2Uj2do&s=CSKJU6ECJE69-8vwJitqDupnexJpeJyf6o6E3MlkzeY&e= ================================================================================ Attendees from October 28, 2020 Meeting (* means attended at least using audio) ANSYS Curtis Clark* Intel Corp. Michael Mirmak Ifiok Umoh Eric Edwards Keysight Technologies Radek Biernacki Mentor, A Siemens Business Arpad Muranyi* Micron Technology Justin Butterfield* Randy Wolff* SiSoft Walter Katz Mike LaBonte Teraspeed Labs Bob Ross* Zuken USA Lance Wang* Randy Wolff convened the meeting. No patents were declared. Justin Butterfield took minutes. Review of Minutes: - Randy called for review of the minutes from the October 21, 2020 meeting. Randy displayed the minutes. Lance moved to approve the minutes. Bob seconded. The minutes were approved without objection. Review of ARs: - Randy and Michael to check if the most recent drafts have been posted to the website. - Randy reported the drafts are starting to be updated. - Michael to move the definition of designators to section 13. - Randy suggested to keep this open [AR]. - Randy will add the regular Interconnect meeting participants to the Requestor list. - Randy reported this is done in draft29. Opens: - None. EMD Draft29 Review: Randy shared the latest draft and saved it as draft30. Arpad noted a mistake in the example on page 28. The example was fixed to include pin_name. Arpad sent some questions over email. We describe the connection in the terminal lines, and connecting by the signal_name can be a little redundant. While, the tool does not know what is in the S-parameter model for instance. He asked if this duplication is necessary. If we have the same device, we repeat the Designator Pin List for each of these devices. Randy replied this is required to be able to trace through by signal_name to understand the connections. Arpad asked if we have, for a designator, something similar to EMD Parts and EMD Designator List. If we have the same connectivity, we could have a model selector to change the designator selection. Randy commented he would have a use for this with memory devices, and the only way to do this currently would be to have multiple EMD files. Arpad asked if you could have a selector for the file reference and the component. Randy noted we would have an interaction with the Voltage List. Walter noted a DIMM can be populated with different parts or part numbers. It is a different case from running at a different voltage. Arpad commented the connectivity would be the same of the IBIS and only the voltage may be different. Walter commented you may want to have an EMD Parts selector. The alternative would be to include different files with a file include. Arpad asked if we have a similar concept to the Group in Interconnect. Walter stated, in his tool, they added logic to pass in external parameters to set the configuration. This could be solved in a generic way to configure IBIS files. Randy commented we have this limitation in EBD currently. One example is when they have multiple temperature grade models. Arpad stated, if this is a more involved question, he doesn't want to hold up this BIRD. Randy suggested this could be added later to have an EMD Parts selector. Arpad asked if we want to allow these to be independently selectable or have a group selection. Walter thought adding logic for file includes would be a better generic solution to add configurations. Arpad agreed this would be a good solution. Randy suggested to continue with this BIRD, and this is a good issue to discuss later. Bob noted the [EMD Set] keyword should be required. EMD Group is required, and it requires at least one EMD Set. This is different from Interconnect. Bob noted the [Manufacturer] keyword is listed as required. But, in EMD Set, it may be used. Arpad asked, in IBIS, if Manufacturer is required. Randy replied it is required for EMD Set. Bob noted sometimes it is required for IBIS. Randy noted Manufacturer is required for .ibs, .pkg, and .ebd, but it is not required in Interconnect. Randy commented the Interconnect Model Set is not required. Bob noted, for the .emd file, EMD Set is always required. Arpad asked why it would not be required in the Interconnect syntax. Bob was not sure, but the Manufacturer is informational. Walter stated the IBIS file is a component level model, and the manufacturer is usually the same for the package. But, for DIMMs the manufacturer may be different. Randy noted at the top-level it is required, but for the EMD Set it is not required. Arpad asked if the use of brackets is not consistent in the introduction. Randy replied, on the first instance of a keyword, we use the brackets, and the subsequent instances do not have the brackets. Bob asked if EMD Parts is required. For instance, how would you model a bare backplane or a passive only structure, where the EMD Pin List describes all the connections. Bob asked if we exclude this case and the connector case. We had EMD Parts as optional, and now it is required, which would not support this case. Walter commented you could have an empty EMD Parts list. Randy agreed there is no rule saying we need an entry in the EMD Parts list. Bob asked if EMD Parts should be required. Randy thought both EMD Parts and EMD Designator List would not be required. Randy was not opposed to this, but we would need to add a statement about this. Bob suggested to add a paragraph in the Other Notes on page 11. Randy will propose text for when EMD parts would not be needed [AR]. Curtis asked about the statement of the issue, which states this proposal does not encompass connectors. He asked if we want to remove this. Bob was okay with removing that statement. Randy removed this statement. Bob asked, on page 27, about the word "all" in italics. Randy suggested to make the next instance of "all" italics as well. Bob suggested, on page 3, to remove the question marks. Randy removed this but retained the highlight. Bob commented, on page 17, the word "must" should be changed to "shall". This could be a global change. Arpad suggested to say "shall be placed". Randy asked if we should submit the EMD BIRD to the IBIS Open Forum. Bob moved to submit the current EMD draft as BIRD202.1 with the changes as discussed. Arpad seconded. There were no objections. Randy to submit the current EMD draft as BIRD202.1 to the IBIS Open Forum [AR]. Arpad asked if we will have a meeting next week. Randy proposed to hold the meeting only if Michael is available. Next Meeting: The next meeting will be TBD. Bob moved to adjourn. Curtis seconded. The meeting adjourned without objection. ================================================================================ Bin List: EMD Comments to be Resolved: (See BIRD202.1 tracking spreadsheet) IBIS-ISS Parser: - IBIS-ISS parser scope document