[SI-LIST] PSXT exact definition of modes, for simulated SAS 3.0 (12Gbps) Compliance
- From: agathon <hreidmarkailen@xxxxxxxxx>
- To: tkjeon@xxxxxxxxxxx, si-list <si-list@xxxxxxxxxxxxx>
- Date: Fri, 22 Feb 2013 00:35:18 -0500
To follow up, for the new draft spec r05a, a question on the document's
meaning of "all modes" for PSXT...
The T10 sas3 r05a Draft is new and dated Jan 31, 2013.
In table 26 "Max Limits for S parameters of the passive TXRX connection"
it's stated as instruction for PSXT calculation:
"Determine all .... valid crosstalk transfer modes." in Note i.
My question: Is this intended to include Sdc(i,j) modes ? (besides the
obvious Sdd)
To be real picky about it, it doesn't even state victim differential
crosstalk.
Regards,
Agathon
On Tue, Aug 14, 2012 at 6:35 PM, T.K. Jeon <tkjeon@xxxxxxxxxxx> wrote:
> Although some parameters have not been settled yet, the wording of SAS3
> passive TxRx connection is shown in the SAS3 spec(Rev01 page 119) like
> following.
>
> "For external cable assemblies, these electrical requirements are
> consistent with using good quality passive Mini SAS HD cable assemblies
> constructed with shielded twinaxial cable with 24AWG solid wire up to 6m
> long, provided that no other TxRx connection segments are included in the
> TxRx connection and the total crosstalk is < 50mV (P-P)."
>
> Since SAS2 have used 10m iPass cable(24AWG) as a reference channel, I
> guess you can use 6m HD iPass cable as the SAS3 channel in addition to all
> FEXT/NEXT. The cable model could be obtained from either cable vendors or
> somewhere in t10.org.
>
> As for the jitter spec, the 12Gbps reference transmitter at the
> transmitter circuit should have 0.15UI(Max) and 0.1UI(Max) for RJ and DJ,
> respectively, according to Table 47 of the standard document.
>
> Best Regards,
> TK
>
> -----Original Message-----
> From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx]
> On Behalf Of Havermann, Gert
> Sent: Monday, August 13, 2012 11:33 PM
> To: SI LIST
> Subject: [SI-LIST] AW: Verifying SAS 3.0 (12Gbps) Compliance via Simulation
>
> Ed,
>
> I had the same problem a few weeks ago. Fortunately the SAS 3 spec is not
> updated in regards to the performance limits. The limits in the latest
> draft are still SAS2 limits. I used the IEEE KR limits as a reference and
> added some margin that will hopefully work for SAS3 once it is ready.
> For simulations you should always make at least two simulations, one
> without added Jitter, and one with Jitter (maybe even more simulations
> where only single Jitter types are added). This gives you the best
> understanding of the channel and helps optimizing and troubleshooting.
>
> BR
> Gert
>
>
> ----------------------------------------
> Absender ist HARTING Electronics GmbH & Co. KG; Sitz der Gesellschaft:
> Espelkamp; Registergericht: Bad Oeynhausen; Register-Nr.: HRA 5596;
> persönlich haftende Gesellschafterin: HARTING Electronics Management GmbH;
> Sitz der Komplementär-GmbH: Espelkamp; Registergericht der
> Komplementär-GmbH: Bad Oeynhausen; Register-Nr. der Komplementär-GmbH: HRB
> 8808; Geschäftsführer: Edgar-Peter Duening, Torsten Ratzmann, Dr. Alexander
> Rost
>
> -----Ursprüngliche Nachricht-----
> Von: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx]
> Im Auftrag von edward kowal
> Gesendet: Montag, 13. August 2012 20:24
> An: SI LIST
> Betreff: [SI-LIST] Verifying SAS 3.0 (12Gbps) Compliance via Simulation
>
> All,
> I am accustomed to looking at SERDES link performance in terms of required
> eye height and eye width, as well as jitter at some point in the signal
> path. Of course, there are also sometimes pure passive requirements such
> as IL/RL mask. For SAS 3.0, however, I cannot seem to find either
> criteria. Since it is a "closed eye" spec, there is no eye mask
> pre-DFE/CTLE. And all my vendor data sheet has where I expect to see the
> jitter requirements is a link to the SAS 3.0 spec annotated as "not
> available yet." Are there IL/RL masks for SAS 3.0?
> On a somewhat side note, if I run a simulation (HSPICE or IBIS-AMI) and I
> do not inject any jitter in the stimulus vector, should I be worrying about
> RJ, DJ, or TJ at the receiver? I remember I use to just add one of those
> numbers to the eye mask width and then could simply evaluate
> pass/fail/margin based on how much clear room there was around the widest
> parts of the mask.
> Sorry if this is a simple question I could have answered by going to the
> right resource, but I've been trying that and spinning my wheels.
> Ed
>
> ------------------------------------------------------------------
>
>
------------------------------------------------------------------
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
Other related posts:
- » [SI-LIST] PSXT exact definition of modes, for simulated SAS 3.0 (12Gbps) Compliance - agathon
