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

ID 849710
Date 8/11/2025
Public
Document Table of Contents

10.3. Testing the Hardware Design Example for Ethernet to CPRI

The Ethernet to CPRI Dynamic Reconfiguration example design simulation testbench block diagrams are shown in the following figure:

Figure 32. Ethernet to CPRI Dynamic Reconfiguration Hardware Design Example Block Diagram
  • The DUT interface signals are driven by a set of test control registers, which are instantiated in the gts_dr_ed_csr module.
  • The tcl test program script main_script.tcl controls all aspects of the test sequence via thejtag_avmm connection.
  • The gts_dr_ed_shim module instantiates a set of test control registers that drive the DUT interface signals.
  • The main_script.tcl TCL test program script controls all aspects of the test sequence through the jtag_avmm module. The jtag_avmm module accesses the test CSR registers and DR control registers by decoding incoming addresses. Once the reset is released, the test script polls the status of the DR IP and test CSR registers, controlling the test sequence by writing to these registers. It checks the RX data comparison results before and after the DR process is completed.

The hardware design example executes the dynamic reconfiguration transition process based on user selection as stated in src/parameter.tcl file and checks the DUT IP status, There is a default dynamic reconfiguration transition sequence, but you can always modify the DR_TRANSITION array variable in src/parameter.tcl file to specify DR transitions of interest.

DR_TRANSITION: Intended DR sequence array, size of this array variable determines the number of dynamic reconfiguration to be performed. For example, if you want to achieve the following dynamic reconfiguration sequence for Ethernet base variant: CPRI > Ethernet the variables changes are:
set power_up_variant "4.9152G CPRI"
set DR_TRANSITION(0)   "10G ETH"
set DR_TRANSITION(1)   $power_up_variant