Randy,
The IBIS-ATM Task Group voted today to submit your BIRD207_draft2.docx to the
IBIS Open Forum.
Please go ahead and submit it to become BIRD207.
Thanks,
Arpad
=============================================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] ;
On Behalf Of Randy Wolff
Sent: Tuesday, July 21, 2020 6:25 PM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] Re: [EXT] New AMI Reserved Parameters Component_Name and
Signal_Name
Here is the BIRD draft for review by email and in the 7/28 ATM meeting. Thanks
all for the feedback in today's meeting.
Randy
From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
<ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>> On
Behalf Of Randy Wolff
Sent: Monday, July 20, 2020 4:18 PM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>>
Subject: [ibis-macro] Re: [EXT] New AMI Reserved Parameters Component_Name and
Signal_Name
Attached is a BIRD draft for discussion in tomorrow's ATM meeting.
I defined an expected behavior by the EDA tool to pass in "NA" when the
Component name or signal_name are not available. Use of a default value needs
further discussion.
Thanks,
Randy
From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
<ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>> On
Behalf Of Randy Wolff
Sent: Monday, July 6, 2020 4:58 PM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>>
Subject: [EXT] [ibis-macro] New AMI Reserved Parameters Component_Name and
Signal_Name
All,
Here's a first pass at defining two new AMI Reserved Parameters to pass a
Component name and signal_name to the executable model. I used Model_Name as a
starting place. I allowed these for both Tx and Rx. I included a statement in
each to indicate that both parameters must be included if either is included.
The executable model will need both Component name and signal_name.
Are there any EDA tools where simulations could be performed at a Model level,
where no information about Component or signal_name would be available to pass
into these parameters? I think this situation could exist, and we may need to
define a default value (NA?) that would tell the executable model to use some
internal default.
Comments welcome.
Parameter: Component_Name
Required: No, and illegal before AMI_Version 7.1
Direction: Rx, Tx
Descriptors:
Usage: In
Type: String
Format: Value
Default: <string_literal>
Description: <string>
Definition: Name of the IBIS [Component] keyword that is being used.
Usage Rules: Value specified in the .ami file is ignored. The EDA tool must
pass the name of the IBIS [Component] keyword that is being instantiated by the
EDA tool through the input parameter strings to AMI_Resolve and AMI_Init
functions as the value of this parameter.
Component_Name must be present if Signal_Name is present. Component_Name must
be absent if Signal_Name is absent.
Other Notes:
Example:
(Component_Name (Usage In) (Type String) (Value "placeholder")
(Description "The name of the instantiated IBIS Component")
)
Parameter: Signal_Name
Required: No, and illegal before AMI_Version 7.1
Direction: Rx, Tx
Descriptors:
Usage: In
Type: String
Format: Value
Default: <string_literal>
Description: <string>
Definition: Name of the IBIS [Pin] keyword's signal_name sub-parameter
that is being used.
Usage Rules: Value specified in the .ami file is ignored. The EDA tool must
pass the name of the IBIS [Pin] keyword's signal_name sub-parameter that is
being instantiated by the EDA tool through the input parameter strings to
AMI_Resolve and AMI_Init functions as the value of this parameter.
Signal_Name must be present if Component_Name is present. Signal_Name must be
absent if Component_Name is absent.
Other Notes:
Example:
(Signal_Name (Usage In) (Type String) (Value "placeholder")
(Description "The name of the instantiated IBIS Pin's signal_name
sub-parameter")
)
Thanks,
Randy
