Visible to Intel only — GUID: vwb1688655944767
Ixiasoft
1. Answers to Top FAQs
2. Introduction to Intel® FPGA Software Installation and Licensing
3. Determining System Requirements
4. Downloading Intel® FPGA Software
5. Installing Intel FPGA Software
6. Licensing Intel® FPGA Software
7. Next Steps After Installing and Licensing the Software
A. Intel FPGA Software Installation and Licensing Archives
B. Document Revision History for Intel® FPGA Software Installation and Licensing
3.3.1. Operating System Requirements
3.3.2. Windows* Subsystem for Linux* (WSL 1) on Windows Requirements for Nios® II EDS
3.3.3. Intel® High Level Synthesis Compiler Software Requirements
3.3.4. Questa*-Intel® FPGA Edition Software Requirements
3.3.5. Other Intel FPGA Software Requirements
3.3.6. Third-Party Software Requirements
5.1. Installing Intel® FPGA Software Through Intel® Quartus® Prime Installer
5.2. Installing the Intel® FPGA Software Manually
5.3. Managing Multiple Versions and Copies of Intel FPGA Software
5.4. Setting Intel® Quartus® Prime Environment Variables
5.5. Starting the Intel® Quartus® Prime Software
5.6. Updating Intel FPGA Software
5.7. Uninstalling Intel FPGA Software
5.8. Troubleshooting Installation Issues
5.2.1. Selecting the Installation Path
5.2.2. Installing Intel FPGA Software at the Command Prompt
5.2.3. Installing from .tar Files
5.2.4. Installing Device Support to Existing Installation
5.2.5. Using the Same Installation Files on Multiple Systems
5.2.6. Installing Programming Cable Drivers
5.2.7. Installing and Configuring a JTAG Server
6.1. Summary of Intel FPGA Software Licenses Required
6.2. Evaluating the Intel® Quartus® Prime Software
6.3. Licensing Intel® FPGA Software Walkthrough
6.4. Getting Hardware Information for License
6.5. Using the Intel FPGA Self-Service Licensing Center
6.6. About Intel® FPGA Software License Files
6.7. Checking the IP License Status
6.8. Configuring the License Manager Server
6.9. Troubleshooting License File Issues
6.1.1. Intel® Quartus® Prime Software License
6.1.2. Questa*-Intel® FPGA Edition and Questa*-Intel® FPGA Starter Edition Software License
6.1.3. Nios® II Embedded Design Suite License
6.1.4. Intellectual Property (IP) Cores Licenses
6.1.5. Siemens EDA* AXI Verification IP Suite License (Intel FPGA Edition)
6.5.1. Using the License Assistant
6.5.2. Getting a License File with Your New Purchase
6.5.3. Viewing Licenses
6.5.4. Filtering Your Licenses
6.5.5. Viewing and Generating a Legacy License
6.5.6. Viewing Licenses or License Files Associated to a Computer
6.5.7. Regenerating a License File
6.5.8. Generating a Temporary Checkout License
6.5.9. Generating a Companion License
6.5.10. Renewing Your License
6.5.11. Managing a Computer Profile
6.5.12. Rehosting a License on a Different Computer
6.5.13. Rehosting All Licenses from Current Computer to a Different Computer
6.5.14. Rehosting Multiple/Partial Licenses from Current Computer to a Different Computer
6.5.15. Sharing a License with Another User
6.5.16. Adding Delegate Administrators to Your Licenses and Computers
6.5.17. Splitting Seats on Your License and Generating Licenses
6.5.18. Merging or Adding Seats on Your License and Generating License
6.5.19. Adding Floating Seats
6.5.20. Signing Up for an Evaluation or No-Cost License
6.5.21. Signing Up For an Employee License
6.8.1. Installing the FLEXlm License Manager Server Software on Another License Server
6.8.2. Upgrading the FLEXlm License Manager Server Software
6.8.3. (Windows Only) Starting and Stopping the License Server
6.8.4. (Windows Only) Starting the License Server Automatically
6.8.5. Rereading an Existing License File on a License Server
Visible to Intel only — GUID: vwb1688655944767
Ixiasoft
6.3.4.1. Setting up a License File in the License Server
Perform the following steps in the license server:
- Save the license.dat file. The preferred location is:
- Windows*:
<drive>:\flexlm
- Linux:
/usr/local/flexlm/licenses
- Windows*:
- Identify the hostname of the license server.
- If the license server uses Windows*, specify the port number for the licensing manager.
- Choose a number outside of the 27000-28000 range, and unique on the machine.
In Linux systems, the FLEXlm license manager automatically chooses a free port between 27000 and 27009. - Modify the SERVER line in the license.dat file to include the hostname and port number of the license server.
SERVER <hostname> <8 or 12-character host or NIC ID> <host port number>
- Identify the path to the alterad vendor daemon executable. 4
- Windows*:
<installation_directory>\bin64\alterad.exe
- Linux:
<installation-directory>/linux64/alterad
- Windows*:
- Optionally, identify the user-defined port numbers for the alterad daemons.
The FLEXlm software works with Internet firewalls that require you to specify port numbers in the license file on the SERVER line and each VENDOR or DAEMON line. The syntax to specify a port is PORT=<number>. Finally, you must allow firewall access to those port numbers.
- Modify the VENDOR line in the license.dat file to include the path to the alterad daemon 5 and the daemon's port number.
VENDOR alterad <path/to/alterad> [port=<user-defined port number>]
- If you are using a license file for the Questa*-Intel® FPGA Edition software and/or Siemens EDA AXI BFMs, identify the path to the Siemens EDA* (formerly Mentor Graphics) vendor daemon executable mgcld. 4
- (Optional) Identify the user-defined port numbers for the mgcld daemon.
Allow firewall access to those port numbers.
- Modify the VENDOR line in the license.dat file to include the path to the mgcld daemon5 and the daemon's port number.
VENDOR mgcld <path/to/mgcld> [port=<user-defined port number>]
When you complete all modifications, ensure the license file conditions are met.
Setting Up Floating Network Licenses on the License Server
The following example shows how to specify port numbers in a floating license file, where ports 1800, 1801, and 1802 provide access through a firewall.
SERVER myServer 0123456789ab 1800 VENDOR alterad ./alterad port=1801 VENDOR mgcld ./mgcld port=1802
With the modified license.dat file, you can set up the FLEXlm license manager on the license server, and finally start the license server.
4 If the license server does not provide the necessary vendor daemon, copy the required daemon from another machine, save the file in a location on the license server, and specify the daemon location on the license server in the license file.
5 If the server path has spaces in it, enclose the full path in quotation marks.