[ibis-macro] Re: IBIS AMI Specification Questions/Proposal
- From: "Ambrish Varma" <ambrishv@xxxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Mon, 24 Aug 2009 16:02:38 -0400
Hi All,
I feel there is some real confusion about "Values" and "Default".
Defaults, generally mean that if there is no value provided, the tool
will use the default value. In the spec, we have used the word Default
to specify the value for that model/simulation (particularly in the
reserved parameters section).
There is also confusion because we have defined the format for declaring
the parameters at 2 places for the reserved parameters (one with format,
one without).
Please refer to the attached document to see the changes that I am
proposing to the parameter section.
Thanks,
-Ambrish.
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, August 18, 2009 6:51 PM
To: IBIS-ATM
Subject: [ibis-macro] Re: IBIS AMI Specification Questions/Proposal
Bob,
Thanks for posting this summary of the problem.
I read trough the attached file and I am not sure what
the reasons are for these inconsistencies. In order to
make the right decisions, I feel we need to ask those
who wrote these portions of the AMI spec to find out
what was their intent. Authors, please speak up...
Thanks,
Arpad
========================================================
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Tuesday, August 18, 2009 5:11 PM
To: IBIS-ATM
Subject: [ibis-macro] IBIS AMI Specification Questions/Proposal
All:
This is being sent out per the issue raised at the Aug. 18
meeting concerning parser interpretation of the AMI Spec.
The ibischk5 parser with the -ami flag will check the
syntax of the <file name>.ami file. The attached document
shows several forms for <parameter_name> that are in the
specification. Some of the forms imply a restricted set of
parameters, but then this is contradicted by the example
at the end.
This implies that some parameters are really optional and
not excluded according to the syntaxes given.
The propposal is simply to make all parameters at least
optional, and some required according to a draft Table 4
that is NOT in the specification.
Do the choices in Table 4 look reasonable?
Bob
--
Bob Ross
Teraspeed Consulting Group LLC Teraspeed Labs
121 North River Drive 13610 SW Harness Lane
Narragansett, RI 02882 Beaverton, OR 97008
401-284-1827 503-430-1065
http://www.teraspeed.com 503-246-8048 Direct
bob@xxxxxxxxxxxxx
Teraspeed is a registered service mark of Teraspeed Consulting Group LLC
---------------------------------------------------------------------
IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/
IBIS Macro reflector: //www.freelists.org/list/ibis-macro
To unsubscribe send an email:
To: ibis-macro-request@xxxxxxxxxxxxx
Subject: unsubscribe
Instead of
| (parameter_name (Usage <usage>)(Type <data_type>)
| (Default <values>) (Description <string>))
on page 144 and
| (<parameter_name> (Usage <usage>)(Type <data_type>)
| (Format <data format>) (Default <values>)
| (Description <string>))
on page 145,
Just have
| (<parameter_name> (Usage <usage>)(Type <data_type>)
| (Format <data format>) (Value <values>)
| (Description <string>))
for the Required Parameters.
- Table 3 can be changed to include "Text" as format (for boolean type) and
Value is changed to "Number"
to remove ambiguity with the Value in parameter definition.
| +-------------------------------------------+
| | Data Format |
| =======================================================================
| | Reserved Parameter | N | R | C | L | I | S | G | D | D | T | T |
| | | U | a | o | i | n | t | a | u | j | a | E |
| | | M | n | r | s | c | e | u | a | R | b | X |
| | | B | g | n | t | r | p | s | l | j | l | T |
| | | E | e | e | | | s | | D | | e | |
| | | R | | r | | | | | i | | | |
| | | | | | | | | | r | | | |
| | | | | | | | | | a | | | |
| | | | | | | | | | c | | | |
| +-------------------------+---+---+---+---+---+---+---+---+---+---+---+
| | Init_Returns_Impulse | X |
| | GetWave_Exists | X |
| | Use_Init_Output | X |
| | Ignore_Bits | X |
| | Max_Init_Aggressors | X |
| | Tx_Jitter | X X X X |
| | Tx_DCD | X X X |
| | Rx_Receiver_Sensitivity | X X X |
| | Rx_Clock_PDF | X X X X |
| +-------------------------+-------------------------------------------+
| Table 3: Allowed Data Format for Reserved Parameters
- Default is not explicitly needed for Required parameters in the AMI file.
Those parameters that are not required, (refer to table 1)
the EDA tool will use the default to begin with. If the user wants to use a
value other than default, then they put
it in the .ami file.
- The new format allows the user a specific place to put their values for the
parameter. Ex:
(Init_Returns_Impulse (Usage Info)(Type Boolean)(Format Text)(Value
False)(Description "Any Text"))
(GetWave_Exists (Usage Info)(Type Boolean)(Format Text)(Value
True)(Description "Any Text"))
- Parameter 'Use_Init_Output' is optional - the default value used by the EDA
tool is True.
- Paramter 'Ignore_Bits' is optional - the default value used by the EDA tool
is 0.
If the user wants to enter a specific value for 'Ignore_Bits', it will be in
the following format:
(Ignore_Bits (Usage Info)(Type Integer)(Format
Number)(Value 200)(Description "Any Text"))
... etc.
- For Model Specific Parameters, the format should be:
| (<parameter_name> (Usage <usage>)(Type <data_type>)
| (Format <data format>) (Value <values>)
| (Default <values>) (Description <string>))
The example in the spec would become:
|=============================================================================
| Example of Parameter File
|=============================================================================
(mySampleAMI | Name given to the Parameter file
(Description "Sample AMI File")
(Reserved_Parameters | Required heading
(Ignore_Bits (Usage Info) (Type Integer) (Value 21)
(Description "Ignore 21 Bits"))
(Max_Init_Aggressors (Usage Info) (Type Integer)(Value 25))
(Init_Returns_Impulse (Usage Info) (Type Boolean)(Value True))
(GetWave_Exists (Usage Info) (Type Boolean) (Value True))
) | End Reserved_Parameters
(Model_Specific | Required heading
(txtaps
(-2 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -0.1 0.2)(Default
0.1)
(Description "Second Precursor Tap"))
(-1 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 0.2 -0.4
0.4)(Default 0.2)
(Description "First Precursor Tap"))
(0 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 1 -1 2)(Default 1)
(Description "Main Tap"))
(1 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 0.2 -0.4
0.4)(Default2 0.2)
(Description "First Post cursor Tap"))
(2 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 0.1 -0.1
0.2)(Default 0.1)
(Description "Second Post cursor Tap"))
) | End txtaps
(tx_freq_offset (Format Range) (Value 0.1 1 0 150) (Type UI) (Default 0))
) | End Model_Specific
)
Other related posts:
