================================================================================ 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=qbDiSNVOZ3qOEjhwxPvH3EIne0BXsxpR_SQFdHEO3I0&s=Y0vm_5wo-bnuy6JCo3sJEeGqrzkSOlu1v0mGpEhT2VE&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=qbDiSNVOZ3qOEjhwxPvH3EIne0BXsxpR_SQFdHEO3I0&s=oXBpX7zxvUsBlmYNnfUBE5rPIGI82TfSUR9Ja5YGeAU&e= ================================================================================ Attendees from February 3, 2021 Meeting (* means attended at least using audio) ANSYS Curtis Clark Intel Corp. Michael Mirmak* Mentor, A Siemens Business Arpad Muranyi* Micron Technology Justin Butterfield* Randy Wolff* SiSoft (MathWorks) Walter Katz 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 January 27, 2021 meeting. Michael displayed the minutes. Randy Wolff moved to approve the minutes. Arpad Muranyi seconded. The minutes were approved without objection. Review of ARs: - Michael to submit BIRD202.2 draft8 to the IBIS Open Forum with an email to the reflector. - Done. - Randy and Arpad to create a proposal for adding a name to EMD Parts list. - Michael reported this is done and we will review this today. Opens: - None. EMD Parts Selector Discussion: Randy shared slides on a proposal to add an EMD Parts list selector. He would like to have a way to support multiple configurations. One idea is to add an EMD Configuration Selector keyword. This would follow the Model Selector keyword. It would be an optional keyword and would have a config_name and description field. Randy detailed additional rules for EMD Parts and Voltage List in the case the model has this EMD Configuration Selector. Randy gave an example of an EMD pointing to multiple temperature options. This adds the config_name column. The second example points to different voltage range parts. There are two Voltage Lists that link to the EMD Parts. Michael asked if we have any similar keywords, where sometimes there is an argument to the keyword and sometimes there is not. Randy was not sure. Bob Ross thought we have not done this before. Arpad suggested to make it required to have the name. Randy asked if EMD Configuration Selector requires more than one entry. One question is how to handle the nesting. The first entry could be the default. Randy detailed some parser checking cases. Bob stated one idea would be to give a name to the Voltage List and to make this mandatory, but it could be a problem in a combined name case such as Example 1. We could add an additional column to give the Voltage List a name in the configuration selector. Bob stated the problem could be that the Voltage List is optional. He would rather have the additional columns and you could have all the combinations. Arpad suggested we should not allow nesting. Bob commented the nesting is an issue that gets complicated. Randy gave an example of when nesting would be used. We have a component EMD which has some selections. We could use this component EMD on a circuit board with an EMD model. Randy asked if this will break anything. Arpad replied, on the board side, there would not be variants on the voltage, and the selection would have to be done at the lower level. The reason we added Voltage List is for the case of on-board termination sources. This is why we should have a separate Voltage List from the EMD Parts. Bob stated there could be Voltage List choices up to the number of EMD Parts lists. The Voltage List is completely optional. This approach could work with an additional column in the EMD Configuration Selector. Bob stated the only way to solve the nesting problem is for the EDA tool to provide the selection at all levels. Michael asked if we are concerned about nesting and if the nesting levels could be infinite. He asked if there is a way to calculate the levels of the nesting. Bob replied that we already limit the nesting levels in the specification to six. He thought it is simple to find the nesting level. Arpad asked if we can have an integer to associate the level. Randy was not sure what to put in the field for the name. Arpad stated the EDA tool will provide a selection drop-down menu. He asked how does it provide the selection at the lower level. He asked if this is always up to the user or if the model maker would want to specify this. Randy replied it depends if the model maker wants to limit the selections. Bob commented the EDA tool has to identify the nested configuration selection. Arpad commented, in the nested case, the content of the EDA tool selection list would depend on the selections at the higher level. Arpad asked if this proposed change is worth pursuing. Michael asked if there is a need and if that need is great enough to include in IBIS 7.1. Arpad replied the concern was if it would be possible to add this later and if we need any changes now to support this later. Randy thought, if we do not find a solution now, we will not be able to add it later. Bob noted it would be possible to add later, but we would need to add all new keywords. Arpad suggested, if we added names for the EMD Parts and Voltage List, the EDA tool could come up with their own solution. Randy asked if this would allow multiple keywords. Bob favored to have the EMD Configuration Selector. Arpad did not like adding new similar keywords later, as this can be confusing for users and model makers. Bob stated the EMD Configuration Selector would allow the model maker to define the valid combinations, and adding the names is a good solution. We will not be able to solve the nesting problems. Michael asked if we need to issue a BIRD202.3 or write a new BIRD for this change. Arpad favored a BIRD202.3. Randy agreed. Arpad asked what is our conclusion to add the proposal. Randy will add the proposal to the BIRD [AR]. Arpad asked if we will add a column to EMD Configuration Selector. Randy stated this is one question we need to resolve. Michael suggested to highlight this choice in the BIRD draft. Next Meeting: The next meeting will be February 10. Arpad moved to adjourn. Randy seconded. The meeting adjourned without objection. ================================================================================ Bin List: IBIS-ISS Parser: - IBIS-ISS parser scope document