================================================================================ IBIS INTERCONNECT TASK GROUP http://www.ibis.org/interconnect_wip/ Mailing list: ibis-interconnect@freelists.org Archives at http://www.freelists.org/archive/ibis-interconn/ ================================================================================ Attendees from February 19, 2020 Meeting (* means attended at least using audio) ANSYS Curtis Clark Cadence Design Systems Bradley Brim Intel Corp. Michael Mirmak*, Ifiok Umoh 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* 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 February 12, 2020 meeting. Walter Katz moved to approve the minutes. Randy Wolff seconded. The minutes were approved without objection. Review of ARs: - Bob Ross to propose changes to the Aggressor_Only rules. - Michael asked if anything was sent out on this. Bob replied he sent out an email, but he did not draft text changes. - Michael to make changes in the EMD draft for task list items #6 and #7. - Michael reported he as completed item #7, but he has questions on item #6. - Randy to create zoomed-in versions of the drawings and add labels. - Randy reported he sent out a version of this for review. - Walter noted he had an outstanding an AR to generate an EMD example and parser. - Michael commented this is on the task list as item #9. - Michael stated it was not captured in the minutes as an AR, but he had a task to work with Steve Parker on posting documents to the website. The minutes have now been posted, but documents are having issues posting. Randy asked if there is a preferred way to send files that we want to have uploaded. Michael will ask Steve the preferred method of communicating files to be posted [AR]. Opens: - Walter stated he is ready to discuss his EMD parser and RDIMM example. - Bob proposed to add text describing extended nets. Randy stated we have text on extended nets and possibly this needs to be moved. Bob agreed this could be a solution. Michael asked if we should add this to the task list. Bob stated this is related to the notion of connected. Randy agreed with adding a task. Bob noted the two methods for connecting extended nets are not stated. Randy commented his drawings would make this more clear. EMD Editorial Review: Michael asked if we want to date code the EMD drafts and document when a particular task has been completed. Randy replied it is probably not necessary, and he is okay with the current format. Michael stated we can track which draft items are implemented. Michael asked how to mark the number of the BIRD and revised date in the current draft. Randy suggested to say 202.1 in the BIRD number. Walter suggested to use the revised date to track the revision date. Bob noted the revised date would be replaced once the draft is completed. Michael noted the changes for the item #7 have been fixed. He also fixed some spacing issues on pages 19 and 25. Michael marked item #7 as fixed on the task list. Michael commented, for item #6, the I/O pin_names appears far down in the document. The EMD Group appears about half way in the document. I/O pin_names are already defined in the document, and many of the other terms and rules have already been defined before this section. Bob noted the concern is we have not defined what an EMD model terminal line is yet. There can be two groups with the same I/O pin_names but different terminals, but these concepts have not been defined. The terminal_lines are not yet defined for connecting to the electrical models. The Aggressor_Only reference is another issue. Michael changed the name of the task, and he can take a look at editing this. Bob suggested we could move this section after the EMD Set definition, but we would need a reference to this section. EMD Example Diagram: Randy reviewed the updated example diagram. He added text below the figure to describe the example. Bob asked about the back side designators U7-U11. Randy thought it looked too busy with showing the backside components. Bob noted the U7-U11 components are referenced in the other figures and example. Randy noted this is the only way he could think to show it. He asked if there were any other concerns with this. Bob noted J1.211 is a pin, but the notation is similar to the designator. Randy suggested to change J1.211 to 211. Randy changed other instances of J1.211 to 211 in the zoomed-in versions. Bob suggested that EMD Set and EMD Models include an extended net example. The EBD file would be different for the ways of connecting the extended net. Randy stated he can create an additional example, and he can elaborate how to do this. Michael asked where we would like to include these figures. Bob noted it might be after Table 41 for the terminal rules. Michael commented this is just before the examples. Bob noted one change is that signal_names determine which pins are connected at different interfaces. He suggested to add this text after the table, since it implies the connectivity. Randy agreed it would be good to include his figures after the table. We will need to decide if we want to include Randy's example. Randy noted he still needs to add a termination voltage rail to the example which connects through a resistor to the rail. Bob noted bus_label or signal_name could be used to connect the rail. Randy asked if we want to show the resistor as a terminator model, or if we want to connect it to the rail. Bob commented we already support this with Rpower terminator models. Arpad Muranyi preferred to not use the Rpower terminator model to keep the EMD model simple. Randy noted these could be series models for the resistor packs. He agreed with not having a terminator. Arpad stated we need to support both cases, but for the examples, he would like the format to be the recommended method. Randy asked Justin, for EBD models, how the terminators are included. Justin replied they have used the Rpower terminator models, as this was the only option for EBDs. Bob commented we could use the [R Series] keyword, but it has EDA tool issues. Walter suggested to review his results of creating an EMD, as it will show these issues. Michael asked if Randy plans to add to the example for the extended net cases. Randy will update his example to show the different methods for modeling the extended nets [AR]. Arpad asked if it would make sense to have a stacked die example. Randy stated we could create a similar example for this. Next Meeting: The next meeting will be February 26. 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