GTS Dynamic Reconfiguration Controller IP User Guide: Agilex™ 5 FPGAs and SoCs
ID
849710
Date
8/11/2025
Public
1. Overview
2. Quick Start Guide
3. Configuring and Generating the IP
4. Integrating the GTS Dynamic Reconfiguration Controller IP With Your Application
5. Designing with the IP Core
6. Designing the IP Solution
7. Sharing Clocking and Applying SDC Constraints
8. Runtime Flow
9. Simulating the IP
10. Validating the IP
11. Appendix A: Functional Description
12. Registers
13. Document Revision History for the GTS Dynamic Reconfiguration Controller IP User Guide
3.1. Configuring the Quartus® Prime Pro Edition Project
3.2. Generating Dynamic Reconfiguration Design and Configuration Profiles
3.3. Generating HDL for Synthesis and Simulation
3.4. Using the Dynamic Reconfiguration Assignment Editor
3.5. Generating HSSI Dynamic Reconfiguration IP
3.6. Generating the Design Example
3.7. Compiling the Design Example
4.1. High-Level Interface Types
4.2. Dependent/Supporting IPs
4.3. Implementing Required Clocking
4.4. Implementing Required Resets
4.5. Implementing Required AVMM Interface
4.6. Control and Status Interface
4.7. Implementing Mux Selector Interface
4.8. Implementing SRC Interface
4.9. Implementing Local AVMM Interface
4.10. Connecting the Interfaces
4.11. Signal Functions
4.12. Integrating the IP With User Logic
4.13. Integrating the IP With Your Board
4.14. Integrating the IP on the Stack With a Software Driver
12.1.1. Register Next ID Configuration 0
12.1.2. Register Next ID Configuration 1
12.1.3. Register Next ID Configuration 2
12.1.4. Register Next ID Configuration 3
12.1.5. Register Next ID Configuration 4
12.1.6. Register Next ID Configuration 5
12.1.7. Register Next ID Configuration 6
12.1.8. Register Next ID Configuration 7
12.1.9. Register Next ID Configuration 8
12.1.10. Register Next ID Configuration 9
12.1.11. Register Next ID Configuration 10
12.1.12. Register Next ID Configuration 11
12.1.13. Register Next ID Configuration 12
12.1.14. Register Next ID Configuration 13
12.1.15. Register Next ID Configuration 14
12.1.16. Register Next ID Configuration 15
12.1.17. Register Next ID Configuration 16
12.1.18. Register Next ID Configuration 17
12.1.19. Register Next ID Configuration 18
12.1.20. Register Next ID Configuration 19
12.1.21. Register Trigger
12.1.22. Register Trigger Status
12.1.23. Register Error Configuration
12.1.24. Register Error Status
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/.
Note: The current release of GTS Dynamic Reconfiguration Example Designs does not support enabling internal loopback.
- 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_script.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 31. TCL Console