R-tile Avalon® Streaming Intel® FPGA IP for PCI Express* User Guide

ID 683501
Date 3/28/2022
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

4.5.5. PIPE Direct Speed Change

In the PIPE Direct Data mode, the clock for the RX datapath is sourced from the PHY recovered clock (pipe_direct_pld_rx_clk_out_o). The PHY recovered clock changes frequency when the PHY trains from Gen1 to Gen5. During the PIPE Direct RX rate change, the following sequence needs to be adhered to.

The soft IP controller first changes the rate or width if required. The R-tile Avalon Streaming IP only asserts lnX_pipe_direct_pclkchangeok_o after the Soft IP controller has made the changes. The Soft IP controller asserts lnX_pipe_direct_pclkchangeack_i when the change is complete and stable. After the Soft IP controller asserts lnX_pipe_direct_pclkchangeack_i, the R-tile Avalon Streaming IP responds by asserting lnX_pipe_direct_phystatus_o for one cycle and deasserting lnX_pipe_direct_pclkchangeok_o at the same time as lnX_pipe_direct_phystatus_o. The Soft IP controller deasserts lnX_pipe_direct_pclkchangeack_i when lnX_pipe_direct_pclkchangeok_o is sampled low.

As a reference, the following two timing diagrams illustrate the speed change from Gen1 to Gen5.
Note: Although the diagrams below illustrate a speed change from Gen1 to Gen5, the overall sequence applies to all speed changes. However, the final value of ln0_pipe_direct_rate_i in Step 1 varies depending on what the final speed is.
Figure 38. PIPE Direct Speed Change (Part 1)
Figure 39. PIPE Direct Speed Change (Part 2)
The steps shown in the diagrams are:
  1. The Soft IP controller changes the PIPE per-channel rate signal (ln0_pipe_direct_rate_i) to the IP from Gen1 to Gen5.
  2. The IP deasserts the PIPE RX reset status signal (ln_pipe_direct_reset_status_n_o) for each channel.
  3. The PIPE per-channel PCLK change OK and ACK signals (ln0_pipe_direct_pclkchangeok_o, ln0_pipe_direct_pclkchangeack_i) are asserted.
  4. The IP deasserts the PIPE per-channel RX CDR lock-to-reference signal (ln0_pipe_direct_cdrlockstatus_o).
  5. The IP sends the PIPE per-channel PHY status pulse (ln0_pipe_direct_phystatus_o) to the Soft IP controller. Also, the IP deasserts pclkchangeok (ln0_pipe_direct_pclkchangeok_o) and the Soft IP controller deasserts pclkchangeack (ln0_pipe_direct_pclkchangeack_i).
  6. The PIPE per-channel TX data (ln0_pipe_direct_txdata_i) transfer from the Soft IP controller to the IP begins (at Gen5 rate).
  7. The IP asserts the PIPE per-channel RX CDR lock-to-data signal (ln0_pipe_direct_cdrlock2data_o).
  8. The PIPE per-channel RX output clock (ln0_pipe_direct_pld_rx_clk_out_o) from the IP to the Soft IP controller becomes active.
  9. The PIPE per-channel RX data (ln0_pipe_direct_pipe_rxdata_o) transfer from the IP to the Soft IP controller begins (at Gen5 rate).

PIPE Direct TX Datapath and PIPE Direct RX Datapath provide an illustration of the PIPE Direct mode TX and RX datapath signals.

Figure 40. PIPE Direct TX Datapath
Note: At Gen1 and Gen2 speeds, only the 10 LSB bits from the lower segment of LnX_pipe_direct_txdata bus contain valid data. Bits [63:10] are don't-cares.
Figure 41. PIPE Direct RX Datapath
Note: At Gen1 and Gen2 speeds, only the 10 LSB bits in the upper and lower segments of the LnX_pipe_direct_rxdata_o bus contain valid data. Bits [31:10] and [63:42] are don't-cares.

Did you find the information on this page useful?

Characters remaining:

Feedback Message