1. IBIS & ICM Interfacing: Simple Link Michael Mirmak September 21, 2005

2. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link2 Original ICM-IBIS Proposal Too Complex Original ICM-IBIS proposals (“BIRD100”) Permitted ICM with “classic” IBIS Allowed complex package paths for IBIS 3.2/4.0 structures Sketched out [External Circuit], [External Model] support Need to simplify proposal Tool vendor discomfort at [Pin] changes [Pin Mapping] complicates classic IBIS support Size of resulting BIRD would have been very large

3. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link3 [External Circuit] Linking ICM to IBIS [E. Circuit] Use [Node Declarations] to list internal ICM map pin names |**************************************** [Node Declarations] |Die pads OR PIN NAMES A1, A2, A3, A4 buff1, buff2, buff3, buff4 [End Node Declarations] |**************************************** [ICM Pin Map] Example1_external Pin_order Row_ordered Num_of_columns = 4 Num_of_rows = 1 Pin_list |Pin Name A1AD2 A2AD5 A3AD7 A4GND Only downsides: Names must be matched; arbitrary packages not reusable Both sides of ICM interconnect are mapped [ICM Pin Map] Example1_internal Pin_order Row_ordered Num_of_columns = 4 Num_of_rows = 1 Pin_list |Pin Name buff1AD2 buff2 AD5 buff3 AD7 buff4 GND IBIS ICM (IIRD8)

4. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link4 Simplification Proposals No update to [Pin] No support of multiple paths under “classic IBIS” Weak support of ICM with [Pin Mapping] No “dot syntax” ICM can only be used with… [External Circuit] through [Node Declarations] [Model]/[E. Model] through 1-to-1 package descriptions Assumptions No integrated parser [Pin Mapping] connects packages to buffers

6. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link6 BACKUP

7. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link7 Four Cases We must handle these four cases to be complete Case 1 – ICM expresses coupling [External Model] Digital Port ICM Pin A1 Pin B1 Pin C1

8. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link8 Four Cases Case 2 – Wired-or or “mux” connections Multiple pins, single [Model] [External Model] Digital Port ICM Pin A1 Pin B1 Pin C1

9. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link9 Four Cases Case 3 – Coupling & power distribution Single model, single signal pin No different than Case 2, from [Pin] perspective [External Model] Digital Port ICM POWER Pin A1 GND

10. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link10 Four Cases Case 4 – Wired-or or “mux” connection Single pin, multiple [Model]s [External Model] Digital Port ICM Pin A1

11. * Other brands and names may be the property of others 02.02.06ICM and IBIS Interfacing: Simple Link11 Four Cases Case 4a – Wired-or or “mux” connection Single pin, multiple [Model]s Variation: where are the package t-lines linked? [External Model] Digital Port ICM Pin A1