- Semiconductor BusinessHOME
- Products and Services of Macnica,Inc.
-
technical information
-
Events and Seminars
- Handling Manufacturer
- Support
- Inquiry
- Click here to purchase products
- Semiconductor business e-mail magazine registration
Narrow down by specifying conditions
現在2149件がヒットしています。check
hello.
My name is Hanako Altera and I provide technical support for Altera® FPGA products at Macnica.
This time, regarding the paid license type FLOAT license of Quartus® Prime,
We will introduce how to coexist with the licenses of software developed by other manufacturers and how to manage them.
Both manufacturers shall manage licenses with FLEXlm software.
FLOAT licenses are operated by installing FLEXlmsoftware on a computer that manages licenses (commonly known as a license server).
FLEXlm is a license management tool that is standardly used in the software of various companies in the field of EDA (Electronic Design Automation). This tool is also used for the FLOAT license of Quartus® Prime.
Similarly, development software from other manufacturers often uses this FLEXlm to manage FLOAT licenses.
If the license management tool is the same, license management for multiple companies can be operated with a single license server.
Files required for management and operation of FLEXlm
The administrator of the license server PC obtains the following files and sets and edits each file.
lmutil,lmtools,lmgrd,alterad
It is saved in the installation folder of Quartus® Prime installed on the client PC, so copy and paste it to the license server PC.
If the server PC and client PC platforms are different, please obtain the driver from the manufacturer's website.
There is no rule for the folder path on the license server PC where each file is saved, but it is recommended to save them in one folder for easy management.
(Caution! Do not use double-byte characters and spaces in the folder path to save.)
In this example, the OS is Windows and the save folder path is C:\FLEXlm.
The Quartus Primelicense file (*.dat) is
You can apply for and obtain a license through the Self-Service License Center, which is exclusively for administrators who registered when signing up for the license.
For details, please see the content below.
How to get a new license for Quartus® Prime, IP and Questa* - Altera® FPGA Edition
For information on how to obtain other vendor daemons and license files, please contact the respective manufacturer.
Below is a brief description of the role of each file.
|
File |
Overview |
| lmutil | A utility for managing the license server using the command line. |
| lmtools | A GUI (Graphical User Interface) utility for Microsoft Windows to manage the license server. |
| lmgrd |
License manager daemon. Prompts to start and stop the vendor daemons of each manufacturer, and manages and issues licenses. |
| alterad |
Vendor daemon for Altera ® FPGA development tools and IP. Manage and issue usage rights such as Quartus ® Prime Standard Edition, Pro Edition, and IP (intellectual property) for client PCs. Only one alterad can run on one PC. |
| Company B vendor daemon |
Vendor daemon for company B's development software. Manage and issue usage rights for Company B's software to client PCs. Only one vendor daemon for company B can run on one PC. |
| License file (*.dat) |
A text file issued by each manufacturer under a maintenance contract. Information on the license server, available products and functions, expiration dates, etc. are specified. Requires editing of server name, vendor daemon path, etc. |
| Debug log file (*.log) |
A file useful for debugging, as it records the status and error messages of each daemon in the FLEXlm system. Optional and automatically generated when configuring lmutil or lmtools. |
Two management methods
[A]Collectand managelicense files
[B]Manage license files separately for each manufacturer
Let's take a look at each feature.
<Notes> In "B] Managing license files separately for each manufacturer," it is also possible to prepare and manage lmgrd for each vendor. (Image)
[A] Collect and manage license files
In this method, the license file for Quartus ® Prime and the license file for Company B's software are combined into one, and the operation is also managed by one.
<Benefits>
・ Easy work such as editing the license file!
(This method is recommended for those who are new to license management with FLEXlm.)
<Disadvantages>
・When one company's service is stopped for maintenance, etc., it is necessary to stop the operation of the software of all manufacturers that are simultaneously managed.
(May be annoying for users who use software unrelated to maintenance.)
◆ How to integrate license files in method [A]
Please refer to "[A] Integration method when managing license files as one" in this content.
◆ How to set lmtools in method [A]
Please refer to "[A] How to set up lmtools when managing license files collectively" in this content.
[B] Manage license files separately for each manufacturer
In this method, the license file for Quartus ® Prime and the license file for Company B's software are managed separately, and the operation is also managed separately.
<Benefits>
・Because management is independent for each manufacturer, one company's license can be suspended while another company's license is in operation.
(Valid during maintenance such as updating license files and vendor daemons)
<Disadvantages>
・Requires license management tool settings for each manufacturer
・The administrator of the license server PC must understand the mechanism of FLEXlm.
The license file for Quartus® Prime contains
The license includes the Questa* - Altera® FPGA Edition license and the AXI BFM IP function (part of the IP Base Suite lineup).
All license functions are managed by the Siemens vendor daemon mgcld (mgcld64), so the license file for Quartus ® Prime can be further subdivided into the alterad vendor daemon and the mgcld (mgcld64) vendor daemon.
◆ How to separate the license file in method [B]
Please refer to "[B] Separation method when managing license files separately for each manufacturer" in this content.
◆ How to set lmtools in method [B]
See "[B] How to set up lmtools when managing license files separately for each manufacturer" in this content.
――――――――
Next, I will explain how to edit the license file and how to configure LMTOOLS.