- pin_perst_n is a "power good" indicator from the associated power domain (to which R-tile is connected). Also, it shall qualify that both the R-tile refclk0 and refclk1 are stable. If one of the reference clocks becomes stable later, deassert pin_perst_n after this reference clock becomes stable.
- pin_perst_n assertion is required for proper Autonomous R-tile functionality. In Autonomous mode (enabled by default), R-tile can successfully link up upon the release of pin_perst_n regardless of the FPGA fabric configuration and will send out CRS (Configuration Retry Status) until the FPGA fabric is configured and ready.
- To prevent potential device degradation, the pin_perst_n signal must not be held active if power is supplied to the R-tile Avalon® Streaming Intel® FPGA IP for PCI Express when the FPGA is in user mode. If the R-tile Avalon® Streaming Intel® FPGA IP for PCI Express is planned to be used but not in the early phases of your design cycle, you must configure it in BTI mode using the following qsf asigment:
set_global_assignment -name PRESERVE_UNUSED_XCVR_CHANNEL ON
- pin_perst_n assertion should be avoided during a functional-level reset or before a functional-level reset is completed since this could impact the link training process. In case this occurs, a cold reset would be required to properly complete the link training process.
The following is an example where a single PERST# (pin_perst_n) is driven with independent refclk0 and refclk1. In this example, the add-in card (FPGA and Soc) is powered up first. R-tile refclk0 is fed by the on-board free-running oscillator. R-tile refclk1 driven by the Host becomes stable later. Hence, the PERST# is connected to the Host.
Did you find the information on this page useful?