[ibis-macro] Comments on BIRD 124
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: <ibis-macro@xxxxxxxxxxxxx>
- Date: Thu, 6 Jan 2011 12:42:12 -0800
I would like to comment on BIRD 124, the Dependency Table BIRD.
Pg. 140 of our existing specification says the following:
| Usage: (required for model specific parameters)
| In Parameter is required Input to executable
| Out Parameter is Output only from executable
| Info Information for user or EDA platform
| InOut Required Input to executable. Executable may return different
| value.
On the other hand, BIRD 124 describes the control parameters of
the Dependency Table as Usage In. These parameters, however, are
not passed into the AMI executable models (contrary to the rule
on pg. 140). This will create a contradiction or discrepancy in
the specification once BIRD 124 gets approved. The example in
BIRD 124 illustrates this:
| (Tx_Strength (Usage In)(Type String)
| (List "0" "1" "2" "3" "4" "5" "6" "7")
| (Description "Output buffer strength setting")
| )
|
| (Rs (Usage Info)(Type Float)
| (List 45.0 46.0 48.0 50.0 52.0 50.0 48.0 45.0)
| (Description "TX output impedance")
| )
|
| (Voh (Usage Info)(Type Float)
| (List 0.40 0.42 0.44 0.46 0.48 0.50 0.52 0.54)
| (Description "TX output voltage")
| )
|
| .
| .
| .
|
| (Tx_Strength_Table
| (Dependency
| (Parameter (Usage Info)(Type String)
| (List "Tx_Strength In" "Rs Out_Match" "Voh Out_Match"))
| (Row1 (List "0" "45.0" "0.40")(Usage Info)(Type String))
| (Row2 (List "1" "46.0" "0.42")(Usage Info)(Type String))
| (Row3 (List "2" "47.0" "0.44")(Usage Info)(Type String))
| (Row4 (List "3" "50.0" "0.46")(Usage Info)(Type String))
| (Row5 (List "4" "52.0" "0.48")(Usage Info)(Type String))
| (Row6 (List "5" "50.0" "0.50")(Usage Info)(Type String))
| (Row7 (List "6" "48.0" "0.52")(Usage Info)(Type String))
| (Row8 (List "7" '45.0" "0.54")(Usage Info)(Type String))
| )
| )
where Tx_Strength is Usage In but is not passed into the AMI executable
model.
I see two ways of fixing this problem. One would be to change the
words on pg. 140 about Usage and say something that In can be used
for other purposes than passing parameters into the executable
models. The other would be to find a different Usage name for the
Dependency Table control parameters.
I would prefer the second, because BIRD 122 as well as the Opal
document says that all the analog parameters must be of Usage Info.
If the analog parameters are Info (going to the tool) and the AMI
executable model parameters are Usage In (or InOut), I think the
Dependency Table control parameters should either be Info (since
they are processed by the tool interpreting the Dependency Table),
or we should come up with another distinct Usage type which is
strictly meant to be used for the Dependency Table.
Thanks,
Arpad
====================================================================
---------------------------------------------------------------------
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
Other related posts:
