Fixing [Pin Mapping] Walter Katz Signal Integrity Software, Inc. IBIS Summit, DesignCon Santa Clara, CA January 22, 2016.

Slides:



Advertisements
Similar presentations
Package Die Ports Walter Katz IBIS Interconnect 10/31/12.
Advertisements

Computer Engineering II
Package EBD/EMD Walter Katz IBIS Interconnect 11/13/12.
Package and On-Die Interconnect Decisions Made and Proposed Solutions Walter Katz IBIS ATM December 3, 2013.
Interconnect Terminal Naming Walter Katz Signal Integrity Software, Inc. IBIS ATM January 9, 2015.
Terminal Draft 2 Walter Katz Signal Integrity Software, Inc. IBIS Interconnect July 9, 2014.
IBIS-ISS Package Status Walter Katz IBIS ATM December 17, 2014.
IBIS Interconnect Decision Time Walter Katz IBIS Interconnect 6/19/13.
EMC Models.
Introduction to Op Amps
IBIS Interconnect BIRD Draft 3 Walter Katz Signal Integrity Software, Inc. IBIS Summit, DesignCon Santa Clara, CA January 30, 2015.
Introduction to Op Amp Circuits ELEC 121. April 2004ELEC 121 Op Amps2 Basic Op-Amp The op-amp is a differential amplifier with a very high open loop gain.
EMC Models. 2 September 15 1.Models, what for ? 2.IC Models for EMC 3.Core Model 4.Package model 5.Test-bench models 6.Emission measurements/simulations.
01/30/04 *Other brands and names are the property of their respective owners Page 1 Futures Subcommittee Proposed “New” Futures Subcommittee To create,
Signal Integrity Software, Inc.Electronic Module Description© SiSoft, 2008 Electrical Module Description EMD A new approach to describing packages and.
IBIS-AMI and Direction Indication February 17, 2015 Updated Feb. 20, 2015 Michael Mirmak.
I N V E N T I V EI N V E N T I V E Updated Algorithmic Modeling Proposal for SERDES Tx and Rx Cadence, SiSoft DesignCon IBIS Summit Feb 1, 2007.
Interconnect Modeling Status Draft 1 Walter Katz … IBIS Summit, DesignCon January 31, 2013.
IBIS-ISS Package Proposal Status Walter Katz IBIS ATM January 7, 2014.
In, Out , InOut , Gnd , Vdd, Source follower
MICRO CONTROLLER MODULE 1. Learning Objectives Name some gadgets that use microcontrollers. Define a microcontroller. Differentiate between a computer.
© 2007 Cisco Systems, Inc. All rights reserved. 1 IBIS Quality Review A status review of the IBIS Quality specification Mike LaBonte, Cisco Systems.
Updated Interconnect Proposal Bob Ross, Teraspeed Labs EPEPS 2015 IBIS Summit San Jose, CA, October 28, 2015 Updated Interconnect.
The George Washington University School of Engineering and Applied Science Department of Electrical and Computer Engineering ECE122 – 30 Lab 5: Layout.
First, let’s review the structure and use of a breadboard.
General Purposes Input/ Output Daughter board for Univ Eval Rev B Julien Cercillieux University of Hawaii
IMIC DISCUSSION Bob Ross Interconnectix Business Unit Mentor Graphics Corporation IBIS Summit Meeting, San Diego, CA December 7, 1998.
03/05/04 *Other brands and names are the property of their respective owners Intel Confidential Page 1 Original Cookbook Objectives Triage to find keywords.
11/09/04 *Other brands and names are the property of their respective owners Page 1 The IBIS Specification and IEEE DASC Michael.
16- Agenda S-Parameters and Linear Analysis 4 Transmission Lines and Field Solver 5 IBIS 6 DAY 2 Synopsys 60-I-032-BSG-005 © 2007 Synopsys, Inc. All Rights.
1 © 2004 Cisco Systems, Inc. All rights reserved. Using the IBIS Quality Checklist Mike LaBonte, Cisco Systems IBIS Open Forum Summit 4 October 2004 Appendix.
Package Modeling Status Walter Katz IBIS Open Forum December 6, 2013.
12/4/2002 The Ground Conundrum - Class 20 Assignment: Find and research papers on this subject, be prepared to defend research.
Backchannel Issues Walter Katz Signal Integrity Software, Inc. IBIS-ATM April 8, 2014.
Updated Interconnect Proposal Bob Ross, Teraspeed Labs Draft Presented September 23, 2015 at the Interconnect Working Group Copyright.
Intel Confidential IBIS & ICM Interfacing: A New Proposal Michael Mirmak Signal Integrity Engineering Intel Corp. Chair,
IBIS & ICM Interfacing: Three Options Michael Mirmak Intel Corporation December 4, 2007.
A Tour of the IBIS Quality Specification DesignCon East IBIS Summit April 5, 2004 Robert Haller Signal Integrity Software, Inc. 6 Clock.
User defined measurements and test loads in IBIS Arpad Muranyi Signal Integrity Engineering Intel Corporation IBIS Cookbook / Futures.
06/02/04 *Other brands and names are the property of their respective owners Page 1 New IBIS Cookbook 1.0 Introduction.
Signal Integrity Software, Inc.Electronic Module Description© SiSoft, 2008 Electrical Module Description EMD A new approach to describing packages and.
Fixing GND in IBIS Walter Katz SiSoft IBIS-Packaging May
10/07/04 *Other brands and names are the property of their respective owners Page 1 IBIS & ICM Interfacing Options Alternative.
Updated Interconnect Proposal Bob Ross, Teraspeed Labs EPEPS 2015 IBIS Summit San Jose, CA, October 28, 2015 Updated Interconnect.
Pin Mapping Key Concepts From IBIS 6.0… “The [Pin Mapping] keyword names the connections between POWER and/or GND pins and buffer and/or terminator voltage.
Interconnect Terminal Mapping Figures 30 Sep
Full Mission Simulation Test Report RocketSat CU Boulder
References in IBIS Bob Ross, Teraspeed Labs IBIS ATM Meeting January 12, 2016 Copyright 2016 Teraspeed Labs 1.
Simulation [Model]s in IBIS Bob Ross, Teraspeed Labs Future Editorial Meeting April 22, 2016 Copyright 2016 Teraspeed Labs 1.
[Die Supply Pads] Walter Katz Signal Integrity Software, Inc. IBIS Interconnect January 6, 2016.
IBIS Interconnect BIRD Draft 0 Walter Katz Signal Integrity Software, Inc. IBIS Summit, DesignCon January 27, 2015.
[Pulldown Reference] [GND Clamp Reference] Offset in [Pulldown] [Ground Clamp] Walter Katz IBIS GND Editorial March 4, 2016.
IBIS 6.2 Editorial Resolutions
V7.0 Linked BIRDs Bob Ross IBIS Editorial Task Group April 7, 2017
Package Modeling Today
BIRD Terminology Issues Bob Ross
Walter Katz IBIS-ATM December 8, 2015
IBIS Interconnect Task Group December 15, 2015
Yuchen Chai, Pradeep Shenoy, Philip T. Krein
IBIS [Model Selector] Improvement Proposal
كارت هوشمند چيست وچگونه كار مي‌كند؟
IBIS Specification Roadmap
DUT vs DIA Device Under Test vs Device In Action
New IBIS Cookbook 1.0 Introduction 2.0 Pre-Modeling Steps
Pin Reference Concerns Bob Ross, Teraspeed Labs
Ground Recommendations Review of Recent Discussion
IBIS 6.2 Editorial Resolutions
Walter Katz Signal Integrity Software, Inc. September 10, 2019
IBIS Interconnect Task Group August 23, 2017
Presentation transcript:

Fixing [Pin Mapping] Walter Katz Signal Integrity Software, Inc. IBIS Summit, DesignCon Santa Clara, CA January 22, 2016

Overview IBIS Pin_name Signal_name Definitions Example Data Book Pin_name and Signal_name Data Associated with Signal_name Non – Power Aware IBIS Example Adding [Pin Mapping] Section Makes Model “Power Aware” Bus_label Indirection is Problematic, IBISCHK Reports No Errors: Enhancements to IBIS Signal_names_are_bus_labels Implies: When using Signal_names_are_bus_labels, POWER and GND Pins not Required in [Pin Mapping] Summary 2

IBIS Pin_name Signal_name Definitions Keyword:[Pin] Required:Yes Description:Associates the component’s I/O models to its various external pin names and signal names. Sub-Params:signal_name, model_name, R_pin, L_pin, C_pin Usage Rules:All pins on a component must be specified. The first column must contain the pin name. The second column, signal_name, gives the data book name for the signal on that pin. The third column, model_name, maps a pin to a specific I/O buffer model or model selector name. Each model_name must have a corresponding model or model selector name listed in a [Model] or [Model Selector] keyword below, unless it is a reserved model name (POWER, GND, or NC). Note that “pin name” is also referred to as pin_name in IBIS. Other common names for pin_name in the industry are “pin number”, “pin assignment”, “ball assignment”. 3

Example Data Book Pin_names and Signal_names DQ13 is Signal_name on Pin_name A2 4

Data Associated with Signal_name 5

Non – Power Aware IBIS Example [IBIS Ver] 3.2 [File Name] base.ibs [File Rev] 1.1 [Component] Memory [Manufacturer] SiSoft. [Package] R_pkg 265.4m 174.5m 406.4m L_pkg 1.568nH 1.047nH 2.378nH C_pkg 0.371pF 0.264pF 0.568pF | [Pin] signal_name model_name | Data Book Information 1 DM1 DM | Rails are VDD and VSS 11 VDD POWER | DC Power Supply 1.2V V 12 VSS GND | Ground | [Model] DQM Model_type Input Vinl = mV Vinh = mV C_comp 1.100pF 1.000pF 1.200pF [Voltage Range] V V V [Temperature Range] [End] 6

Adding [Pin Mapping] Section Makes Model “Power Aware” [Pin] signal_name model_name | Data Book Information 1 DM1 DM | Rails are VDD and VSS 11 VDD POWER | DC Power Supply 1.2V V 12 VSS GND | Ground [Pin Mapping] pulldown_ref pullup_ref gnd_clamp_ref power_clamp_ref ext_ref 1 VSS VDD 11 NC VDD 12 VSS NC The names in the [Pin Mapping] section are not signal_names, they are bus_labels. The following is equivalent to the above section. Making bus_labels the same as signal_name is the common method used in the industry. [Pin Mapping] pulldown_ref pullup_ref gnd_clamp_ref power_clamp_ref ext_ref 1 xyz def 11 NC def 12 xyz NC 7

Bus_label Indirection is Problematic IBIS CHK Reports No Errors: [Pin] signal_name model_name | Data Book Information 1 VDD POWER | DC Supply 1.2V V 2 VDDQ POWER | DC Supply 1.2V V 3 VDDQ GND | DC Supply 1.2V V 4 VPP POWER | DC Supply /1 0.1V 6 VSS GND | Ground 7 VSS POWER | Ground 10 DM1 DM | Rails are VDD VSS | [Pin Mapping] pulldown_ref pullup_ref gnd_clamp_ref power_clamp_ref ext_ref 1 NC PWR 2 NC PWR 3 GRND NC 4 NC PWR 6 GRND NC 7 NC PWR 10 GRND PWR Signal_names VDDQ and VSS are both POWER and GND? Bus_label GRND shorts VDDQ and VSS Bus_label PWR shorts VDD, VDDQ, VPP, and VSS 8

Enhancements to IBIS New Rules –All pins with the same signal_name must have the same model_name –All POWER and GND pins with the same bus_label must have the same signal_name New [Pin Mapping] Option –New sub-parameter Signal_names_are_bus_labels –If set, then bus_label defaults to signal_name on POWER and GND pins –Can still partition pins, pads and buffers with the same signal_name into sub-groups using bus_labels 9

Signal_names_are_bus_labels Implies: [Pin] signal_name model_name | Data Book Information 1 VDD POWER | DC Supply 1.2V V 2 VDDQ POWER | DC Supply 1.2V V 3 VDDQ POWER | DC Supply 1.2V V 4 VPP POWER | DC Supply /- 0.1V 6 VSS GND | Ground 7 VSS GND | Ground 10 DM1 DM | Rails are VDD VSS | [Pin Mapping] pulldown_ref pullup_ref gnd_clamp_ref power_clamp_ref ext_ref 1 NC VDD 2 NC VDDQ 3 NC VDDQ 4 NC VPP 6 VSS NC 7 VSS NC 10 VSS VDD 10

When using Signal_names_are_bus_labels, POWER and GND Pins not Required in [Pin Mapping] [Pin] signal_name model_name | Data Book Information 1 VDD POWER | DC Supply 1.2V V 2 VDDQ POWER | DC Supply 1.2V V 3 VDDQ POWER | DC Supply 1.2V V 4 VPP POWER | DC Supply /1 0.1V 6 VSS GND | Ground 7 VSS GND | Ground 10 DM1 DM | Rails are VDD VSS | [Pin Mapping] pulldown_ref pullup_ref gnd_clamp_ref power_clamp_ref ext_ref Signal_names_are_bus_labels 10 VSS VDD 11

Summary Signal_name defined as “Data Book Name” has consequences for power aware IBIS files and Power Deliver Networks. New rules are required to make [Pin Mapping] useable. Signal_names_are_bus_labels is a major simplification to [Pin Mapping]. I have not seen any [Pin Mapping] section that uses bus_labels other than signal_name. –Can still group pins, buffer supply terminals and die pads within a signal_name into bus_labels. 12