================================================================================ 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=a2Al-j-w-3cXNvxkenZWVJ0EBr7I9CtTRcZHZLe8_1w&s=IH7s8-92zkXbfTrklOA5H9GDGLjuftppjW3ovuistcM&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=a2Al-j-w-3cXNvxkenZWVJ0EBr7I9CtTRcZHZLe8_1w&s=aluU-tYkixudr37c_ZrQAGNKYGmVNhVpGMQK4joscAA&e= ================================================================================ Attendees from August 12, 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 August 5, 2020 meeting. Michael displayed the minutes. Randy commented on line 110 the statement "with aggressor_only" should be "without aggressor_only". Randy moved to approve the minutes with this change. Michael seconded. The minutes were approved without objection. Review of ARs: - Michael to add a new item to the bin list for reviewing instances of "pin_name". - Michael reported this is done, and he has sent out an updated copy of the bin list. - Randy and Bob to review the section 13.7 text. - Randy reported the example has been redone, but it needs to have comments added. He suggested, if we have time, we can review this. Opens: - Randy noted there is text to review from Walter regarding changes how the term "associated" is used. EMD Draft20 Review: Walter had sent out a version with suggested changes. Randy suggested to change the phrase "CAD net" to "CAD net name". Walter's change was from the term "associated" to "assigned names", which is standard terminology used in CAD systems. The word "associated" is used in many different contexts in this BIRD. Randy noted one alternative would be to say "assigned to a CAD net". Bob agreed with the changes. Bob commented one additional change would be to clarify I/O pins on page 7, as this is the first mention in EMD. Bob noted, on page 13, there is a definition, but that is later in the EMD document. Walter noted "I/O pins" is referred to many times in the IBIS document. Bob suggested to reinforce the definition. Randy suggested for Bob to propose this change over email. Randy asked which version of the suggested change is preferred. Michael preferred to add the word "name". Randy made this change and Walter's suggested changes. Randy noted there were other changes on page 13. These relate to changing "associated" to "assigned". Michael asked about the difference between "signal_name" and "name of the signal". Randy changed "name of the signal" to "signal_name". Randy removed the parenthetical "aka associated" on page 13. Bob commented it is not stated that this is for I/O pins. Randy asked if this is true for rails. Bob replied you could have a bus_label. Walter stated it is the same for rails. Randy noted they are still connected if they have bus_label. Walter noted two signals are connected if they have the same signal_name. Randy added they are connected but not necessarily shorted. Bob noted this is true at the same interface. Randy stated that is why we say connected and not shorted. Walter commented an EMD model can short groups of pins to a single terminal. Bob stated, for rails, we provide options for individual pin_names, signal_names, and bus_labels. Walter commented the model determines how well they are connected. Michael asked if the objection is to the word "connected". He asked if it is implied that the only way to connect the signals is through having the same signal_name. Randy replied we go into more detail later in the section. Randy noted under the Terminal_type description there is another change from "associated" to "connected". Bob was not sure about this change. Randy suggested to change this to "connected" in quotes. It is a similar statement to the previous one. Michael asked if the signal_name is the only way to specify the connections. Walter replied there is the case of series connections where the extended net is created. Bob agreed they are implied to be connected. Michael suggested to not to use the quotes, but we do need to define the term "connected". Randy stated under bus_label the word "associated" is changed to "shorted". And, he was not sure about this change. Walter commented the goal of bus_label is to take a subset of rail pins to short them to one terminal. Randy commented this text is restating what bus_label means. He asked if we need this and suggested to change bus_label to subset. Bob noted the *.bus_label can be used for left side, right side routing. Michael asked if the word "connected" can be used. Bob agreed, but stated "connected" is ambiguous. Walter disagreed. Michael noted we need a definition and to be consistent using the word "connected". Bob commented all we are doing is defining terminal connections at each designator. There is an implication that they are connected. The syntax assumes they are connected, but that doesn't mean they are electrically connected unless you specify the connections. Bob noted, on page 9 under EMD Pin List, we make a statement that the second column lists the data book name. This statement needs changed, as it does not need to be data book names. Michael noted this is copied from the Pin keyword. Bob commented even at the EMD interface we can assign the name to make the connection. Randy asked why we would not match the signal_name from the data book. Michael noted there are parser implications. Randy commented the EMD Pin List and the Designator Pin list are different. The EMD pin list should match the data book or the customer won't know how to connect it. At the Designator Pin List, the connections are made at that level. Next Meeting: The next meeting will be August 19. Randy moved to adjourn. Arpad 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