[ibis-macro] Re: Comments on BIRD 150 (Dependency Table)
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "ibis-macro@xxxxxxxxxxxxx" <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 9 Oct 2012 18:30:59 +0000
Or do we want to talk about these in the ATM meeting?
Arpad
=======================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Walter Katz
Sent: Tuesday, October 09, 2012 1:29 PM
To: ambrishv@xxxxxxxxxxx; ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Re: Comments on BIRD 150 (Dependency Table)
Ambrish,
I think we should resolve these issues by e-mail this week. I do not have the
time before today's meeting to respond today.
Walter
From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]>
On Behalf Of Ambrish Varma
Sent: Tuesday, October 09, 2012 2:06 PM
To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] Comments on BIRD 150 (Dependency Table)
Hi Walter,
I was going through the dependency table BIRD (draft 3) and had a few
questions/comments:
1) Page 1: It is mentioned that "Dependency Tables are Model_Specific
parameters that are defined with format Table, and Usage Info. The parameter
name shall end in "Dependency_Table". " I believe that this is not true
anymore with the introduction of the new Usage(Dependency_Table).
2) Page 4: You say that "The values listed in the table for each Parameter
must be a legal Format for that Parameter based, and should, but is not
required, to be a legal value based on the definition of the Parameter in the
.ami file." Why can't we require it to be a legal value based on the definition
of the Parameter? If the definition of the parameter specifies the legal values
for the parameter, then those are what it should be set to. The EDA tool (via
the Dependency_Table)should not set it to an illegal value. Please let me know
if I am missing something.
3) Page4/5: In the example: Tx_Strength is type string with possible
values "0" "1" "2" "3" "4" "5" "6" "7" but in the dependency table, they are
treated as Ints.
4) Page 5: It is mentioned that "Dependency Tables support one or more
columns of input parameter data and one or more columns of output parameter
data." How is the combination of the 2 (or more input parameter data handled?
5) Page 5: Why are all the input column, except only the last, are
required to be an exact match to select the Output Parameters? In other words,
why is the last column treated differently? Can we get some examples for this
scenario please?
6) Do the output column types need to be the same in a Dependency Table?
7) Page 7: It is mentioned that "In AMI models Corner, shall be treated as
(Type String) and have values "Typ", "Min" and "Max", that can be used to
create an input column in a Dependency Table." So in other words, is Corner
treated as a Parameter - and somehow associated with the 'internal IBIS
parameter' ?
8) Page 8: What are intrinsic AMI parameters? What are 'bit_time', BAUD,
GBAUD and [Model]? There are no examples or explanations regarding these
parameters.
Besides these, we would prefer to have examples without reference to the
equivalent circuit analog mode parameters that are more generic and do not
confuse the reader.
Thanks,
Ambrish.
Cadence Design Systems.
Other related posts:
