[ibis-serdes-backchan] FW: [IBIS] Welcome to the IBIS AMI Backchannel Reflector

From: "Walter Katz" <wkatz@xxxxxxxxxx>
To: <ibis-serdes-backchan@xxxxxxxxxxxxx>
Date: Wed, 9 Feb 2011 08:57:56 -0500
 

Welcome to the IBIS AMI Backchannel Reflector. 

 

This e-mail was sent to IBIS mailing lists as well as Si-List as an
invitation to join the IBIS AMI Backchannel Reflector. I intend to follow
this up with three e-mails subjects:

1.      Is Backchannel an acceptable name.
2.      Introduction to AMI Modeling Statistical Analysis
3.      Introduction to AMI Modeling Time Domain Analysis

 

Walter

 

To subscribe:

 

The IBIS AMI Backchannel Reflector list is
<mailto:ibis-serdes-backchan@xxxxxxxxxxxxxx>
ibis-serdes-backchan@xxxxxxxxxxxxx

You must be subscribed to post to the list. To subscribe send email to

 

 <mailto:ibis-serdes-backchan-request@xxxxxxxxxxxxx>
ibis-serdes-backchan-request@xxxxxxxxxxxxx

with 'subscribe' in the Subject field

 

Or, subscribe online at
<//www.freelists.org/list/ibis-serdes-backchan>
//www.freelists.org/list/ibis-serdes-backchan

 

 

IBIS AMI Backchannel Reflector Overview

The IBIS AMI Backchannel Reflector is maintained by IBIS

Goal is to produce an IBIS BIRD that will

Enable Channel Standards Groups to define communication protocols between
the Tx and Rx DLLs.

Enable IC Vendors and AMI Model Developers to write IBIS AMI models that are

Portable               Model will work with multiple EDA Tools

Interoperable    Vendor A Tx will work with Vendor B Rx

Enable EDA Vendors to develop tools that will support AMI Backchannel models

 

 

Two presentations and lively discussion was had at the IBIS Summit at
DesignCon 2011. As a result of these presentations and discussions I will
shortly start several e-mail threads in the Backchannel Reflector. One
important issue brought up was the interface layer(s) that need to be
supported (i.e. does the Rx model communicate to the Tx model in commands
like "Increase Pre-Cursor tap by 3", and/or the actual  binary stream that
the Rx sends to the Tx.

 

The complete set of presentations at this year's IBIS Summit can be found at
<http://www.eda.org/ibis/summits/> http://www.eda.org/ibis/summits/

The two papers presented on SerDes Backchannel were:

 

AMI Backchannel Co-Optimization

Walter Katz

SiSoft 

 <http://www.eda.org/ibis/summits/feb11/katz2.pdf>
http://www.eda.org/ibis/summits/feb11/katz2.pdf

Extending IBIS-AMI to Support Back-Channel Communications

Kumar Keshavan

Sigrity

 <http://www.eda.org/ibis/summits/feb11/keshavan.pdf>
http://www.eda.org/ibis/summits/feb11/keshavan.pdf

 

Initial discussion topics for the reflector include:

 

1.       Shall we continue to call this "Backchannel"

2.       Review of AMI modeling, including statistical and time domain
methodologies.

3.       Confirm the mechanism that data is passed back and for the between
the Tx DLL, Rx DLL, and EDA Tool.

4.       Determine the generic format of the data passed back and for the
between the Tx DLL, Rx DLL, and EDA Tool.

5.       Determine Reserved Parameters that will be used to communicate
information between the EDA Tool and the Rx DLL, and between the EDA Tool
and the Tx DLL.

6.       Determine the interface layers that need to be supported.

7.       Determine the methodology that Channel Standards Groups (e.g. IEEE
Ethernet, PSIe-Gen3) define communication protocols between the Tx and Rx
DLLs.

8.       Consider forming Reflector subgroups that might wish to resolve
issues like the above without overloading the general membership of the
mailing list. Specifically do we need a IEEE Ethernet subgroup and a
PCIe-Gen3 subgroup.

 

Walter

 

Walter Katz

 <mailto:wkatz@xxxxxxxxxx> wkatz@xxxxxxxxxx

Phone 303.449-2308

Mobile 303.883-2120

 


-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean.
[ibis-serdes-backchan] FW: [IBIS] Welcome to the IBIS AMI Backchannel Reflector

Other related posts:
