OFS Evaluation Quick Start Guide: Open FPGA Stack for Intel Stratix 10 FPGA
Glossary
| Term | Description |
|---|---|
| AER | Advanced Error Reporting, The PCIe AER driver is the extended PCI Express error reporting capability providing more robust error reporting. |
| AFU | Accelerator Functional Unit, Hardware Accelerator implemented in FPGA logic which offloads a computational operation for an application from the CPU to improve performance. Note: An AFU region is the part of the design where an AFU may reside. This AFU may or may not be a partial reconfiguration region |
| BBB | Basic Building Block, Features within an AFU or part of an FPGA interface that can be reused across designs. These building blocks do not have stringent interface requirements like the FIM's AFU and host interface requires. All BBBs must have a (globally unique identifier) GUID. |
| BKC | Best Known Configuration, The exact hardware configuration Intel has optimized and validated the solution against. |
| BMC | Board Management Controller, Acts as the Root of Trust (RoT) on the Intel FPGA PAC platform. Supports features such as power sequence management and board monitoring through on-board sensors. |
| CSR | Command/status registers (CSR) and software interface, OFS uses a defined set of CSR's to expose the functionality of the FPGA to the host software. |
| DFL | Device Feature List, A concept inherited from OFS. The DFL drivers provide support for FPGA devices that are designed to support the Device Feature List. The DFL, which is implemented in RTL, consists of a self-describing data structure in PCI BAR space that allows the DFL driver to automatically load the drivers required for a given FPGA configuration. |
| FIM | FPGA Interface Manager, Provides platform management, functionality, clocks, resets and standard interfaces to host and AFUs. The FIM resides in the static region of the FPGA and contains the FPGA Management Engine (FME) and I/O ring. |
| FME | FPGA Management Engine, Provides a way to manage the platform and enable acceleration functions on the platform. |
| HEM | Host Exerciser Module, Host exercisers are used to exercise and characterize the various host-FPGA interactions, including Memory Mapped Input/Output (MMIO), data transfer from host to FPGA, PR, host to FPGA memory, etc. |
| Intel FPGA PAC D5005 | Intel FPGA Programmable Acceleration Card D5005, A high performance PCI Express (PCIe)-based FPGA acceleration card for data centers. This card is the target platform for the initial OFS release. |
| Intel VT-d | Intel Virtualization Technology for Directed I/O, Extension of the VT-x and VT-I processor virtualization technologies which adds new support for I/O device virtualization. |
| IOCTL | Input/Output Control, System calls used to manipulate underlying device parameters of special files. |
| JTAG | Joint Test Action Group, Refers to the IEEE 1149.1 JTAG standard; Another FPGA configuration methodology. |
| MMIO | Memory Mapped Input/Output, Users may map and access both control registers and system memory buffers with accelerators. |
| OFS | Open FPGA Stack, A modular collection of hardware platform components, open source software, and broad ecosystem support that provides a standard and scalable model for AFU and software developers to optimize and reuse their designs. |
| OPAE SDK | Open Programmable Acceleration Engine Software Development Kit, A collection of libraries and tools to facilitate the development of software applications and accelerators using OPAE. |
| PAC | Programmable Acceleration Card: FPGA based Accelerator card |
| PIM | Platform Interface Manager, An interface manager that comprises two components: a configurable platform specific interface for board developers and a collection of shims that AFU developers can use to handle clock crossing, response sorting, buffering and different protocols. |
| PR | Partial Reconfiguration, The ability to dynamically reconfigure a portion of an FPGA while the remaining FPGA design continues to function. In the context of Intel FPGA PAC, a PR bitstream refers to an Intel FPGA PAC AFU. Refer to Partial Reconfiguration support page. |
| RSU | Remote System Update, A Remote System Update operation sends an instruction to the Intel FPGA PAC D5005 device that triggers a power cycle of the card only, forcing reconfiguration. |
| SR-IOV | Single-Root Input-Output Virtualization, Allows the isolation of PCI Express resources for manageability and performance. |
| TB | Testbench, Testbench or Verification Environment is used to check the functional correctness of the Design Under Test (DUT) by generating and driving a predefined input sequence to a design, capturing the design output and comparing with-respect-to expected output. |
| UVM | Universal Verification Methodology, A modular, reusable, and scalable testbench structure via an API framework. |
| VFIO | Virtual Function Input/Output, An IOMMU/device agnostic framework for exposing direct device access to userspace. |
1 Overview
1.1 About this Document
This document serves as a set-up and user guide for the checkout and evaluation of an Intel® FPGA PAC D5005 development at form using Open FPGA Stack (OFS). After reviewing the document, you will be able to:
-
Set-up and modify the script to the your environment
-
Compile and simulate an OFS reference design
-
Run hardware and software tests to evaluate the complete OFS flow
1.2 Table : Software Version Summary
| Component | Version | Description |
|---|---|---|
| FPGA Platform | Intel® FPGA PAC D5005 | Intel platform you can use for your custom board development |
| OFS FIM Source Code | Branch: ofs-d5005, Tag: release/1.0.x | OFS Shell RTL for Intel Stratix 10 FPGA (targeting Intel® FPGA PAC D5005) |
| OFS FIM Common | Branch: ofs-fim-common-1.1.0-rc2, Tag: ofs-fim-common-1.1.0-rc2 | Common RTL across all OFS-based platforms |
| AFU Examples | Branch: examples-afu , Tag:ofs-examples-ofs-examples-afu-1.0.0-rc3 | Tutorials and simple examples for the Accelerator Functional Unit region (workload region) |
| OFS Platform Building Blocks | Branch: ofs-platform-bbb,Tag: 1.0.0-rc3 | Provides bridge interfaces for protocol translation |
| OPAE SDK | Branch: 2.3.0-1, Tag: 2.3.0-1 | Open Programmable Acceleration Engine Software Development Kit |
| Kernel Drivers | Branch: ofs-2022.3-2, Tag: ofs-2022.3-2 | OFS specific kernel drivers |
| OPAE Simulation | Branch: opae-sim, Tag: 2.3.0-1 | Accelerator Simulation Environment for hardware/software co-simulation of your AFU (workload) |
| Intel Quartus Prime Pro Edition Design Software | 22.3 Intel® Quartus® Prime Pro Edition Linux | Software tool for Intel FPGA Development |
| Operating System | RHEL 8.2 | Operating system on which this script has been tested. |
A download page containing the release and already-compiled FIM binary artifacts that you can use for immediate evaluation on the Intel® FPGA PAC D5005 can be found on the OFS 2022.3 official release drop on GitHub.
2 Introduction to OFS Evaluation Script
By following the setup steps and using the OFS evaluation script you can quickly evaluate many features that the OFS framework provides and also leverage this script for your own development.
2.1 Pre-Requisites
This script uses on the following set of software tools which should be installed using the directory structure below. Tool versions can vary.
- Intel Quartus® Prime Pro Software
- Synopsys® VCS Simulator
- Siemens® Questa® Simulator
Figure 2-1 Folder Hierarchy for Software Tools
-
You must create a directory named "ofs-X.X.X" where the X represents the current release number, for example ofs-d5005-1.0.1.
-
You must clone the required OFS repositories as per Figure 2-2 . Please refer to the BKC table for locations., Please go OFS Getting Started User Guide for the instructions for the BKC installation.
-
Assign the ofs-X.X.X folder to the $OFS_BUILD_ROOT environment variable.
-
Once the repositories are cloned, copy the evaluation script (ofs_d5005_eval.sh) which is located at evaluation script beneath the $OFS_BUILD_ROOT directory location as shown in the example below:
Figure 2-2 Directory Structure for OFS Project
## ofs-ofs-d5005-1.0.1
## -> examples-afu
## -> linux-dfl
## -> fim-d5005
## -> opae-sdk
## -> opae-sim
## -> ofs_d5005_eval.sh
- Open the README file named (README_ofs_d5005_eval.txt) which is located at evaluation script which informs the user which sections to modify in the script prior to building the FIM and running hardware, software and simulation tests.
2.2 d5005 Evaluation Script modification
To adapt this script to the user environment please follow the instructions below which explains which line numbers to change in the ofs_d5005_eval.sh script.
User Directory Creation
The user must create the top-level source directory and then clone the OFS repositories
mkdir ofs
In the example above we have used ofs as the directory name
Set-Up Proxy Server (lines 61-63)
Please enter the location of your proxy server to allow access to external internet to build software packages.
Note: Failing to add proxy server will prevent cloning of repositories and the user will be unable to build the OFS framework.
export http_proxy=<user_proxy>
export https_proxy=<user_proxy>
export no_proxy=<user_proxy>
License Files (lines 66-68)
Please enter the the license file locations for the following tool variables
export LM_LICENSE_FILE=<user_license>
export DW_LICENSE_FILE=<user_license>
export SNPSLMD_LICENSE_FILE=<user_license>
Tools Location (line 82)
Set Location of Quartus, Synopsys and Questasim Tools
export TOOLS_LOCATION=/home
In the example above /home is used as the base location of Quartus, Synopsys and Questasim tools
Quartus Tools Version (line 87)
Set version of Quartus
export QUARTUS_VERSION=${{ env.5005_QUARTUS_PRIME_PRO_VER }}
In the example above "${{ env.5005_QUARTUS_PRIME_PRO_VER }}" is used as the Quartus tools version
OPAE Tools (line 100)
change OPAE SDK VERSION
export OPAE_SDK_VERSION=${{ env.5005_D5005_OPAE_VER }}
In the example above "${{ env.5005_D5005_OPAE_VER }}" is used as the OPAE SDK tools version
PCIe (Bus Number) (lines 223 and 230)
The Bus number must be entered by the user after installing the hardware in the chosen server, in the example below "b1" is the Bus Number for a single card as defined in the evaluation script.
export ADP_CARD0_BUS_NUMBER=b1
The evaluation script uses the bus number as an identifier to interrogate the card. The command below will identify the accelerator card plugged into a server.
lspci | grep acc
86:00.0 Processing accelerators: Intel Corporation Device bcce (rev 01)
The result identifies the card as being assigned "86" as the bus number so the entry in the script changes to
export ADP_CARD0_BUS_NUMBER=86
The user can also run the following command on the ofs_d5005_eval.sh script to automatically change the bus number to 86 in the ofs_d5005_eval.sh script.
grep -rli '86' * | xargs -i@ sed -i '86' @
if the bus number is 85 for example
85:00.0 Processing accelerators: Intel Corporation Device bcce (rev 01)
the command to change to 85 in the evaluation script would be
grep -rli '86' * | xargs -i@ sed -i '85' @
The ofs_d5005_eval.sh script has now been modified to the server set-up and the user can proceed to build, compile and simulate the OFS stack
3 Using the Evaluation Script
3.1 Overview
The evaluation script focuses on different evaluation areas. Each of these menu options are described in the next section. Note that some option selection numbers are not available currently. As new features are added additional selections will be added.
3.1.1 TOOLS MENU
By selecting "List of Documentation for ADP d5005 Project," a list of links to the latest OFS documentation appears. Note that these links will take you to documentation for the most recent release which may not correspond to the release version you are evaluating. To find the documentation specific to your release, ensure you clone the intel-ofs-docs tag that corresponds to your OFS version.
By selecting "Check Versions of Operating System and Quartus Premier Design Suite", the tool verifies correct Operating System, Quartus version, kernel parameters, license files and paths to installed software tools.
| Menu Option | Example Output |
|---|---|
| 1 - List of Documentation for ADP d5005 Project | Getting Started Guide: Intel Open FPGA Stack for Intel Stratix 10 FPGA Guides you through the setup and build steps to evaluate the OFS solution targeting an Intel® FPGA PAC D5005 FPGA Interface Manager Technical Reference Manual: Intel Open FPGA Stack for Intel Stratix 10 FPGA Describes the OFS FIM architecture and features Software Reference Manual: Intel® Open FPGA Stack Describes the Open Programmable Acceleration Engine (OPAE) Software Development Kit, the OPAE C++ and Python API and management interfaces. This document also covers building the OPAE SDK, how to add a new PCIe device, and debugging the software stack FPGA Interface Manager Developer Guide: Intel Open Stack for Intel Stratix 10 FPGA Provides guidance on developing an FPGA Interface Manager (FIM) for a custom FPGA acceleration board Accelerator Functional Unit Developer Guide: Intel Open FPGA Stack Provides guidance on how to build and test an AFU when designing to an OFS-based FPGA Interface Manager Security User Guide: Intel Open FPGA Stack for Intel Stratix 10 FPGA Describes how to create keys and sign bitstreams for your custom design |
| 2 - Check versions of Operating System and Quartus Premier Design Suite (QPDS) | Checking Linux release Linux version 5.15.77-dfl-20${{ env.5005_QUARTUS_PRIME_PRO_VER }}-1 (DCPsupport@sj-2308-a405.sj.intel.com) (gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-15), GNU ld version 2.30-73.el8) #1 SMP Thu Dec 8 10:21:38 PST 2022 Checking RedHat release Red Hat Enterprise Linux release 8.2 Checking Ubuntu release cat: /etc/lsb-release: No such file or directory Checking Kernel parameters BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.15.77-dfl-20${{ env.5005_QUARTUS_PRIME_PRO_VER }}-1 root=/dev/mapper/rhel-root ro crashkernel=auto resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet intel_iommu=on pcie=realloc hugepagesz=2M hugepages=200 Checking Licenses LM_LICENSE_FILE is set to port@socket number:port@socket number DW_LICENSE_FILE is set to port@socket number:port@socket number SNPSLMD_LICENSE_FILE is set to port@socket number:port@socket number Checking Tool versions QUARTUS_HOME is set to /home/intelFPGA_pro/${{ env.5005_QUARTUS_PRIME_PRO_VER }}/quartus QUARTUS_ROOTDIR is set to /home/intelFPGA_pro/${{ env.5005_QUARTUS_PRIME_PRO_VER }}/quartus IMPORT_IP_ROOTDIR is set to /home/intelFPGA_pro/${{ env.5005_QUARTUS_PRIME_PRO_VER }}/quartus/../ip QSYS_ROOTDIR is set to /home/intelFPGA_pro/${{ env.5005_QUARTUS_PRIME_PRO_VER }}/quartus/../qsys/bin Checking QPDS Patches Quartus Prime Shell Version ${{ env.5005_QUARTUS_PRIME_PRO_VER }}.0 Build 104 09/14/2022 SC Pro Edition Copyright (C) 2022 Intel Corporation. All rights reserved. |
3.1.2 HARDWARE MENU
Identifies card by PCIe number, checks power, temperature and current firmware configuration.
| Menu Option | Example Output |
|---|---|
| 3 - Identify Acceleration Development Platform (ADP) d5005 Hardware via PCIe | PCIe card detected as 86:00.0 Processing accelerators: Intel Corporation Device bcce (rev 01) Host Server is connected to SINGLE card configuration |
| 4 - Identify the Board Management Controller (BMC) Version and check BMC sensors | Intel FPGA Programmable Acceleration Card D5005 Board Management Controller, MAX10 NIOS FW version: 2.0.13 Board Management Controller, MAX10 Build version: 2.0.8 //****** BMC SENSORS ******// Object Id : 0xF000000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 Ports Num : 01 Bitstream Id : 0x4010002278FD3AA Bitstream Version : 4.0.1 Pr Interface Id : 64c39726-fe2d-52ab-981f-ff49395db6e7 |
| 5 - Identify the FPGA Management Engine (FME) Version | Intel FPGA Programmable Acceleration Card D5005 Board Management Controller, MAX10 NIOS FW version: 2.0.13 Board Management Controller, MAX10 Build version: 2.0.8 //****** FME ******// Object Id : 0xF000000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 Ports Num : 01 Bitstream Id : 0x4010002278FD3AA Bitstream Version : 4.0.1 Pr Interface Id : 64c39726-fe2d-52ab-981f-ff49395db6e7 Boot Page : user |
| 6 - Check Board Power and Temperature | Intel FPGA Programmable Acceleration Card D5005 Board Management Controller, MAX10 NIOS FW version: 2.0.13 Board Management Controller, MAX10 Build version: 2.0.8 //****** POWER ******// Object Id : 0xF000000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 Ports Num : 01 Bitstream Id : 0x4010002278FD3AA Bitstream Version : 4.0.1 Pr Interface Id : 64c39726-fe2d-52ab-981f-ff49395db6e7 ( 1) VCCERAM Voltage : 0.90 Volts etc ...................... Intel FPGA Programmable Acceleration Card D5005 Board Management Controller, MAX10 NIOS FW version: 2.0.13 Board Management Controller, MAX10 Build version: 2.0.8 //****** TEMP ******// Object Id : 0xF000000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 Ports Num : 01 Bitstream Id : 0x4010002278FD3AA Bitstream Version : 4.0.1 Pr Interface Id : 64c39726-fe2d-52ab-981f-ff49395db6e7 ( 1) VCCT Temperature : 57.00 Celsius etc ...................... |
| 7 - Check Accelerator Port status | //****** PORT ******//
Object Id : 0xEF00000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 |
| 8 - Check MAC and PHY status | Intel FPGA Programmable Acceleration Card D5005 Board Management Controller, MAX10 NIOS FW version: 2.0.13 Board Management Controller, MAX10 Build version: 2.0.8 //****** MAC ******// Object Id : 0xF000000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 Ports Num : 01 Bitstream Id : 0x4010002278FD3AA Bitstream Version : 4.0.1 Pr Interface Id : 64c39726-fe2d-52ab-981f-ff49395db6e7 MAC address : 64:4c:36:f:44:1f Intel FPGA Programmable Acceleration Card D5005 Board Management Controller, MAX10 NIOS FW version: 2.0.13 Board Management Controller, MAX10 Build version: 2.0.8 //****** PHY ******// Object Id : 0xF000000 PCIe s:b:d.f : 0000:86:00.0 Vendor Id : 0x8086 Device Id : 0xBCCE SubVendor Id : 0x8086 SubDevice Id : 0x138D Socket Id : 0x00 Ports Num : 01 Bitstream Id : 0x4010002278FD3AA Bitstream Version : 4.0.1 Pr Interface Id : 64c39726-fe2d-52ab-981f-ff49395db6e7 |
3.1.3 FIM/PR BUILD MENU
Builds FIM, Partial Reconfiguration Region and Remote Signal Tap
| Menu Option | Description |
|---|---|
| 9 - Check ADP software versions for ADP d5005 Project | OFS_ROOTDIR is set to /home/DCPsupport/ofs-d5005-1.0.1/ofs-d5005 OPAE_SDK_REPO_BRANCH is set to release/${{ env.5005_D5005_OPAE_VER }} OPAE_SDK_ROOT is set to /home/DCPsupport/ofs-d5005-1.0.1/ofs-d5005/../opae-sdk LD_LIBRARY_PATH is set to /home/DCPsupport/ofs-d5005-1.0.1/ofs-d5005/../opae-sdk/lib64: |
| 10 - Build FIM for d5005 Hardware | This option builds the FIM based on the setting for the $ADP_PLATFORM, $FIM_SKU1 or $FIM_SKU2 environment variable. Check these variables in the following file ofs_d5005_eval.sh |
| 11 - Check FIM Identification of FIM for d5005 Hardware | The FIM is identified by the following file fme-ifc-id.txt located at $OFS_ROOTDIR/$FIM_WORKDIR/syn/syn_top/ |
| 12 - Build Partial Reconfiguration Tree for d5005 Hardware | This option builds the Partial Reconfiguration Tree which is needed for AFU testing/development and also for the OneAPI build flow |
| 13 - Build Base FIM Identification(ID) into PR Build Tree template | This option copies the contents of the fme-ifc-id.txt into the Partial Reconfiguration Tree to allow the FIM amd Partial Reconfiguration Tree to match and hence allow subsequent insertion of AFU and OneAPI workloads |
| 14 - Build Partial Reconfiguration Tree for d5005 Hardware with Remote Signal Tap | This option builds the Partial Reconfiguration Tree which is needed for AFU testing/development and also for the OneAPI build flow and for the Remote Signal Tap flow |
| 15 - Build Base FIM Identification(ID) into PR Build Tree template with Remote Signal Tap | This option copies the contents of the fme-ifc-id.txt into the Partial Reconfiguration Tree for Remote Signal Tap to allow the FIM amd Partial Reconfiguration Tree to match and hence allow subsequent insertion of AFU and OneAPI workloads |
3.1.4 HARDWARE PROGRAMMING/DIAGNOSTIC MENU
The following submenu allows you to: * Program and check flash * Perform a remote system update (RSU) of the FPGA image into the FPGA * Bind virtual functions to VFIO PCIe driver * Run host exerciser (HE) commands such as loopback to test interfaces VFIO PCI driver binding * Read the control and status registers (CSRs) for bound modules that are part of the OFS reference design.
| Menu Option | Description |
|---|---|
| 16 - Program BMC Image into d5005 Hardware | The user must place a new BMC flash file in the following directory $OFS_ROOTDIR/bmc_flash_files. Once the user executes this option a new BMC image will be programmed. A remote system upgrade command is initiated to store the new BMC image |
| 17 - Check Boot Area Flash Image from d5005 Hardware | This option checks which location area in FLASH the image will boot from, the default is user1 Boot Page : user1 |
| 18 - Program FIM Image into user1 area for d5005 Hardware | This option programs the FIM image "d5005_page1.bin" into user1 area in flash |
| 19 - Initiate Remote System Upgrade (RSU) from user1 Flash Image into d5005 Hardware | This option initiates a Remote System Upgrade and soft reboots the server and re-scans the PCIe bus for the new image to be loaded 2022-12-13 07:31:33,244 - [[pci_address(0000:86:00.0), pci_id(0x8086, 0xbcce, 0x8086, 0x138d)]] performing RSU operation 2022-12-13 07:31:33,249 - [[pci_address(0000:85:00.0), pci_id(0x8086, 0x2030, 0x1590, 0x00ea)]] removing device from PCIe bus 2022-12-13 07:31:34,333 - waiting 10.0 seconds for boot 2022-12-13 07:31:44,344 - rescanning PCIe bus: /sys/devices/pci0000:85/pci_bus/0000:85 2022-12-13 07:31:44,377 - RSU operation complete |
| 20 - Check PF/VF Mapping Table, vfio-pci driver binding and accelerator port status | This option checks the current vfio-pci driver binding for the PF's and VF's |
| 21 - Unbind vfio-pci driver | This option unbinds the vfio-pci driver for the PF's and VF's |
| 22 - Create Virtual Functions (VF) and bind driver to vfio-pci d5005 Hardware | This option creates vfio-pci driver binding for the PF's and VF's Once the VF's have been bound to the driver the user can select menu option 20 to check that the new drivers are bound |
| 23 - Run HE-LB Test | This option runs 5 tests 1) checks and generates traffic with the intention of exercising the path from the AFU to the Host at full bandwidth 2) run a loopback throughput test using one cacheline per request 3) run a loopback read test using four cachelines per request 4) run a loopback write test using four cachelines per request 5) run a loopback throughput test using four cachelines per request |
| 24 - Run HE-MEM Test | This option runs 2 tests 1) Checking and generating traffic with the intention of exercising the path from FPGA connected DDR; data read from the host is written to DDR, and the same data is read from DDR before sending it back to the host 2) run a loopback throughput test using one cacheline per request |
| 25 - Run HE-HSSI Test | This option runs 1 test HE-HSSI is responsible for handling client-side ethernet traffic. It wraps the 10G and 100G HSSI AFUs, and includes a traffic generator and checker. The user-space tool hssi exports a control interface to the HE-HSSI's AFU's packet generator logic 1) Send traffic through the 10G AFU |
| 26 - Read from CSR (Command and Status Registers) for d5005 Hardware | This option reads from the following CSR's HE-LB Command and Status Register Default Definitions HE-MEM Command and Status Register Default Definitions HE-HSSI Command and Status Register Default Definitions |
3.1.5 HARDWARE AFU TESTING MENU
This submenu tests partial reconfiguration by building and loading an memory-mapped I/O example AFU/workload, executes software from host, and tests remote signal tap.
| Menu Option | Description | |
|---|---|---|
| 27 - Build and Compile host_chan_mmio example | This option builds the host_chan_mmio example from the following repo $OFS_PLATFORM_AFU_BBB_EXTERNAL/plat_if_tests/$AFU_TEST_NAME, where AFU_TEST_NAME=host_chan_mmio. This produces a GBS(Green Bit Stream) ready for hardware programming |
|
| 28 - Execute host_chan_mmio example | This option builds the host code for host_chan_mmio example and programs the GBS file and then executes the test | |
| 29 - Modify host_chan_mmio example to insert Remote Signal Tap | This option inserts a pre-defined host_chan_mmio.stp Signal Tap file into the OFS code to allow a user to debug the host_chan_mmio AFU example | |
| 30 - Build and Compile host_chan_mmio example with Remote Signal Tap | This option builds the host_chan_mmio example from the following repo $OFS_PLATFORM_AFU_BBB_EXTERNAL/plat_if_tests/$AFU_TEST_NAME, where AFU_TEST_NAME=host_chan_mmio. This produces a GBS(Green Bit Stream) ready for hardware programming with Remote Signal tap enabled | |
| 31 - Execute host_chan_mmio example with Remote Signal Tap | This option builds the host code for host_chan_mmio example and programs the GBS file and then executes the test. The user must open the Signal Tap window when running the host code to see the transactions in the Signal tap window |
3.1.6 HARDWARE AFU BBB TESTING MENU
This submenu tests partial reconfiguration using a hello_world example AFU/workload, executes sw from the host
| Menu Option | Description |
|---|---|
| 32 - Build and Compile hello_world example | This option builds the hello_ world example from the following repo $FPGA_BBB_CCI_SRC/tutorial/afu_types/01_pim_ifc/$AFU_BBB_TEST_NAME, where AFU_BBB_NAME=hello_world. This produces a GBS (Green Bit Stream) file ready for hardware programming |
| 33 - Execute hello_world example | This option builds the host code for hello_world example and programs the GBS file and then executes the test |
3.1.7 UNIT TEST PROJECT MENU
Builds, compiles and runs standalone simulation block tests. More unit test examples are found at teh follwimng location ofs-d5005/sim/unit_test
| Menu Option | Result |
|---|---|
| 34 - Generate Simulation files for Unit Test | This option builds the simulation file set for running a unit test simulation |
| 35 - Simulate Unit Test dfh_walker and log waveform | entry |
3.1.8 ADP BUILD ALL PROJECT MENU
Builds the complete OFS flow, good for regression testing and overnight builds
For this menu a user can run a sequence of tests (compilation, build and simulation) and executes them sequentially. After the script is successfully executed, a set of binary files is produced which a you can use to evaluate your hardware. Log files are also produced which checks whether the tests passed.
You can run a sequence of tests and execute them sequentially. In the example below when the user selects option 36 from the main menu script, the complete OFS flow covering build, compile and simulation will execute.
| Menu Option | Result |
|---|---|
| 36 - Build and Simulate Complete d5005 Project | Generating Log File with date and timestamp Log file written to /home/DCPsupport/ofs-d5005-1.0.1/log_files/d5005_log_2022_11_10-093649/ofs_d5005_eval.log |
Definition of Multi-Test Set-up
Menu Option 36 above in the evaluation script can be refined to tailor it to the users need and is principally defined by the variable below
MULTI_TEST[A,B]=C
where
A= Total Number of menu options in script
B= Can be changed to a number to select the test order
C= Menu Option in Script
Example 1
MULTI_TEST[36,0]=2
A= 36 is the total number of options in the script
B= 0 indicates that this is the first test to be run in the script
C= Menu option in Script ie 2- List of Documentation for ADP d5005 Project
Example 2
MULTI_TEST[36,0]=2
MULTI_TEST[36,1]=9
In the example above two tests are run in order ie 0, and 1 and the following menu options are executed ie 2- List of Documentation for ADP d5005 Project and 9 - Check ADP software versions for ADP d5005 Project
The user can also modify the build time by de-selecting options they do not wish to use, see below for a couple of use-case scenarios.
User Case for ADP FIM/PR BUILD MENU
In the example below when the user selects option 36 from the main menu the script will only run options from the ADP FIM/PR BUILD MENU (7 options, main menu options 9, 10, 11, 12, 13, 14 and 15). All other tests with an "X" indicates do not run that test.
4 Common Test Scenarios
This section will describe the most common compile build scenarios if a user wanted to evaluate an acceleration card on their server. The Pre-requisite column indicates the menu commands that must be run befere executing the test eg To run Test 5 then a user needs to have run option 10, 12 and 14 before running options 27, 28, 29, 30 and 31.
| Test | Test Scenario | Pre-Requisite Menu Option | Menu Option |
|---|---|---|---|
| Test 1 | FIM Build | - | 10 |
| Test 2 | Partial Reconfiguration Build | 10 | 12 |
| Test 3 | Program FIM and perform Remote System Upgrade | 10 | 18, 19 |
| Test 4 | Bind PF and VF to vfio-pci drivers | - | 20, 21, 22 |
| Test 5 | Build, compile and test AFU on hardware | 10, 12, 13 | 27, 28 |
| Test 6 | Build, compile and test AFU Basic Building Blocks on hardware | 10, 12, 13 | 32, 33 |
| Test 8 | Build and Simulate Unit Tests | - | 34, 35 |
Notices & Disclaimers
Intel® technologies may require enabled hardware, software or service activation. No product or component can be absolutely secure. Performance varies by use, configuration and other factors. Your costs and results may vary. You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document, with the sole exception that you may publish an unmodified copy. You may create software implementations based on this document and in compliance with the foregoing that are intended to execute on the Intel product(s) referenced in this document. No rights are granted to create modifications or derivatives of this document. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. You are responsible for safety of the overall system, including compliance with applicable safety-related requirements or standards. © Intel Corporation. Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of others.