================================================================================ 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=gqlqK43nuYaB1GFn7fPwWR-jwIGbKNBvCMp_tH9jc_I&s=eWeCKrJzGf9EiASKpTpI6ECISHLCFVk3qchykDA14jI&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=gqlqK43nuYaB1GFn7fPwWR-jwIGbKNBvCMp_tH9jc_I&s=WZvizMTJfTU1Q7J3Os6g3ZlF7YQ7Y3M0WkyViGrL8L0&e= ================================================================================ Attendees from December 16, 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 convened the meeting. No patents were declared. Justin took minutes. Review of Minutes: - Michael called for review of the minutes from the December 9, 2020 meeting. Michael displayed the minutes. Randy noted two typos in the following: - Arpad [stated that] the problem with the phrase "can be considered connected" is whose decision is it to make the connection. - Michael highlight[ed] the sentence and added a comment. - Curtis moved to approve the minutes with the changes. Randy seconded. The minutes were approved without objection. Review of ARs: - Michael to send out EMD BIRD202.2 draft3. - Done. Opens: - Arpad sent a version of the document with proposed changes. He had accepted all previous changes to only focus on the changes to the EMD Pin List and Designator Pin List sections. BIRD202.2 draft3 review: Bob asked which version will be the starting point for the next draft. Randy replied if we like the changes from Arpad we can copy the changes into EMD draft3. Michael agreed. Arpad thought the original EMD Pin List and Designator Pin List sections did not flow well. He rewrote these sections to have a consistent flow. He also wanted to have consistency between the two keywords. The changes start at the Usage Rules and go to the first example. Michael noted the text addresses the comments on the number of columns. He asked what the phrase "pin type" means. Arpad replied "pin type" is I/O vs. rail vs. no-connect pins. Michael thought it becomes clear later in the text. Arpad noted most of the changes were moving sentences, but in a few cases he changed the wording. Michael asked if we use "no-connect" elsewhere. Randy replied we use "no-connect" later in this section. Michael asked about the single quotes for 'NC'. Arpad noted this was copied from the previous text, but it could be changed to double quotes. Michael asked about the sentence with the word "however", he suggested to make it two sentences. Bob noted we are not consistent with "e.g." and "i.e." followed by a comma or not. Michael stated we can search for this and correct it [AR]. Arpad noted the shorted and merging paragraph has more significant changes. The shorting is done by the bus_label in the [EMD Model] keyword. The bus_label in the Pin List does not do the shorting. Randy noted all the details are described in the [EMD Model] keyword. He asked if we want this much detail in this section. Bob asked if we can omit this text. Arpad stated the question is how do we explain the bus_label. Bob replied bus_label is a grouping of terminals. A rail terminal can be grouped by signal_name or bus_label. Randy stated the Pin List is just names of pins, and you can group the pins in the Pin List. In section 13.4 on page 27, we talk about how we can reduce terminals with bus_label. Bob stated all of the cases are described. Michael commented we have a short description of how the pins are merged. He asked if this is duplicate text. Arpad replied the text was there originally, and he thought we had this as an introduction. He only intended to make it easier to understand. Randy's concern was with putting too many details in this section. Michael asked if we can remove some of the text and add a reference to the [EMD Model] keyword. Randy agreed this would be good. Michael thought all of the details are captured later in the BIRD. Bob agreed. Arpad noted he still does not like the second sentence in the original paragraph. The connectivity of the merging is established with the terminal lines. Michael noted the proposed sentence is very similar. It is adding the details to make it more clear. Randy suggested to say the the merging is done with the terminal line syntax. This way we avoid discussion of the details. Michael made the proposed changes for EMD Pin List. Randy suggested to remove the reference to the EMD Model section. Arpad noted the Designator Pin List section has the same approach with changes to Usage Rules down to the first example. Randy noted there is a change in the Description field as well. Arpad commented there is an unenforceable rule for pin names. Randy commented you could check against the referenced IBIS file. Bob commented we need to list all the pins. It is not enforceable to look at the databook to check, and we cannot check the BGA grid. Michael asked about the phrase "[Begin EMD] keywords", and if "keywords" needs to be plural. Arpad thought it is referring to the Component and related keywords under Begin EMD. Michael suggested to delete the word "in". Michael asked about the phrase "containing the pin_name and signal_name entries". Randy replied it is specific to these columns. Bob asked about the phrase "no more and no less". Randy suggested to replace this with the word "only". Curtis suggested the word "exactly". Randy suggested to change the first "containing" to "consist of". Arpad suggested to make the same changes to the EMD Pin List. Curtis asked about the meaning of NC in the Designator Pin List. Bob stated if the pin is not defined you have the option of routing to it or not routing to it. NC covers everything, and it could cover pins which IBIS cannot model. Michael asked if we want to revisit this, and he highlighted this section. Michael will make the changes to the EMD Pin List to match the Designator Pin List and send out EMD BIRD202.2 draft4 [AR]. Next Meeting: The next meeting will be January 6. Curtis 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