LS2160A Serdes Clocking

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LS2160A Serdes Clocking

111 Views
kiron
Contributor I

I'm using LX2160A SerDes1 with RCW SerDes Protocol 2:

Lanes E–H: SGMII
Lanes A–D: PCIe.2 x4 (Gen2 only)

From the Reference Manual, it appears all lanes use PLLS, so both SGMII and PCIe must share the same reference clock. I originally wanted to run SGMII at 125 MHz and PCIe at 100 MHz using separate fast/slow clock inputs, but since this specific protocol option puts both protocols on PLLS only, they must share one identical reference frequencyso now I plan to provide a single 100 MHz clock to the SD1 PLLS input and leave PLLF unused.


Is it possible to run Protocol 2 with a single 100 MHz PLLS reference for both SGMII and PCIe Gen1/Gen2, with no additional SerDes configuration beyond the RCW?
Are there any protocol-specific issues (jitter, SSC, etc.) when SGMII and PCIe share the same PLLS?
My SGMII link partner is a LAN9645 using its own local 125 MHz reference. Since SGMII uses CDR, is it normal for one side to be derived from 100 MHz and the other from 125 MHz, as long as both generate the correct 1.25 Gbaud line rate?
Since Protocol 2 doesn't use PLLF, can the SD1 fast reference clock input be left unconnected, or should it still be driven?

Tags (1)
0 Kudos
Reply
3 Replies

44 Views
yipingwang
NXP TechSupport
NXP TechSupport

Yes. For LX2160A SerDes1 Protocol 2, the initial PLL mapping is all PLLS: lanes H–E are SGMII and lanes D–A are PCIe.2 x4. If PCIe is limited to Gen1/Gen2 using SRDS_DIV_PEX_S1 = 0b10 or 0b11, a single fixed 100 MHz reference on SD1 PLLS is valid for both SGMII 1.25 Gbaud and PCIe Gen1/Gen2. No additional SerDes PLL reconfiguration is required beyond correct RCW settings.

Do not use spread-spectrum on this shared PLLS reference, because the Reference Manual states that when SSC is used for a PCIe SerDes reference clock, the same SerDes PLL must not be used concurrently for other protocols. Use a fixed, low-jitter 100 MHz clock.

It is normal for the SGMII peer to use its own local 125 MHz reference while the LX2160A derives SGMII from 100 MHz, because each SGMII receiver uses CDR and both sides only need to generate a compliant 1.25 Gbaud serial stream.

Since PLLF is not used in this Gen1/Gen2-only configuration, SD1_PLLF_REF_CLK may be left un-driven only if the RCW disables the PLLF reference clock and powers down PLLF. If Gen3 may ever be enabled, PLLF must be provided with a valid reference clock, because Protocol 2 switches PCIe lanes to PLLF at Gen3.

0 Kudos
Reply

37 Views
kiron
Contributor I
Does SGMII support 1.25G Baudrate or 2.5G Baudrate. Does 2.5G require a different clocking other than 100Mhz.
0 Kudos
Reply

35 Views
yipingwang
NXP TechSupport
NXP TechSupport

 1.25G Baudrate

Please refer to "26.1.7 Reference Clocks for SerDes Protocols" in LX2160A Reference Manual.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2389682%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ELS2160A%20Serdes%20Clocking%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2389682%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI'm%20using%20LX2160A%20SerDes1%20with%20RCW%20SerDes%20Protocol%202%3A%3C%2FP%3E%3CP%3ELanes%20E%E2%80%93H%3A%20SGMII%3CBR%20%2F%3ELanes%20A%E2%80%93D%3A%20PCIe.2%20x4%20(Gen2%20only)%3C%2FP%3E%3CP%3EFrom%20the%20Reference%20Manual%2C%20it%20appears%20all%20lanes%20use%20PLLS%2C%20so%20both%20SGMII%20and%20PCIe%20must%20share%20the%20same%20reference%20clock.%20I%20originally%20wanted%20to%20run%20SGMII%20at%20125%20MHz%20and%20PCIe%20at%20100%20MHz%20using%20separate%20fast%2Fslow%20clock%20inputs%2C%20but%20since%20this%20specific%20protocol%20option%20puts%20both%20protocols%20on%20PLLS%20only%2C%20they%20must%20share%20one%20identical%20reference%20frequencyso%20now%20I%20plan%20to%20provide%20a%20single%20100%20MHz%20clock%20to%20the%20SD1%20PLLS%20input%20and%20leave%20PLLF%20unused.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIs%20it%20possible%20to%20run%20Protocol%202%20with%20a%20single%20100%20MHz%20PLLS%20reference%20for%20both%20SGMII%20and%20PCIe%20Gen1%2FGen2%2C%20with%20no%20additional%20SerDes%20configuration%20beyond%20the%20RCW%3F%3CBR%20%2F%3EAre%20there%20any%20protocol-specific%20issues%20(jitter%2C%20SSC%2C%20etc.)%20when%20SGMII%20and%20PCIe%20share%20the%20same%20PLLS%3F%3CBR%20%2F%3EMy%20SGMII%20link%20partner%20is%20a%20LAN9645%20using%20its%20own%20local%20125%20MHz%20reference.%20Since%20SGMII%20uses%20CDR%2C%20is%20it%20normal%20for%20one%20side%20to%20be%20derived%20from%20100%20MHz%20and%20the%20other%20from%20125%20MHz%2C%20as%20long%20as%20both%20generate%20the%20correct%201.25%20Gbaud%20line%20rate%3F%3CBR%20%2F%3ESince%20Protocol%202%20doesn't%20use%20PLLF%2C%20can%20the%20SD1%20fast%20reference%20clock%20input%20be%20left%20unconnected%2C%20or%20should%20it%20still%20be%20driven%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2391405%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LS2160A%20Serdes%20Clocking%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2391405%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%3E%0A%3CP%3EYes.%20For%20LX2160A%20SerDes1%20Protocol%202%2C%20the%20initial%20PLL%20mapping%20is%20all%20PLLS%3A%20lanes%20H%E2%80%93E%20are%20SGMII%20and%20lanes%20D%E2%80%93A%20are%20PCIe.2%20x4.%20If%20PCIe%20is%20limited%20to%20Gen1%2FGen2%20using%20%3CCODE%3ESRDS_DIV_PEX_S1%20%3D%200b10%3C%2FCODE%3E%20or%20%3CCODE%3E0b11%3C%2FCODE%3E%2C%20a%20single%20fixed%20100%20MHz%20reference%20on%20SD1%20PLLS%20is%20valid%20for%20both%20SGMII%201.25%20Gbaud%20and%20PCIe%20Gen1%2FGen2.%20No%20additional%20SerDes%20PLL%20reconfiguration%20is%20required%20beyond%20correct%20RCW%20settings.%3C%2FP%3E%0A%3CP%3EDo%20not%20use%20spread-spectrum%20on%20this%20shared%20PLLS%20reference%2C%20because%20the%20Reference%20Manual%20states%20that%20when%20SSC%20is%20used%20for%20a%20PCIe%20SerDes%20reference%20clock%2C%20the%20same%20SerDes%20PLL%20must%20not%20be%20used%20concurrently%20for%20other%20protocols.%20Use%20a%20fixed%2C%20low-jitter%20100%20MHz%20clock.%3C%2FP%3E%0A%3CP%3EIt%20is%20normal%20for%20the%20SGMII%20peer%20to%20use%20its%20own%20local%20125%20MHz%20reference%20while%20the%20LX2160A%20derives%20SGMII%20from%20100%20MHz%2C%20because%20each%20SGMII%20receiver%20uses%20CDR%20and%20both%20sides%20only%20need%20to%20generate%20a%20compliant%201.25%20Gbaud%20serial%20stream.%3C%2FP%3E%0A%3CP%3ESince%20PLLF%20is%20not%20used%20in%20this%20Gen1%2FGen2-only%20configuration%2C%20SD1_PLLF_REF_CLK%20may%20be%20left%20un-driven%20only%20if%20the%20RCW%20disables%20the%20PLLF%20reference%20clock%20and%20powers%20down%20PLLF.%20If%20Gen3%20may%20ever%20be%20enabled%2C%20PLLF%20must%20be%20provided%20with%20a%20valid%20reference%20clock%2C%20because%20Protocol%202%20switches%20PCIe%20lanes%20to%20PLLF%20at%20Gen3.%3C%2FP%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2391537%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LS2160A%20Serdes%20Clocking%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2391537%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EDoes%20SGMII%20support%201.25G%20Baudrate%20or%202.5G%20Baudrate.%20Does%202.5G%20require%20a%20different%20clocking%20other%20than%20100Mhz.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2391560%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LS2160A%20Serdes%20Clocking%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2391560%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3E%26nbsp%3B1.25G%20Baudrate%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EPlease%20refer%20to%20%2226.1.7%20Reference%20Clocks%20for%20SerDes%20Protocols%22%20in%20LX2160A%20Reference%20Manual.%3C%2FP%3E%3C%2FLINGO-BODY%3E