Intel® High Level Synthesis Compiler Standard Edition: Getting Started Guide

Download PDF
ID 683053
Date 3/26/2020
Public
Document Table of Contents
Document Table of Contents x
1. Intel® High Level Synthesis (HLS) Compiler Standard Edition Getting Started Guide 2. High Level Synthesis (HLS) Design Examples and Tutorials 3. Troubleshooting the Setup of the Intel® HLS Compiler A. Intel® HLS Compiler Standard Edition Getting Started Guide Archives B. Document Revision History for Intel® HLS Compiler Standard Edition Getting Started Guide
1. Intel® High Level Synthesis (HLS) Compiler Standard Edition Getting Started Guide x
1.1. Intel® High Level Synthesis Compiler Standard Edition Prerequisites 1.2. Installing the Intel® HLS Compiler Standard Edition on Linux Systems 1.3. Installing the Intel® HLS Compiler Standard Edition on Microsoft* Windows* Systems 1.4. Initializing the Intel® HLS Compiler Standard Edition Environment
2. High Level Synthesis (HLS) Design Examples and Tutorials x
2.1. Running a High Level Synthesis (HLS) Design Example (Linux) 2.2. Running a High Level Synthesis (HLS) Design Example (Windows)
3. Troubleshooting the Setup of the Intel® HLS Compiler x
3.1. Intel® HLS Compiler Licensing Issues
3.1. Intel® HLS Compiler Licensing Issues x
3.1.1. QuestaSim* Licensing Error Messages 3.1.2. LM_LICENSE_FILE Environment Variable
3.1.2. LM_LICENSE_FILE Environment Variable x
3.1.2.1. QuestaSim* Software License-Specific Considerations
1. Intel® High Level Synthesis (HLS) Compiler Standard Edition Getting Started Guide
2. High Level Synthesis (HLS) Design Examples and Tutorials
3. Troubleshooting the Setup of the Intel® HLS Compiler
A. Intel® HLS Compiler Standard Edition Getting Started Guide Archives
B. Document Revision History for Intel® HLS Compiler Standard Edition Getting Started Guide

1.4. Initializing the Intel® HLS Compiler Standard Edition Environment

Before you can compile your component with the Intel® HLS Compiler i++ command, a number of environment variables must be set for the i++ command to run successfully.

The Intel® HLS Compiler environment initialization script applies only to the environment variable settings in your current terminal or command prompt session. You must initialize the Intel® HLS Compiler environment each time that you start a terminal or command prompt session to develop your design.

To initialize your current terminal or command prompt session so that you can run the Intel® HLS Compiler:

  • On Linux systems, initialize your environment as follows:
    1. In your terminal session, change directories to the hls directory in your Intel® Quartus® Prime installation directory.
      For example, /home/<username>/intelFPGA_standard/22.1/hls
    2. Run the following command from the hls directory to set the environment variables for the i++ command in the current terminal session:

      source init_hls.sh

      The command prints out the modified environment variable settings.

    The environment initialization script shows the environment variables that it set, and you can now run the i++ command from this terminal session.
  • On Windows systems, initialize your environment as follows:
    1. Start a Visual Studio x64 Win64 Command Prompt session.
      For example, C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\vcvars64.bat.
    2. In your x64 Win64 Command Prompt session, change directories to the hls directory in your Intel® Quartus® Prime installation directory.
      For example, C:\intelFPGA_standard\22.1\hls
    3. Run the following command from the hls directory to set the environment variables for the i++ command in the current terminal session:

      init_hls.bat

      The command prints out the modified environment variable settings.

    The environment initialization script shows the environment variables that it set, and you can now run the i++ command from this command prompt session.
Tip: To set the environment variables permanently, follow your operating system's standard procedure for making persistent changes to environment variable settings. Review the output of the environment initialization script to determine the environment variables to set permanently.
Level Two Title