GTS Dynamic Reconfiguration Controller IP User Guide: Agilex™ 5 FPGAs and SoCs

ID 849710
Date 4/18/2025
Public

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

Document Table of Contents

10.2.3. Running the Hardware Test

Follow these steps to test the hardware design example on the System Console:
  • The GTS Dynamically Reconfigurable Mode Design Example runs the external loopback test by default, with the loopback_mode parameter set to 0.
    • External Loopback: Before performing any hardware test, attach the QSFP28 loopback module according to the QSF pinout assignments of the respective design example.
    • Internal Loopback: To perform an internal loopback test in hardware, set the loopback_mode parameter to 1 in the parameter.tcl file located in <design_example_dir>/hardware_test_design/hwtest/src/.
  • The jtag_port_id parameter is set to 0 by default. To change the JTAG port ID to point to the correct Agilex™ 5 FPGA Master, modify the jtag_port_id parameter in the parameter.tcl file located in <design_example_dir>/hardware_test_design/hwtest/src/.
  • The dynamic reconfiguration transition sequence is set by default. However, you can change it by modifying the DR_TRANSITION array variable in the parameter.tcl file located in <design_example_dir>/hardware_test_design/hwtest/src/ to change the transition sequence.
  • For example, to achieve the these dynamic reconfiguration sequence for the 9.8304G Base Variant: 9.8304G > 4.9152G > 9.8304G > 4.9152G, the variable changes are:
    • Set DR_Transition(0) 4.9152G
    • Set DR_Transition(1) 9.8304G
    • Set DR_Transition(2) 4.9152G
  • Open Tools > System Debugging Tools > System Console or type the command:
    system-console &
  • In the TCL Console window, type cd hwtest to change directory to <design_example_dir>/hardware_test_design/hwtest.
  • Type source main_10G.tcl to open a connection to the JTAG master and start the test.
  • Verify that the output of the TCL script matches the output from a sample test run, shown below:
  • Analyze the results. Successful run displays Test Passed in the System Console.
    Figure 30. TCL Console