From: Mirmak, Michael Sent: Tuesday, March 12, 2013 9:33 PM To: IBIS-Interconnect (ibis-interconn@freelists.org) Subject: Minutes, Feb. 27, 2013 IBIS-Interconnect Task Group and March 13, 2013 Agenda ====================================================================== IBIS INTERCONNECT TASK GROUP MEETING http://www.eda.org/ibis/interconnect_wip/ Mailing list: ibis-interconn@freelists.org ====================================================================== Next meeting: March 13, 2013 8 AM US Pacific Time Agenda: Attendance Call for Patents Agenda and Opens Review Si2 Specification Status S-parameter Direction and Status EMD Draft Rev. 3 Comments/Review Next Meetings’ Schedule/Agenda • Mar. 20 • Mar. 27 For international numbers, please contact Michael Mirmak. Note: in case of issues with Lync we will use the WebEx noted at the bottom of this message ......................................................................................................................................... Join online meeting https://meet.intel.com/michael.mirmak/QZ193W0C First online meeting? [!OC([1033])!] ......................................................................................................................................... <--- Reservationless Bridge – Do not edit or remove --- 916-356-2663, 8-356-2663, Bridge: 2, Passcode: 8625431 Speed dialer: inteldialer://2,8625431 -----------------------------------------------------------------> Note: in case of issues with Lync we will use the WebEx noted at the bottom of this message ====================================================================== Attendees, Feb. 20 Agilent Technologies Radek Biernacki* Altera David Banas ANSYS [Luis Armenta], Steve Pytel Cadence Design Systems Brad Brim*, Ambrish Varma* Intel Michael Mirmak* Mentor Graphics Arpad Muranyi* Micron Technology Justin Butterfield, Randy Wolff* QLogic Jason Zhou Signal Integrity Software Walter Katz* Teraspeed Consulting Group Bob Ross Minutes No patents were declared. Brad Brim noted that the Si2 60-day exclusion period for their package specification ends March 11. Walter Katz reviewed his EMD changes in draft 2. Radek Biernacki noted that fork is present in EBD; is it here? Walter noted that this is covered in the interconnect branch, not the pin branch. Forks will be embedded in the interconnect branch. These would be called "visible pins". Brad asked whether this is on the board side or package side list. Walter stated that the die side is not here; only board side. Bob Ross asked whether this supports an EMD file calling it. Walter answered yes, it supports having an EMD calling it/containing one as well; this is almost identical to the EBD Component section. An open question: is a component section needed? Bob replied that it is not needed, but would be helpful as a cross-check. A simple tree might suffice. Walter stated that connections between visible pins and component pins are supported. Bob asked whether, for example, for DQ1 should be added on to that U3.18? Walter answered no. A connection is a non-time-dependent that shares a level. Pin A2, the visible pin, is connected inside the module to Pin U1.18, U2.18 and U3.18. A pin can occur in one and only one connection. Radek asked whether unconnected pins are involved. Walter answered that unconnected pins would not appear in any connection or may be in a connection by itself. Randy raised a DQx example - imagine this is a device with a controller connected to the visible pins, with connections to stacked NAND devices inside the package. This section shows the connections in that scenario, or in a registered DIMM scenario? Walter responded yes. Randy added that, in EBD this is not supported, so this is a new feature; tools would need to simulate these internal connections. Walter stated that there's a connection between branches, for each IBIS-ISS subcircuit for example. Each one can be a single, or coupled, or differential, or signal or coupled power and signal connection. Could have three corners at least; the question is having a list or not for more corners. Parameters look like strings/IBIS values (should be legal IBIS-ISS parameter values). Michael Mirmak asked about loss- based corners. Ports are always numbers. Radek asked whether you can mix ports from different connections. Walter noted that this can be handled by an example; ports do not have to be in numerical order. Terminating unused ports is an open question. If I have some connections that are not including all the pins, how is this handled? Does this make sense, particularly for supplies? Bob replied that, the way this is written, supply pins are not included. Walter will update the document to properly handle this (pullups are particular challenges, for example). Brad asked whether this will support M connections on the board side and N on the die side. Nets B1, B2, B3 are power nets; are B1-net1, B2-net1, etc. to be treated as extended nets? Walter responded yes, that these are qualified by the reference designator. Bob suggested that a conditional vote be taken based on the status of Si2. Radek suggested adding text to summarize of functionality relative to EBD, to show where the specification is gaining and losing features. ====================================================================== In case of Lync issues only, we will switch to WebEx as noted below. Meeting Number: 732 940 715 Meeting Password: IBIS ------------------------------------------------------- To join this meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://sisoft.webex.com/sisoft/j.php?J=732940715&PW=NNWY2NmRmZTY0 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: IBIS 4. Click "Join". 5. Follow the instructions that appear on your screen. ------------------------------------------------------- Audio conference information ------------------------------------------------------- Call-in toll number (US/Canada): 1-650-479-3208 Access code:732 940 715 http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.