Hi Hung,
If you have HyperLynx it has compliance tests built into it for PCIe
channels, you will need the S-parameters of the full channel but it
sounds like you already have that. I think Mentor has a video on
their web site that shows how to run the compliance test for a PCIe
channel.
Best Regards,
Jeff Smith
GHz Systems Inc.
858-829-9702
----- Original Message -----
From: hndang@xxxxxxxxxxxxxxxxxxx
To:"si-list@xxxxxxxxxxxxx" <si-list@xxxxxxxxxxxxx>
Cc:
Sent:Sat, 12 May 2018 13:54:46 +0000
Subject:[SI-LIST] EYE mask for SerDes Simulation
Dear Experts,
I use SystemSI to run AMI-IBIS analysis for PCIE3.0 and SATA3.0.
I have concern about EYE mask to check the simulation results.
The channel is configured below:
PCIE_TX(AMI-IBIS model)--> Package --> Model board --> Cable and
Connector --> Backplane--> Connector (Probe Point)--> PCIE_RX(AMI-IBIS
model)
Per my understand, to determine PASS or FAIL result, It need the EYE
mask requirement at receiver. But I lack AMI-IBIS model at receiver
side.
I have replaced by AMI-IBIS model of our chip. The purpose is to make
termination for probe point.
Now, I can probe the EYE diagram before it's send to AMI-IBIS model.
My question is how to know the channel meet PCIE3.0 or SATA3.0
specification?
In the PCIE3.0 spec, the EYE mask requires 35mV EYE height and 0.3UI
EYE width. But signal is measured after it's processed by
CTLE/DFE/CDR.
In the SATA3.0 spec, I cannot find EYE mask requirement.
Thanks.
CONFIDENTIALITY NOTICE: This e-mail message, including any
attachments, is for the sole use of the intended recipient(s) and
contains information that is confidential and proprietary to Ampere
Computing or its subsidiaries. It is to be used solely for the purpose
of furthering the parties' business relationship. Any review, copying,
or distribution of this email (or any attachments thereto) is strictly
prohibited. If you are not the intended recipient, please contact the
sender immediately and permanently delete the original and any copies
of this email and any attachments thereto.
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
