Article ID: 000074871 Content Type: Troubleshooting Last Reviewed: 08/13/2012

Why is received data getting corrupted when reconfiguring from a bonded mode using the ratematch block to a bonded mode not using the ratematch block?

Environment

  • Stratix® IV GT FPGA
  • Stratix® IV GX FPGA
  • HardCopy™ IV GX ASIC Devices
  • Arria® II GX FPGA
  • Arria® II GZ FPGA
BUILT IN - ARTICLE INTRO SECOND COMPONENT
Description

In bonded mode configurations that use the rate matcher block (PCIe or XAUI), coreclkout is used. However bonded mode configurations that do not use the rate match block require that each independent rx_clkout be used.

Quartus® II incorrectly continues to use coreclkout for the non rate matched configuration, hence data is corrupted.

Examples of un-supported dynamic reconfiguration modes include:

  • PCIe x4 <-> Basic mode without rate matcher.
  • Basic mode with rate matcher <-> Basic mode without rate matcher

Possible workarounds are:

  1. Ensure all reconfiguration modes use rate matching, then use coreclkout for all modes.
  2. If using XAUI, use the soft XAUI PCS, then independent rx_clkout can be used for each channel.

Examples of supported dynamic reconfiguration modes are:

  • PCIe x4 <-> XAUI x4
  • Basic mode with rate matcher <-> Basic mode with rate matcher
  • Basic mode without rate matcher <-> Basic mode without rate matcher

Disclaimer

1

All postings and use of the content on this site are subject to Intel.com Terms of Use.