Arpad and All,
In response to your suggestion .
Here is a quick BIRD191_draft1 for review and vetting before submission.
There is a vote dependency, but we can easily handle this. Otherwise, we
would need to put this into BIRD189.x
Bob
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Monday, June 26, 2017 11:34 AM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: Unusual topic for Wednesday: BIRD161 vs.
BIRD189
Bob,
Good catch.
Although there is a close relationship between this and BIRD189, and there
may even be a
"vote dependency" between them, I would still prefer to write a separate
BIRD for this one.
Simply because I would not like to delay BIRD189 any longer, and there is a
danger that adding
this topic to BIRD189 might delay it.
Hopefully this probe location topic would be easy to approve, and this and
BIRD189 would
both end up in the next IBIS release.
Thanks,
Arpad
========================================================================
From: Bob Ross [mailto:bob@xxxxxxxxxxxxxxxxx] ;
Sent: Monday, June 26, 2017 12:19 PM
To: Muranyi, Arpad <Arpad_Muranyi@xxxxxxxxxx>; ibis-editorial@xxxxxxxxxxxxx
Subject: RE: [ibis-editorial] Re: Unusual topic for Wednesday: BIRD161 vs.
BIRD189
Arpad, All,
I agree that BIRD161.1 should be deferred and even stripped down. It has
some unrelated elements in it that could delay its resolution..
The immediate problem introduced by BIRD189.4 is that separate Buffer and
Pad interfaces are defined. That makes "Die" ambiguous because it has been
used to describe the buffer location. It can be used for the Pad location
(or "die pad" for on-die interconnects in BIRD189.4). The problem and
possible resolution is below:
Existing V6.1
Keyword: [Component]
Required: Yes
Description: Marks the beginning of the IBIS description of the
integrated circuit named after the keyword.
Sub-Params: Si_location, Timing_location
Usage Rules: If the .ibs file contains data for more than one component,
each section must begin with a new [Component] keyword. The length of the
component name must not exceed 40 characters, and blank characters are
allowed.
NOTE: Blank characters are not recommended due to usability issues.
Si_location and Timing_location are optional and specify where the Signal
Integrity and Timing measurements are made for the component. Allowed
values for either subparameter are "Die" or "Pin". The default location is
at the "Pin".
Example:
[Component] 7403398 MC452
|
Si_location Pin | Optional subparameters to give measurement
Timing_location Die | location positions
A proposed change in red:
Keyword: [Component]
Required: Yes
Description: Marks the beginning of the IBIS description of the
integrated circuit named after the keyword.
Sub-Params: Si_location, Timing_location
Usage Rules: If the .ibs file contains data for more than one component,
each section must begin with a new [Component] keyword. The length of the
component name must not exceed 40 characters, and blank characters are
allowed.
NOTE: Blank characters are not recommended due to usability issues.
Si_location and Timing_location are optional and specify where the Signal
Integrity and Timing measurements are made for the component. Allowed
values for either subparameter are "Buffer", "Die" or "Pin" to support three
possible locations available when connections are made using the
[Interconnect Model Set Selector] keyword below.. (The "Die" maps into Pad
or die pad locations.) The default location is at the "Pin". For pins
whose connections to the buffer do NOT use the [Interconnect Model Set
Selector] keyword, "Buffer" and "Die" describe the same location at the
buffer interface.
Example:
[Component] 7403398 MC452
|
Si_location Pin | Optional subparameters to give measurement
Timing_location Die | location positions
----------
The easiest option is to add this change in BIRD189.5 in response to a
technical comment on BIRD189.4.
An alternative is to issue a new BIRD to be included in V7.0,
Bob
Attachment:
BIRD191_draft1.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
