High Bandwidth Memory (HBM2E) Interface Intel Agilex® 7 M-Series FPGA IP Design Example User Guide

ID 773266
Date 12/04/2023
Public

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

Document Table of Contents

2.5. Using the HBM2E Design Example with the Test Engine IP

  1. Click Tools > System Debugging Tools > System Console to open the System Console.
  2. Load the ed_synth.sof file into the System Console by clicking File > Load Design > ed_synth.sof. (Alternatively, you can load the .sof file from the terminal command line, if you prefer not to use the System Console.)
  3. After you have loaded the ed_synth.sof file, access the testengine_library.tcl file by entering the following command in the System Console:
    source hydra_sw/testengine_library.tcl
    
    You can see the test engine library loaded now. The testengine_library.tcl file includes the functions to interact with the test engine IP on hardware over a JTAG connection.
  4. Enter the following sequence of commands to check the driver status:
    1. To reset and program a new traffic pattern, type: testengine_reprogram
    2. To run the traffic, type: testengine_run
    3. To see the status of each driver included in the design, type: testengine_status
    For example, you should see the following output when you enabled all channels:
    Driver done: 16 / 16
    Driver pass: 16 / 16

The above steps run the default traffic pattern set in the traffic_pattern.py file. You can change or customize the traffic pattern if you want. When you modify or use a new traffic pattern, you must first regenerate the driver files. Use the following command to regenerate the driver files for the new program:

quartus_py hydra_sw/main.py --ipdir=<example_design_directory>/qii --prog=<name of your traffic pattern program>

The main advantage of the new test engine IP is that you don't need to recompile your entire design when you change or modify the traffic pattern. You must just regenerate the binary files. For additional information on test engine IP functions, refer to the testengine_library.tcl file.