SerialLite II IP Core User Guide

ID 683179
Date 7/13/2021
Public
Document Table of Contents

3.4. Multiple Core Configuration

When you instantiate multiple SerialLite II IP cores, you must apply additional guidelines to create a working design.
  • If you use the Tcl constraints to make assignments for the MegaCore functions, you must edit the Tcl script associated with each generated SerialLite II MegaCore function to update the hierarchical paths to each clock node and signal inside the TCL scripts. You can use the generated scripts as a guide. You must also make these changes to the generated Synopsys Design Constraints File (.sdc) if you intend to use the TimeQuest Timing Analyzer.
    Note: The Tcl scripts assume a top-level name for several clocks, such as: trefclk, rxrdp_clk, rxhpp_clk, txrdp_clk, and txhpp_clk. You must edit Set Clock Names in the scripts if the clock name connected to these inputs does not match. If the multiple cores are connected to the same clocks at the top-level file, you must make sure Set Clock Names and clock settings are only available in one script. You must always set to run this script first in the projects. You must edit the Tcl script and the .sdc file if you plan to use the TimeQuest timing analyzer.
  • For Arria II GX and Stratix IV designs, you must ensure that the cal_blk_clk input to each SerialLite II IP core is driven by the same calibration clock source. Also ensure that the SerialLite II IP core and other IP core variants in the system that use the ALTGX IP core have the same clock source connected to their respective cal_blk_clk ports.
  • In Arria II GX and Stratix IV designs that include multiple SerialLite II cores in a single transceiver block, the same signal must drive gxb_powerdown to each of the SerialLite II IP core variants.