================================================================================ 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=EuMLfC3za7cvi4MXA5YAWlb7awy8ISM60Jj9clb5mCg&s=diCJfR0zzyygtTRvwIEj3gD5pi2iV6ChDyzhofZUbQY&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=EuMLfC3za7cvi4MXA5YAWlb7awy8ISM60Jj9clb5mCg&s=qMCbZu50lVIxH_lyXQsAEgzWBiUQ2fW75KB9w3QYQfQ&e= ================================================================================ Attendees from August 5, 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* Michael Mirmak convened the meeting. No patents were declared. Justin Butterfield took minutes. Review of Minutes: - Michael called for review of the minutes from the July 29, 2020 meeting. Michael displayed the minutes. Randy moved to approve the minutes. Lance seconded. The minutes were approved without objection. Review of ARs: - Bob to clarify the cascading restriction in connection rule 1.a.iv. - Bob sent out suggested revisions to this rule. - Randy and Bob to review the section 13.7 text. - Randy noted this is started but not yet complete. Opens: - Walter sent an email with suggested changes to the Designator Pin List, and he would like to discuss this. EMD Draft19 Review: Randy noted Bob had added changes to the Designator Pin List section. Bob's suggested text was added in red. Bob agreed with Walter that the section is awkward, but we should be careful making edits. There is an additional rule at the EMD Pin List interface, where we cannot have the same signal_name for two IO pins. Randy did not see this rule in the EMD Pin List section. Walter thought this rule does not make sense, and this should be a case we support. This means in the EMD two signals are coming in and coming together. Randy agreed we do not want this rule. Bob commented for Component we do not allow this. Walter noted for Component we have the one-to-one pin to pad requirement, but in EMD we want to support this. Bob asked if the signals would be brought in at the same time. Walter replied the signal_names are connected, and the EDA tool can bring in the net as an extended net. Walter had started to edit the text Bob added. Walter noted the word "connected" should be used, and we can make a statement about the connections across the signal_name. Distinguishing bus_label is not necessary. Bob disagreed. Walter noted some editorial changes from "pin_names" to "signal_names". Walter suggested to replace this section with his simpler paragraph. The paragraph notes there are no rules on how often a signal_name can appear in the EMD Pin List or Designator Pin List. Bob noted the signal_names are assigned by the model maker of the EMD. Walter commented this is true for both the EMD Pin List and the Designator Pin List. Bob noted the original text was trying to call out that we may have EMD pin_names and Designator pin_names which are different. Our syntax for I/O pin_names allows the DQs to be connected in the EMD model, but the association is based on the identical signal_name. The electrical connections are based on the pin_name connections. Michael asked if the new text proposed by Walter states that signal_names create the association, and if there is a similar rule for pin_names, this is not correct. Walter replied this is stated in the first sentence of the paragraph. The pin_names that have the same signal_name are connected. Michael asked if we agree on the rule. Randy thought we are saying the same the thing. Bob agreed the text by Walter states the issues. Walter noted there is no association between the signal_name in the EMD and the signal_name in the IBIS. Randy asked if we can replace Walter's proposed text. Michael agreed. Walter suggested to scrub the document for the word "associated". Michael will add this to the bin list if it is not already present. Walter also suggested to scrub for the word "pin_name". Michael will add a new item to the bin list for reviewing instances of "pin_name" [AR]. Randy replaced the Designator Pin List text and added a comment to double check this section. Randy noted Bob had added a rule to the connection rules 1.a. Bob suggested to add these new rules. Walter noted the new rule states that there is no rule. Michael commented the wording of the rule does not match the intent of the combinations of "designator.pin_name" rules. Walter asked what rule 1.a.iii means. Bob replied pin_names have to be different, but you can have the same signal_name in the Designator Pin List. Walter noted this is stated previously. Bob commented this is stated in rule 1.a.ii. Michael asked if we are combining two different rules. Bob noted the intent is to highlight the pin_names shall be distinct. Walter suggested to remove the text about signal_names being distinct. The Aggressor_Only on any one terminal means it cannot be used as a victim. There is nothing the IBIS parser needs to consider for Aggessor_Only. Bob commented, if the EMD Group contains Aggressor_Only, the model should be selected without Aggessor_Only. Walter commented, when the EDA tool looks at the model groups, it will pick the net with Aggressor_Only. We could say it is expected for the EDA tool to select the model without the Aggressor_Only. Bob suggested all models in a Group are taken into account. Walter commented it is up to the model maker to determine how to create models which properly relay the crosstalk information. Next Meeting: The next meeting will be August 12. Walter moved to adjourn. Randy 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