- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
125MHz refclk for V5 PCIe Endpoint block plus?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-13-2011 01:37 AM
Is there any issue using 125MHz as ref clk for V5 (SXT) PCIe Endpoint Block Plus?
While the Core Gen only allows 100MHz or 250MHz, I think the clk can be changed to 125MHz by modifying pcie_gt_wrapper and pcie_clocking.
However, I wonder why the Core Gen does not want to support 125MHz. Is it because of practical issue like jitter exceeding PCIe spec?
Re: 125MHz refclk for V5 PCIe Endpoint block plus?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-13-2011 02:24 PM
Using 125 MHz or 250 MHz as the reference clock would improve the RX and TX performance of the design. The 100 MHz is the de-facto standard set by Intel and the PCISIG.
You will need to modify the attributes on the MGTs that are used by the PCIe core to support the change in the reference clock and maybe the pcie_clocking block (I haven't looked at the internal to know what is in it), but once this is done it should work fine.
If you are using a system that does not have the same clock used for both endpoints of the PCIE block you may run in to some interoperability issues if one of the endpoints doesn't have a reasonable size elastic buffer or doesn't support clock correction.
Have you tried typing your question into Google? If not you should before posting.
Too many results? Try adding site:www.xilinx.com
Re: 125MHz refclk for V5 PCIe Endpoint block plus?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-16-2011 03:57 AM
One furthering thing to add. After you make all these changes, I highly recommend a simulation. You'll save a lot of time and you'll be able to ensure your internal clock rates are correct.











