V7. 0 Linked BIRDs Bob Ross bob@teraspeedlabs V7.0 Linked BIRDs Bob Ross bob@teraspeedlabs.com IBIS Editorial Task Group April 7, 2017 Copyright 2017 Teraspeed Labs

Several BIRDs Linked with V6.1 and/or with Other BIRDs Purpose: what should go into the next release? Some major links shown next with the legend: X Y (reason) means Y requires X (because …) Links documented in BIRDs and imply same release Otherwise the Editorial Task Group would have to do the links Also, parser developer might raise more linkage issues Copyright 2017 Teraspeed Labs

BIRD186.1 File Name Subdirectories and File Names BIRD186.1  Version 6.1 (many file formats and files) BIRD186.1  BIRD189.X (.ims subdirectory calls and .ims file) BIRD186.1  BIRD147.6 (subdirectories for backchannel) BIRD186.1  Version 6.1 (assumes no impact of Supporting File name subdirectories) BIRD186.1  Version 6.1, BIRDs (file name capitalization relaxation throughout, but still maintain distinct file capitalization differences) Copyright 2017 Teraspeed Labs

BIRD181.X Terminal Names BIRD181.X  Version 6.1 (standard I-V tables) BIRD181.X  New BIRDs (for other I-V table terminals, notes on data derivation, [ISSO PU], etc.) BIRD181.X  Potential Reference BIRD (terminal notation and equation formulation) IBIS 6.1 [Receiver Thresholds]  BIRD189.X (terminal names such as Pullup_ref, etc.) BIRD189.X  BIRD181.X (match Buffer terminal names including Pullup_ref, Buf_I/O versus Buffer_I/O issue) Copyright 2017 Teraspeed Labs

BIRD182 [Pin Mapping] bus_label, BIRD180, BIRD184 pin_name rules BIRD182 Version 6.1 (new rules and bus_label defaults to signal_name) BIRD182  Version 6.1 (unknown impact on [Define Package Model] checking) BIRD189.X  Version 6.1 (two more ways to add bus_label to [Pin Mapping] with [Bus Label] and [Die Supply Pads] , more checks for POWER/GND and signal_name conflicts) BIRD180, BIRD184  IBIS V6.1 (distinct pin_names, rail model_name differences versus rail signal_name) Copyright 2017 Teraspeed Labs

Candidate BIRDs 12-18? BIRDs BIRD158.X unknown linkage to BIRD189.X? Some with internal dependencies E.g., Five BCI parameters with new all or none rule More BIRDs add more … Spec work Contract work for checking rules and for quote Parser project includes source code changes, test cases, error code spreadsheet update, and testing Funding issues and longer schedule Copyright 2017 Teraspeed Labs

Parser Contract Writing Can Begin Legally required for services and payment Many BIRDs already known Need to specify some checking details Needed for an accurate quote Signed contract needed before parser work begins Parser funding needs to be assured before parser work begins Project could be broken up, but an incomplete parser should never be officially released Copyright 2017 Teraspeed Labs

Example of $10,000 Contract Detail for ibischk6 V6.0.0 (7 BIRDs) Copyright 2017 Teraspeed Labs

Example: Checking Details Copyright 2017 Teraspeed Labs

Example: Checking Details Copyright 2017 Teraspeed Labs

Example: Checking Details Copyright 2017 Teraspeed Labs

Parser Delivery Delivered only after all test cases work correctly Complexity implies several iterations with parser developer before actual distribution Example: Four iterations for ibischk6 V6.1.3 due to issues and failures with IBIS-AMI BUG179 checking between executable models and platforms and bits Follow on Version 6.1 work including PAM4 addition - $5,800 Copyright 2017 Teraspeed Labs

Conclusions Full IBIS V7.0 requires more BIRDs and time No quick release of ibischk7 V7.0.0 Can start parser contract with what we know E.g., spell out many tests needed for BIRD189.X Quicker release requires trading off features and “requirements” for other “requirements” E.g., Backchannel without subdirectories and no BIRD186.X Otherwise BIRD147.6 is pushed to the end with BIRD189.X (Interconnect Modeling) What is the best path forward? Copyright 2017 Teraspeed Labs