Transcript Model Encryption

IBIS 5.0
Pending Changes

IBIS 5.0 has several BIRDs already “queued”
–
–
–
–
–
–
–
BIRD74.6
BIRD95.6
BIRD97.2/98
BIRD103.1
BIRD1xx
BIRD1xx
BIRD1xx
– EMI Parameters
– Power Integrity Analysis using IBIS
– Gate Modulation Effect
– [Model Spec] DDR2 Over/Undershoot
– [External Model] under [Circuit Call]
– ICM-IBIS Linking
– User-Defined Measurements
IBIS Futures Task Group
1
IBIS 5.0 Direction

IBIS 5.0 is “a fork in the road”
– With each revision, we add keywords,
subparameters
– Features from previous versions unchanged
 Clarifications

excepted
IBIS 5.0 becoming highly encumbered
– 101 keywords in IBIS 4.2
– New features have to avoid stepping on old ones
– Example: ICM-IBIS link nearly impossible due to
paths blocked by old requirements, assumptions
IBIS Futures Task Group
2
Proposed Actions
“Splitting” IBIS 5.0 into sub-specifications

New compatibility switch
– If switch is in “non-compatible” mode, rules
regarding previous versions are simplified
– “Compatible” mode keeps 4.2 rules & features
plus enhancements we selectively add
New keyword, feature
development need not be
hampered by previous
version limitations
Old features can be
maintained as they
are phased out
IBIS Futures Task Group
3
Non-Compatible Mode

New mode eliminates keywords
– Package, TTgnd, TTpower
– Voltage Range, Driver Schedule, Submodel
– PKG, EBD, Diff Pin, Pin Mapping, etc.

Simplify features using multi-lingual structure
– [Pin] no longer assumes 1:1 link to [Model]
– Can add [Pad] keyword for buffer pad nodes
– Support arbitrary power, package paths
– Support direct link to ICM

Parser enforces differences
IBIS Futures Task Group
4
Pros and Cons

Pros
– Focuses IBIS on value-add in
multi-lingual world
– Makes connections intuitive again
– Removes obstacles to advanced development

Cons
– Two-parsers-in-one required
– Dual-meaning of keywords depending on context
 e.g.,
[Pin] will have different rules for both modes
– Some “retooling” of passed BIRDs required
IBIS Futures Task Group
5