[ibis-macro] Minutes from the 4 Jan 2011 ibis-atm meeting
- From: "Randy Wolff (rrwolff)" <rrwolff@xxxxxxxxxx>
- To: <ibis-macro@xxxxxxxxxxxxx>
- Date: Fri, 7 Jan 2011 14:04:36 -0700
Minutes from the January 4, 2011 IBIS ATM task group meeting are
attached.
Randy
IBIS Macromodel Task Group
Meeting date: 4 January 2011
Members (asterisk for those attending):
Agilent: Fangyi Rao
* Radek Biernacki
Ansoft: Chris Herrick
Danil Kirsanov
Ansys: * Samuel Mertens
* Dan Dvorscak
Deepak Ramaswamy
Jianhua Gu
Cadence Design Systems: Terry Jernberg
* Ambrish Varma
Celsionix: Kellee Crisafulli
Cisco Systems: Mike LaBonte
Stephen Scearce
Ashwin Vasudevan
Ericsson: Anders Ekholm
IBM: * Greg Edlund
Intel: * Michael Mirmak
LSI Logic: Wenyi Jin
Mentor Graphics: * John Angulo
Vladimir Dmitriev-Zdorov
Zhen Mu
* Arpad Muranyi
Micron Technology: * Randy Wolff
Nokia-Siemens Networks: * Eckhard Lenski
Sigrity: Brad Brim
Kumar Keshavan
* Ken Willis
SiSoft: * Walter Katz
Mike Steinberger
Todd Westerhoff
ST Micro: Syed Sadeghi
Teraspeed Consulting Group: Scott McMorrow
* Bob Ross
TI: * Casey Morrison
Alfred Chong
Vitesse Semiconductor: Eric Sweetman
Xilinx: Mustansir Fanaswalla
The meeting was lead by Arpad Muranyi
------------------------------------------------------------------------
Opens:
- Arpad said the next meeting would be Jan 11, 2011
--------------------------
Call for patent disclosure:
- none
-------------
Review of ARs:
-None
-------------
New Discussion:
Arpad showed the Typos_Format_Value_Default BIRD
- Bob: Page 10-11, noted comments don't seem to belong in the BIRD.
- Arpad: This is a reminder for final editors.
- Bob: Put this in the background info section.
- Bob: Page 2, "Value and Default are...", Default is a forward reference and
hasn't been defined yet. Seems to be defined well on page 3.
- Arpad: Prefers the language stay. Forward reference doesn't bother him.
- John: Likes Bob's suggestion to add "Default (defined below)"
- Bob: Noted some indentations that could be fixed
- Arpad: let's fix those in final editing
- Bob: Page 5, what does the language "The EDA tool must handle gracefully"
mean?
- Arpad: First line defines minimum requirements for the EDA tool.
- Walter: Thinks it is clear that you can't send it just anything. If you
send other parameter tree names that aren't In or InOut, then the DLL
should ignore them. He suggested Bob write up other language in an email.
- Bob: Would like the sentence removed.
- Arpad: There has been much email discussion on this. Bob, are you suggesting
more rigorous rules?
- Michael: Maybe add language to say that other types are permitted but may be
ignored.
- Bob: Cleanest rule is to say that other parameters must be defined in the
.ami file.
- Arpad: Continue this discussion on email.
- Bob: Confused by leaf and its interchangeability with parameter name. He will
write up his thoughts in an email.
- Bob: Bottom of page 7, the note seems inappropriate until we define the rules
of a Table.
- Walter: Thinks the note should be left in, because it clarifies the Table.
Arpad shared a presentation related to BIRDs 116-118.
- Arpad: This is an update to a presentation shared with the Open Forum already.
He noted Walter felt we should talk about BIRDs 116-118 before deciding
whether to vote down BIRD 122. He abandoned IBIS-ISS under [External
Circuit]
for AMI modeling due to non-support of parameter passing.
- Walter: Slide 4, box on right, D_drive for a Tx is single ended, what is
rise time of that stimulus?
- Arpad: D_drive is a digital signal that is converted to Analog with the
D_to_A converter that specifies rise time.
- Michael: Not all EDA tools have true digital signals, so implementation may
be non-ideal.
- Arpad: EDA tools should have methods to handle this.
- Arpad: On slide 5 is a circuit that could be used to generate an impulse
response. This could be handed to the AMI DLL for processing.
- Walter: When talking about [External Model]s, the input is not necessarily a
digital stimulus, the input may be the output of the Tx GetWave function.
The output is not necessarily a truly differential signal. For AMI, this
needs to be defined. The D_to_A converters are confusing.
- Michael: D_to_A and A_to_D were in the spec to account for cases where the
EDA tool needs to convert between truly digital signals to analog signals
and vice-versa.
- Arpad: Still need to clarify the boundary of the AMI model and the analog
model
to address Scott's comments.
- Arpad: Slide 6 shows how the A_to_D converter needs to be connected up
differently depending on use of a 2-port or 4-port analog Rx ISS model.
- Walter: How does the EDA tool know which nodes are the positive and negative
inputs on the Tx?
- Arpad: Requires looking at low and high levels of the my_drive* stimuli.
- Walter: Why don't we have a keyword to define the stimuli explicitly
without
the D_to_A converter?
- Arpad: Defined the BIRD to make minimum changes to the IBIS spec, but it
could be done other ways.
- Walter: Would prefer to have an [ISS Model] for use with AMI that has only
the information needed and removes the legacy [External Model] overhead.
It seems incompatible with ISS and AMI.
- Arpad: Will cleanup the BIRD a bit, and he encouraged Walter to write up
and
propose other ideas.
- Ambrish: Asked if Arpad could share S-parameter files used in his examples.
- Arpad: He hasn't completed them yet.
-------------
Next meeting: 11 Jan 2011 12:00pm PT
-------------
IBIS Interconnect SPICE Wish List:
1) Simulator directives
Other related posts:
