[ibis-macro] Re: Package modeling comparison

  • From: James Zhou <james.zhou@xxxxxxxxxx>
  • To: "wkatz@xxxxxxxxxx" <wkatz@xxxxxxxxxx>, IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
  • Date: Tue, 4 Sep 2012 11:15:20 -0700

Hi Walter,

Thanks for providing the example files. Here is a list of questions I have on 
the example files (there are many of them which may take some time to resolve).

package.emd
    (1) It refers to both pin and pad in "interconnect" section, however only 
pins are defined in "Pin" section. Should there also be a section to define 
"pads"?
    (2) "Pkg", "Tx" and "Rx" are instantiated using two different keywords of 
"Package_Model" and "Class". However, their syntax and most of the contents 
look exactly the same. What are the differences between them?
    (3) "Reference_Designator_Map" points to bare_die.ibsx file. There are no 
explicit mapping on pad names. Is the mapping implicit, requiring both files 
using the same pad names?
    (4) What is the difference between Tx and Tx_Coupled and, Rx and 
Rx_coupled? What are  the benefits of making such distinctions at model time?
    (5) can you please provide examples of pkg_typ.mod pkg_min.mod pkg_max.mod. 
What's the syntax of these mod files?

bare_die_ibsx:
    (1) Are sNp files allowed when N not equal 4 or 2?
    (2) Are "Buffer+ Buffer- Pad+ Pad-" reserved node names? What to do when N 
not equal 4 or 2?
    (3) Other than Tstonefile, we assume IBIS-ISS is also allowed, what is the 
syntax to hook it up?
    (4) possible typo in line 80, missing "Pad+":     (Tstonefile Ports Pad- 
Buffer+ Buffer-)

legacy.ibs
   (1) is it the intention to introduce keywords in comment lines for future 
standards (ibis 6.0)?

James Zhou



From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Walter Katz
Sent: Tuesday, September 04, 2012 8:24 AM
To: IBIS-ATM
Subject: [ibis-macro] Package modeling comparison

All,

Enclosed is a zip file containing a presentation and implementations of 
"legacy.ibs" in legacy IBIS format, using legacy IBIS files with parameter tree 
sections, splitting the IBIS file into an EMD file (parameter tree format) and 
a bare-die legacy file, and finally converting the bare-die legacy file into an 
IBISx file.

Mike L,

Can you post this please to the IBIS Reflector.

Walter



Walter Katz
wkatz@xxxxxxxxxx<mailto:wkatz@xxxxxxxxxx>
Phone 303.449-2308
Mobile 303.335-6156


________________________________
This message and any attached documents contain information from QLogic 
Corporation or its wholly-owned subsidiaries that may be confidential. If you 
are not the intended recipient, you may not read, copy, distribute, or use this 
information. If you have received this transmission in error, please notify the 
sender immediately by reply e-mail and then delete this message.

Other related posts: