MEDAL How To Install

How To Install
DOLPHIN INTEGRATION
How To Install
MEDAL
December 17, 2018
Dolphin Integration
39 Avenue du Granier - BP 65 - Inovallee - 38242-MEYLAN - FRANCE
Phone : + 33 4 76 41 10 96 - Fax : + 33 4 76 90 29 65
www.dolphin-integration.com
contact@dolphin.fr
MEDAL How To Install
COPYRIGHT
c 1992 - 2018 Dolphin Integration. All rights reserved. No part of this document may be trans-
mitted, reproduced, or transcribed in a retrieval system without prior written consent of Dolphin Integration.
The information in this manual is subject to change without notice and does not represent a commitment on
the part of Dolphin Integration. Except as may be explicitly set forth in a written agreement between Dolphin
Integration and its customer, Dolphin Integration does not make, and expressly disclaims, any representations
or warranties as to the completeness, accuracy or usefulness of the information contained in this document.
Dolphin Integration reserves the right to revise this document without any obligation to notify any person of
such revision or change.
The software described in this manual is supplied under a license agreement between you and Dolphin Integra-
tion. The license agreement authorizes the number of copies that may be made and the computer systems on
which they may be used. Any unauthorized duplication or use in whole or part is forbidden.
DOLPHIN INTEGRATION is a brand of Dolphin Design.
SMASH is a registered trademark of Dolphin Design.
Mac OS is a registered trademark of Apple Inc.
Microsoft Windows is a registered trademark of Microsoft Corporation.
Verilog is a registered trademark of Cadence Design Systems Inc.
December 17, 2018 Page 2/35

Your Feedback
How To Install MEDAL
Contents
Contents 3
1 Thanks 5
2 Downloads & Options 6

2.1 What is an Evaluation kit? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 What is a Discovery option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 What is a Commercial option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 How to Install the Software 8

3.1 How to install under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 How to install under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1 Preparing the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.2 Running the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.3 Installing in batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.4 Installing system dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.4.1 Red Hat Enterprise Linux / CentOS . . . . . . . . . . . . . . . . . . . . . . 11
3.2.4.2 Suse Linux Enterprise 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.4.3 Fedora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.4.4 Ubuntu older than 17.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.4.5 Ubuntu 17.10 and newer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.4.6 Debian 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.4.7 Debian 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 How to Install the Access Codes 13

4.1 Finding the hostid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.1 From an installed MEDAL Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.2 Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.3 Under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Installing the license data file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3 Configuring the license data file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4 Starting the license server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.1 Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.2 Under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.2.1 Manually start the license server . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.2.2 Start the license server when the workstation starts . . . . . . . . . . . . . . 18
4.5 Configuring access to license data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.1 SLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.2 SMASH & SCROOGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Page 3/35 December 17, 2018

Your Feedback
5 How to Update Access Codes 22

5.1 Updating the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1.1 Keeping the older license server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1.1.1 Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1.1.2 Under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.1.2 Using a new license server installation . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.1.2.1 Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.1.2.2 Under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2 Configuring access to the new license data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6 How to Obtain Support 27

6.1 Possible sources for technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2 Whom should you contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.3 Preparing a support request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.4 What is supported and how . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
A FLEXlm Server and License Data File 29

A.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
A.2 Feature Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
A.3 License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
A.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
A.5 FLEXlm Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
A.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
A.5.2 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
A.5.3 License management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
B FLEXid Dongle Usage 33

B.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
B.2 Installing the FLEXid dongle driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
B.2.1 Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
B.2.2 Under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
B.3 Finding the FLEXid dongle hostid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
B.3.1 Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
B.3.2 Under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
List of Figures 35

Your Feedback
1 Thanks
As always for new releases, we would also like to thank those customers who take the time to report problems
and/or to suggest improvements (please remember that the best way to do so is by sending an email to sup-
port@dolphin.fr with an accurate description of your problem or suggestion, together with the relevant files
if any). As you will see in the new features, we do our best to take feedback, remarks and suggestions into
account. And even if your suggestion does not appear this time, don’t think it was lost or disregarded. Simply,
it means that its implementation could not fit into the development plan for this particular release, but be sure
we will try to take it into account in a future release.

Your Feedback
2 Downloads & Options
Complete installers are available for download from the web site allowing you to install and get acquainted
with the MEDAL Solutions:
• the Schematic Link EDitor SLED,
• the mixed-signal multi-language single kernel simulator SMASH,
• the power consumption estimator SCROOGE, powered by SMASH,
• the Interactive Curve Display ICD.
The solutions installed are neither slide-shows nor self-running demos but fully functional solutions, limited1
in capabilities or design size when no access codes are installed, that will allow you to discover the solutions,
as long as the limitations are not exceeded. You should start by running the tutorials that are delivered with the
solutions and that guide you through the discovery of simple examples.
The downloads are complete installations of the solutions. If you feel you would need a fully enabled solution
with no limitations, please contact Dolphin or one of their distributors. Commercial access codes can be used
to enable complete usage. The downloaded installer can of course be used to update your local installation of
the solutions.
Distribution You are free to distribute (not to sell!) the installer without any restrictions, as long as you do not
modify its contents.
Feedback If you download our solutions, it would be really nice to hear your feedback.
2.1 What is an Evaluation kit?
When the MEDAL Solutions are installed and used without any access codes, they are used as an Evaluation
kit. Warning dialogs may be displayed when using the MEDAL Solutions without any access codes and, if
limitations are exceeded, explicit error messages will be displayed.
If access codes are installed but the hostid in the access codes does not correspond to the hostid of the
workstation, the MEDAL Solutions will run in Evaluation mode. If you have installed access codes but the
MEDAL Solutions are still in Evaluation mode, please check that the hostid corresponds and request support
if needed.
License The License for use of the MEDAL Solutions as Evaluation kits restricts usage to evaluation purposes.
Evaluation You should start by running the tutorials that are delivered with our solutions and that guide you
through the discovery of simple examples.
Discovery The Discovery option access codes (see 2.2) can be easily obtained from the web site without
needing to download or reinstall the solutions.
1 The limitations when using the MEDAL Solutions without Commercial access codes are described on the web site.

Your Feedback
2.2 What is a Discovery option?
When the MEDAL Solutions are installed and used with Discovery access codes, the Discovery options are
enabled. The Discovery options are free options allowing you to use the solutions as long as the limitations are
not exceeded. Information dialogs may be displayed when using the Discovery option and, if limitations are
exceeded, explicit error messages will be displayed.
If you enter a hostid in the download forms on the web site, you will automatically receive access codes for
the Discovery options. Installing these access codes removes the warnings dialogs that may be displayed when
using an Evaluation kit and enables its use for teaching or other purposes.
License The License authorizes the use of Discovery options for any design purposes.
Discovery You should start by running the tutorials that are delivered with our solutions and that guide you
through the discovery of simple examples.
Commercial Other commercial options provide unlimited use.
2.3 What is a Commercial option?
When the MEDAL Solutions are installed and used with access codes delivered by a sales representative of
Dolphin or one of their distributors, one of the Commercial options are enabled. There is no difference between
the Commercial options provided for Industrial users, for Universities or for Partners.

Your Feedback
3 How to Install the Software

This guide presents the installation of MEDAL Solutions under Windows and Linux from a web download.
Notation Conventions
The following table lists the notation that is used throughout the installation instructions to represent items that
must be replaced with information specific to your installation and the symbols that are used in the examples.
<y> Replace with the year.

<q> Replace with the quarter.
% Represents the Linux shell prompt
3.1 How to install under Windows
The MEDAL Solutions are designed to run on Microsoft Windows Vista / 7 / 8 / 10 on x86_64 platforms.
From a download on the Dolphin web site, the installer is available both as a deployable Microsoft Installer
(.msi) or an auto-extracting Microsoft Installer (.exe).
Run the installation by directly executing the file that you chose to download:
dolphin_solutions_<y>_<q>_windows.msi
dolphin_solutions_<y>_<q>_windows.exe
This will start the installer in graphic mode:
• Select a location to install the software and follow the instructions.
3.2 How to install under Linux
These installation instructions describe how to install MEDAL Solutions under Linux workstations. The in-
tended users of this section are System Administrators.
The MEDAL Solutions are designed to run under X-Window on RedHat Enterprise Linux 6 (RHEL6) and
supports compatible Linux distributions on x86_64 platforms.
Warning
It is recommended that you complete each step in the installation instructions to ensure that the product
is correctly installed.
3.2.1 Preparing the installation
1. Identify a location to install the MEDAL Solutions. The location where you will install should be acces-
sible from all machines involved in the installation.
2. Locate the executable installer, downloaded from the web. Verify that the file is named with the expected
release number and OS type:

Your Feedback
dolphin_solutions_<y>_<q>_linux.install
3. Prepare the installation directory. You must have the permissions to write into <install-dir>. The
installation will extract a directory containing the application files.
4. Now run the installer (see 3.2.2).
5. Add the bin directory of each MEDAL solution in the installation to your PATH environment variable.
3.2.2 Running the installer
The MEDAL solutions require some system packages to be installed in order to work correctly. If you run the
installer with the root user and your Linux distribution is recognized, the installer can install these dependen-
cies.
You can also run the installer with an other user. In this case, the dependencies installation step will be unavail-
able.
If you need or prefer to install the required system packages manually, you can do this later (see 3.2.4).
The web download provides an installer:
• Make sure that it can be executed:
% chmod +x dolphin_solutions_<y>_<q>_linux.install
• Run the installer:
% ./dolphin_solutions_<y>_<q>_linux.install
This will start the installer in graphic mode:
• Select a location to install the software and follow the instructions.
3.2.3 Installing in batch mode
The installer also allows performing a batch installation with no graphic windows. In order to perform such an
installation, several command line options are available:

Your Feedback
--mode default To specify that no graphic windows should be displayed and that
default choices should be used for all options.
--prefix <installdir> To specify the installation directory and override the default location.
--type <installtype> To specify which components should be installed. Possible values for
<installtype> are:
• Typical: install everything (Applications, examples, tutorials,

license server, run environments...)
• “Applications and examples”: install SLED,

SMASH, SCROOGE and ICD and their examples, but without
licensing utilities or system packages.
• “Applications only”: install SLED, SMASH,

SCROOGE and ICD without examples and tutorials, and
without the system packages required to run them.
• “Examples only”: install the examples and tutorials for

SLED, SMASH and SCROOGE. In case of network
installations, a user may want to install them in a directory where
he as write permissions to try running and modifying them.
• “Run environments”: install the system packages required

to run the MEDAL solutions. This requires to run the installer as
root, and may not be available if you are not running the installer
on a recognized Linux distributions.
• “License server”: install only the licensing utilities, and

the system package required to run them.
Run the installer:
% ./dolphin_solutions_<y>_<q>_linux.install --mode default \
--prefix <installdir>
3.2.4 Installing system dependencies
The software requires some system packages to be installed in order to work correctly. The precise list of
required system packages varies with the Linux distribution and its release. Here is a short list for some
common distributions.
If you run the installer with the root account on a recognized Linux distribution, you may also choose to
automatically install the required packages.

Your Feedback
Warning
In some cases, absent packages may cause the software to exit immediately with no message.
3.2.4.1 Red Hat Enterprise Linux / CentOS
This distribution only requires to install the glibc development package. You just have to type:
% yum install glibc-devel
In order to run the license server, you will also require the Linux Standard Base (LSB) libraries:
% yum install redhat-lsb-core
3.2.4.2 Suse Linux Enterprise 11
This distribution only requires to install the glibc development package. You just have to type:
% zypper install glibc-devel
3.2.4.3 Fedora
The default Fedora installation already has all the required packages to run Dolphin Solutions.
However, in order to run the license server, you will require the Linux Standard Base (LSB) libraries. You just
have to type:
% dnf install redhat-lsb-core
3.2.4.4 Ubuntu older than 17.10
The default Ubuntu installation already has all the required packages to run Dolphin Solutions.
However, in order to run the license server, you might need to create the system temporary directory /usr/tmp,
that might not exist within this distribution. You just have to type:
% ln -s /var/tmp -t /usr
The license server also requires the Linux Standard Base (LSB) libraries. On Ubuntu releases older than 16.04,
there is a system package for it:
% apt-get install lsb-core
On Ubuntu release 16.04 or newer however, you need to create the required loader, to compensate for Ubuntu’s
removed support for Linux Standard Base:
% ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

Your Feedback
3.2.4.5 Ubuntu 17.10 and newer
These distributions only require to install the glibc development package. You just have to type:
% apt-get install libc6-dev
In order to run the license server, you might need to create the system temporary directory /usr/tmp, that
might not exist within this distribution. You just have to type:
% ln -s /var/tmp -t /usr
In order to compensate for Ubuntu’s removed support for Linux Standard Base (LSB), which is required by the
license server, you also need to create the LSB loader:
% ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
3.2.4.6 Debian 7
The default Debian 7 installation already has all the required packages to run Dolphin Solutions.
However, in order to run the license server, you will require the Linux Standard Base (LSB) libraries. You just
have to type:
3.2.4.7 Debian 8
This distribution requires to install some development and environment packages. You just have to type:
% apt-get install libc6-dev binutils libcanberra-gtk-module
In order to run the license server, you will also require the Linux Standard Base (LSB) libraries:

Your Feedback
4 How to Install the Access Codes
This section describes:
• 4.1How to find the hostid of the computer or workstation
• 4.2What needs to be done to install the access codes and configure the MEDAL solutions for each type
of license.
• 4.3How to configure the license data file.
• 4.4How to start the license server when access to the licensed features needs to be controlled by a server.
• 4.5How to configure MEDAL Solutions to use the correct license data file or server under Windows and
Linux.
4.1 Finding the hostid
The hostid is an identification code that is used by the licensing software to identify the workstation. It is
usually specific to the workstation itself, but it may be provided by a FLEXid dongle, connected to a USB port,
for licenses that are to be moved between different workstations.
The preferred method to find the hostid is to obtain it from an installed MEDAL Solution. There are some
other ways that are mentioned below, but they are platform dependent and there are some traps that are easy to
overlook. If the MEDAL Solutions and the platform specific method do not give the same hostid, the one
found with the MEDAL Solution should be used.
4.1.1 From an installed MEDAL Solution
If you already have a MEDAL Solution installed, you can find the list of valid hostids in the Licensing panel
of the Preferences dialog (see section 4.5).
In SLED, SMASH or SCROOGE, open the Preferences dialog using the menu command “Edit . Preferences”,
and select the “Licensing” panel (see figure 3 and figure 4). The “HostId” field in the “Description” sections
shows the list of valid hostids.
4.1.2 Under Windows
For the Windows platform, the hostid is the physical or ethernet MAC2 address of any network card.
You can obtain the list of MAC addresses from a command shell, with the command:
getmac
Note: The list might include some pseudo interfaces that cannot be used as hostid.
2 Media Access Control

Your Feedback
4.1.3 Under Linux
For the Linux platform, the hostid is the hardware or ethernet MAC address of an eth# network interface
or an em# network interface. You can obtain this address with the command:
% /sbin/ifconfig eth0
or:
% /sbin/ifconfig em1
The hostid are the figures following “HWaddr”.
Warning
Linux has a “hostid” command, but the identifier that is returned by this command is not the one used
by the MEDAL Solutions.
4.2 Installing the license data file
Depending on the type of access codes, the license data file may need to be installed on the local workstation
or on a license server.
• If you do not know which type of access codes you have, just follow the instructions at the beginning of
each of the following paragraphs to determine from the license file content which operations you have to
perform.
• If the access codes are for a Discovery option obtained automatically when downloading from the web
site:
1. the license data file simply needs to be installed, without any modifications, in a directory on the
local workstation, for instance in the root directory of the installation of the MEDAL Solutions.
2. the MEDAL solutions need to be configured to use the corresponding access codes (see 4.5).
• If the access codes are for a node-locked serverless license:
1. the license data file simply needs to be installed, without any modifications, in a directory on the
local workstation, for instance in the root directory of the installation of the MEDAL Solutions.
2. the MEDAL solutions need to be configured to use the corresponding access codes (see 4.5).
• If the access codes are for a node-locked license served by the node-locked workstation:
1. the license data file needs to be installed in a directory on the local workstation, for instance in the
FLEXlm server directory of the installation of the MEDAL Solutions,
2. the license data file needs to be configured (see 4.3),
3. the license server needs to be started (see 4.4),
4. the MEDAL solutions need to be configured to use the corresponding license server (see 4.5).

Your Feedback
• If the access codes are for a floating license, single or redundant, or a node-locked license served by a
license server:
1. the license data file needs to be installed in a directory on the license server, for instance in the
FLEXlm server directory,
2. the license data file needs to be configured (see 4.3),
3. the license server needs to be started (see 4.4),
4. the MEDAL solutions need to be configured to use the corresponding license server (see 4.5).
4.3 Configuring the license data file
If your license is not generated by Dolphin to be served by a server (no SERVER line present in the
license data file), such as for a Discovery option obtained when downloading from the web site or an
“uncounted” license, you must skip this section.
Some fields in the license data files must be changed before running the license server:
• Edit the license file with a text editor
• Replace <hostname> or <hostname1> with the server hostname
• Adapt the server port number if necessary
• Replace <PATH> by the complete absolute path to the “dolphin.d” file
• Save the file
Warning
If you change anything but the mentioned fields, the license data file will most likely become invalid.
Example license data file:
#Customer: Dolphin Integration

#
#Server configuration
#
SERVER <hostname1> 9271b9afa162 21097
VENDOR dolphin.d "<PATH>/dolphin.d"
#
Modified license data file for a workstation called HEBUS:
#Customer: Dolphin Integration

#
#Server configuration
#

Your Feedback
SERVER HEBUS 9271b9afa162 21097

VENDOR dolphin.d "C:/Solutions 2017 Q2/licensing/FLEXlm/x64_n6/dolphin.d"
#
4.4 Starting the license server
If your license is not generated by Dolphin to be served by a server (no SERVER line present in the
license data file), such as for a Discovery option obtained when downloading from the web site or an
“uncounted” license, you must skip this section.
Refer to section §A for more detailed information about the FLEXlm license server.
Note
You cannot run more than one Dolphin license server per workstation.
Note
If the license server does not run on the same platform as the MEDAL Solutions, you may download the
license server for your platform from the web site as a separate archive.
4.4.1 Under Windows
• Open the license administration tool by running the application going into the licensing/FLEXlm/x64_n6
directory of the Dolphin Solutions installation and running the application lmtools.exe (see figure 1).
Figure 1: FLEXlm Service Configuration Dialog
• In the “Service/License File” tab, check “Configuration using Services”
• In the “Configure Services” tab:

Your Feedback
– Define the path to “lmgrd.exe” and the license file

– Define the path to a the debug log file that the license server will create and fill with log information
– Check “Use Services”
– Check “Start server at power Up”
– Click on “Save Service”
• In the “Start/Stop/Reread” tab, click on “Start Server” to start the server for this session
• Close the dialog
To verify that the server started correctly, you can use the license management tools or check the content of the
log file. To use the license manager, activate the “Server Status” tab and click on the “Perform Status Enquiry”
button (see figure 2). The text field below indicates whether the server is running and whether the licenses are
available.
Figure 2: FLEXlm Server Status
The debug log file defined in the “Configure Services” tab provides all the necessary information to diagnose
the origin of a problem with a license server. You can see a sample of this file below:
10:16:47 (lmgrd) The TCP port number in the license, 21097, is already in use.
10:16:47 (lmgrd) Possible causes:
10:16:47 (lmgrd) 1) lmgrd is already running for this license.
10:16:47 (lmgrd) 2) The OS has not "cleared" this port since lmgrd died.
10:16:47 (lmgrd) 3) Another process is using this port number (unlikely).
10:16:47 (lmgrd) Solutions:
10:16:47 (lmgrd) 1) Make sure lmgrd and all vendor daemons for this

Your Feedback
Note
The license server only reads the license file at startup. If you change the contents of the license file
(either to correct errors or to install an update) then you have to restart the license server to apply the
change.
If the server is running correctly, then go to section 4.5 to see how to use this server with MEDAL Solutions.
4.4.2 Under Linux
Warning
The /lib64/ld-lsb-x86-64.so.3 file is required (see 3.2.1).
4.4.2.1 Manually start the license server
Under Linux, anybody can start the license server.

Go to the flexlm directory in the installation:
% cd <install dir>/licensing/FLEXlm
Start the license server with the lmgrd command:
% ./lmgrd -c <license data file> -L <log file>
To check that the license server started correctly, you can query for available licenses with the lmstat command:
% ./lmstat -c <license data file>
or
% ./lmstat -c <port>@<host>
Where <port> and <host> are the machine name and TCP port number defined in the SERVER line of the
license file.
Note
change.
If the server is running correctly, then go to section 4.5 to see how to use this server with MEDAL Solutions.
4.4.2.2 Start the license server when the workstation starts

Your Feedback
Warning
Configuring the license server to start when the workstation starts requires root privileges.
The S99dolphin file in the licensing/FLEXlm directory is a Linux startup script that can automatically
start the license server when the workstation starts. To install it:
1. Edit the S99dolphin file and update the parameters at the beginning of the file:
• LICENSE_FILE: full path to the updated license file.

• LOG_FILE: full path to the server log file. This file will be recreated by the license server, it does
not have to already exist.
• LMGRD and LMUTIL: full path to the licensing programs
• RUNAS: login name of the account used to start the license server. This account must have read
access to the license file and the licensing programs, and it must have write access to the server log
file.
2. Make the script run when the workstation starts by copying it to /etc/rc2.d and /etc/rc3.d
directories.
3. If you did not already start the license server manually, you may start it with the script:
/etc/rc2.d/S99dolphin start
Note
change.
4.5 Configuring access to license data
The licensing setup of MEDAL Solutions is shared between the different solutions. This means that whichever
solution is setup first, the setup is common and taken into account by the other solutions.
There are two options for specifying the paths to FLEXlm license files or license servers:
• They can be specified in the DOLPHIN.D_LICENSE_FILE, DOLPHIND_LICENSE_FILE or LM_LICENSE_FILE

environment variables; in this case, the “System setting” option must be selected
• They can be defined in the licensing preferences; in this case, the “Application setting” option must be
selected.
– the “Add local” button can be used add a license data file; the file will be added to the list of license
files and servers,
– the “Add remote” button will show a new dialog where the license server information must be
entered (in the <port>@<host> form); the server will be added to the list of license files and
servers (please refer to the section 4.4 to configure FLEXlm servers),

Your Feedback
– To remove license files or servers, just select them in the list and press the “Remove” button.
Whenever licensing settings are modified, the list of available features and associated information are updated.
For each feature, the description provides a status:
• The name of the feature.
• The time remaining before the expiration of feature:
– Orange if the remaining time is less than 30 days,
– Red if the remaining time is less than 7 days or if the feature is expired.
• The number of tokens not used and the total number of tokens available for the feature.
4.5.1 SLED
Displayed with the menu “Edit Preferences” of the main window of SLED, the “Licensing” panel in the
preferences dialog (see figure 3) allows configuring access to the license server or the data file.
Figure 3: SLED Licensing Setup

Your Feedback
4.5.2 SMASH & SCROOGE
Displayed with the menu “Edit Preferences” of the main window of SMASH or SCROOGE, the “Licensing”
panel in the preferences dialog (see figure 4) allows configuring access to the license server or the data file.
Figure 4: SMASH & SCROOGE Licensing Setup

Your Feedback
5 How to Update Access Codes
This section describes how to install new access codes when older ones are already installed.
It supposes that you know the different types of access codes, and which one you are using. Please refer to 4.2
if you do not.
It only applies if you stay with the same type of access codes. If you are changing the type of access codes,
follow the instructions for installing a new license data file instead (see 4.2).
5.1 Updating the License Server
If your access codes have not been generated by Dolphin to be served by a license server (no SERVER
line present in the license data file), such as for a Discovery option obtained when downloading from the
web site or an “uncounted” license, you must skip this section.
You may choose either to update the license data file in your older license server installation or to install the
license data file in a new license server installation.
The former implies less operations, but it prevents you from uninstalling the older release of the product.
Note
You cannot run more than one Dolphin license server per workstation.
5.1.1 Keeping the older license server
Note
With this method, the configuration of the access to the license data in the applications is the same, so
the only operations are on the server.
The steps are:
• the license data file needs to be configured in the same manner as for new access codes (see 4.3),
• the older license data file needs to be replaced with the new configured one,
• the license server needs to apply the changes.
5.1.1.1 Under Windows
• In the “Start/Stop/Reread” tab (see 5), click on “ReRead License File” to update the license data for the
server

Your Feedback
Figure 5: FLEXlm Server Control Dialog
To verify that the server was updated correctly, you can use the license management tools or check the content
of the log file. To use the license manager, activate the “Server Status” tab and click on the “Perform Status
Enquiry” button (see figure 2). The text field below indicates whether the server is running and whether the
licenses are available.
the origin of a problem with a license server.
If the server is running correctly, your access codes update is finished.
5.1.1.2 Under Linux
Under Linux, anybody can tell the license server to update the license data from its original license data file.
Go to the flexlm directory in the installation:
% cd <install dir>/licensing/FLEXlm
Update the license data in the server with the with the lmreread command:
% ./lmreread -c <license data file>
To check that the license server was updated correctly, you can query for available licenses with the lmstat
command:
% ./lmstat -c <license data file>
or
license file.
If the server is running correctly, your access codes update is finished.

Your Feedback
5.1.2 Using a new license server installation
Note
This method requires administrator privileges on the license server machine.
5.1.2.1 Under Windows
• Configure the license data file (see 4.3).
• In the “Start/Stop/Reread” tab (see 5), click on “Stop Server” to stop the license server running from the
older installation directory.
• In the “Configure Services” tab:
– Define the path to new “lmgrd.exe”, the new license file and the new debug log file
• In the “Start/Stop/Reread” tab, click on “Start Server” to start the server for this session
To verify that the server was updated correctly, you can use the license management tools or check the contents
of the log file. To use the license manager, activate the “Server Status” tab and click on the “Perform Status
Enquiry” button (see figure 2). The text field below indicates whether the server is running and whether the
licenses are available.
the origin of a problem with a license server.
If the server is running correctly, then go to section 5.2 to see how to use this server with Dolphin Solutions.
5.1.2.2 Under Linux
If the license server was started manually
Go to the flexlm directory in the older installation:
% cd <old install dir>/licensing/FLEXlm
Stop the license server with the lmdown command:
% ./lmdown -c <old license data file>
Go to the flexlm directory in the new installation:
% cd <new install dir>/licensing/FLEXlm
Start the new license server with the lmgrd command:

Your Feedback
% ./lmgrd -c <new license data file> -L <log file>
To check that the license server started correctly, you can query for available licenses with the lmstat com-
mand:
% ./lmstat -c <new license data file>
or
license file.
If the license server was started automatically at boot time
Stop the older license server:
% /etc/rc2.d/S99dolphin stop
Edit the /etc/rc2.d/S99dolphin and /etc/rc3.d/S99dolphin files and update the parameters at
the beginning of the file:
• LICENSE_FILE: full path to the new license file.
• LOG_FILE: full path to the new server log file. This file will be recreated by the license server, it does
not have to already exist.
• LMGRD and LMUTIL: full path to the new licensing programs
Start the new license server:
% /etc/rc2.d/S99dolphin start
To check that the license server started correctly, you can query for available licenses with the lmstat com-
mand:
% ./lmstat -c <new license data file>
or
license file.

Your Feedback
5.2 Configuring access to the new license data
The licensing setup of Dolphin Solutions is shared between the different solutions. So, if the access to the
license data is not changed, there is nothing to reconfigure in the applications.
• If you replaced your older license file with the new one, there is nothing to reconfigure in the applications,
your access codes update is finished.
• If you configured a remote access to the license server in your applications (in the <port>@<host>
form), there is nothing to reconfigure in the applications, your access codes update is finished.
• In other cases, you have to reconfigure the access to the license data in your application. Just follow the
instructions in section 4.5 as if it was the first configuration.

Your Feedback
6 How to Obtain Support
This paragraph describes the technical support that you are entitled to. It does not cover the conditions under
which you may get new releases of the software. This is a different matter covered by our Innovation Contract.
Please contact either your distributor or our sales services if you need information. This paragraph deals with
the everyday technical support that you may need when using the software, and how to get it efficiently. The
terms and conditions of the technical support are subject to changes without notice.
6.1 Possible sources for technical support
You may find technical information in the documentation and in the tutorials delivered with the product, as well
as on our web site. www.dolphin-integration.com contains application notes, information about new releases,
patches and updates. . . If the information in these places is not sufficient to solve your problem, support is
provided by our distributors and by our support center as well.
6.2 Whom should you contact
If you need assistance, please follow these rules:
• First level technical support is through your local distributor if any. Your distributor will solve basic
problems regarding installation. . .
• More technical questions will be routed to our technical support center, and solved by our support engi-
neers.
• If you purchased a license directly from Dolphin, the fastest and most efficient route to support services
is through email to your sales representative or to support@dolphin.fr.
6.3 Preparing a support request
If you send a support request, please provide the following information:
• The exact software version and release number.
• Your machine configuration (type of computer, exact OS revision, amount of RAM, . . . )
As far as possible, please send support requests with a single problem at a time. When describing the problem,
please provide an accurate description of the sequence of actions which leads to the problem. Specify if the
problem is reproducible or not. If the problem is related to specific input files, provide all files needed to
reproduce the problem in our offices. Please provide files which are readily useable. Support engineers may
have difficulties accepting files which must be reworked before investigation.
6.4 What is supported and how
Technical support is not subject to a fee and is provided to users of the two latest releases of the software (the
current release, and the previous one). Support for older releases is provided on a best-effort basis.

Your Feedback
The answer will be identified by an issue identification number (ID#). Please refer to this issue number in all
subsequent exchanges with the support center on this support request. The answer may also include change
request identification numbers (DDIsa).
Depending on the severity of the problem (and in many cases on the quality of the formulation of the request...),
the nature of this answer will be:
• a direct solution,
• questions from the support engineer, if additional information is needed to diagnose, or if the initial
request is incompletely formulated,
• a workaround, in case the problem is non-blocking and there is an alternate way to do the job, or to avoid
the problem you described,
• a target date for a workaround,
• a target date for a fix, if the problem is blocking (you cannot use your system because of a problem
which should not exist according to the specifications). Please note that the date is a target date: what
we commit to is deploying our maximum efforts to fix the problem as soon as possible.
In case you submit a blocking problem, we shall release what we call an ASAP3 release which fixes the
problem, and deliver it to you, free of charge. ASAP releases concern the very latest release only. In case
the problem is reported at a time which is really close to the delivery of a new release, we may choose to
incorporate the fix in the new release only.
3 As Soon As Possible

Your Feedback
A FLEXlm Server and License Data File

This appendix provides a quick introduction to FLEXlm, which is the license manager used for Dolphin So-
lutions. It is not necessary to read this appendix to completely install the license data. However, it helps
understand the license management system and helps diagnose and correct problems.
For more detailed documentation on the usage of FLEXlm, refer to the “FLEXlm End User Guide”.
A.1 Overview
FLEXlm is one of the most commonly used licensing solutions. It is a flexible license manager that controls
the usage of protected functionalities of a software solution.
Basically, each protected functionality is associated to a FLEXlm “feature”, or feature in short. FLEXlm
organizes the licensing policy around this notion of feature. In other words, the software solution provides
several “features” that are protected by FLEXlm.
FLEXlm allows the software provider to deliver license data files containing access codes that enable the
available features with associated usage constraints on these features. This way, new licenses can be provided
simply with a new license data file. The possible usage constraints on features are detailed in the next section.
A.2 Feature Constraints
The constraints define the specific conditions in which the features can be acquired to enable the protected
functionality. These constraints can define limits for validity periods, number of concurrent usages, used
stations. . . Each feature has its own constraints, independently from the other ones. The constraints commonly
used for features of Dolphin Solutions are explained below:
• Release number: the license data file allows to run only the specified or older releases.
• Expiration date: date after which the feature cannot be used any more.
• Number of tokens: possible concurrent usages for a feature. Features with a limited number of concurrent
usages are also called “counted features”, and unlimited features are called “uncounted features”.
• Node-locked or floating: the feature is used only on a specific host or on any hosts.Platform: the license
may be restricted to a certain platform. Dolphin Solutions may only use the feature if they are run on the
specified platform. This does not restrict the platform of the license server.
You can see below an example license data file, which defines the parameters of several features with the
corresponding constraints highlighted.
# Reseller: DOLPHIN Integration

# Licensee: DOLPHIN Integration
# 38242 Meylan Isere
# Contact: MEDAL (medal@dolphin.fr)
# Single server configuration (FLEXlm 9.2)
SERVER mars 000e0ca5e918 21097
VENDOR dolphin.d "./dolphin.d"

Your Feedback
# WARNING: You must edit the hostname on the SERVER line (1st arg).
# You must edit the (optional) path on the VENDOR line (2nd arg).
# Most other changes will invalidate this license data file.
#
# SLED1.7 access codes for option(s):
# SLED
#
INCREMENT SOCHLE_sled dolphin.d 107.0 31-dec-2011 2 \
C28BBE5B3DF0 VENDOR_STRING="Missing EDA Links" \
PLATFORMS=i86_n vendor_info="DOLPHIN Integration" \
dist_info="DOLPHIN Integration" ck=171 \
SIGN=A3A940E80042
INCREMENT SOCHLE_slednet dolphin.d 107.0 31-dec-2011 2 \
4FAE9CCE206C VENDOR_STRING="Missing EDA Links" \
PLATFORMS=i86_n vendor_info="DOLPHIN Integration" \
dist_info="DOLPHIN Integration" ck=150 \
SIGN=133B17184A82
Note that the license file is encrypted to avoid the modification of critical data. Therefore, only specific parts
of the license file can be modified:
• The server name and the port number on the SERVER line.
• An optional path to the dolphin.d file in the VENDOR line.
Two types of license files are delivered for MEDAL Solutions: free Discovery licenses and commercial li-
censes.
The free Discovery license consists in an uncounted feature locked on a specific host. You can start as many
simultaneous executions as you want on only one specific workstation. To activate this license, configure the
Solutions to directly use this license file.
Other commercial options may consist of counted or uncounted features that can be node-locked or floating.
If they are counted this means that you are granted a limited number of simultaneous executions for the corre-
sponding features. An optional restriction on the authorized station allows obtaining licenses at a lower price.
This kind of license requires a license server to run on a specific host. The next section explains how a license
server provides tokens for its features.
A.3 License Server
A license server is necessary to control the number of simultaneous usages of a specific feature. It consists in
a daemon process that runs on a specific host (server). This daemon centralizes the feature requests and keeps
up-to-date the number of available tokens for each feature.
According to its specific restrictions, a feature can be granted to any requesting hosts (floating) or only to one
specific host (node-locked). The license server is in charge of controlling this.
Figure 6 presents an example of floating counted licenses through a network. The license server provides three
floating features F1, F2 and F3 with respectively five, two and one tokens. External hosts Client A and Client

Your Feedback
B have already reserved one token for feature F1, and F1, F2 and F3. When Client C requests feature F3, the
license server replies that this feature is not available because the token limit has been reached.
Figure 6: Example of floating counted tokens
A.4 Troubleshooting
If you are experiencing problems that you cannot solve, then contact the support and transmit the following
elements:
• The current license data file, with all features used.
• The current log file if a license server has been started.
• The error messages on licenses displayed by Dolphin Solutions.
A.5 FLEXlm Releases
A.5.1 Introduction
This section informs customers of Dolphin Integration on how to manage products using different releases of
FLEXlm. Indeed, our products are kept up-to-date with the most relevant FLEXlm releases to provide the
best possible service. However, new releases can be delivered at different dates for different products of the
same vendor and will be for products from different vendors. So, you can have products that concurrently use
different FLEXlm releases. This document helps users to manage compatibility between successive releases of
FLEXlm.

Your Feedback
A.5.2 Compatibility
The FLEXlm product suite provides full backward compatibility for all delivered elements. This compatibility
works as described below:
• The lmgrd and lmreread utilities support any older dolphin.d,
• The dolphin.d binary supports any application using older FLEXlm libraries,
• An application supports older license file formats.
A.5.3 License management
The best way to avoid release mismatches is to run each license data file on one license server and to use the
original release for each product. You can run several license managers on one workstation, provided that they
run with different vendor daemons. In this case, these servers must use different ports.
But if different products use the same vendor daemon, you must merge corresponding license data into one file.
To manage correctly the merging of license data files, follow these rules:
• Take the newer version of lmgrd for every application.
• Take the newer version of dolphin.d for Dolphin products.
Use lmver to determine the FLEXlm release of a program or a FLEXlm utility.

Your Feedback
B FLEXid Dongle Usage

This appendix provides a quick overview of FLEXid dongle usage specifics.
B.1 Overview
FLEXlm license servers (and sometimes the access codes themselves) are locked on a hostid, which is
an identification code that is used by the licensing software to identify the workstation. This hostid may
be provided by a FLEXid dongle, which is a USB key that is plugged into the workstation and gives it an
additional hostid.
Using a FLEXid dongle has some restrictions:
• The FLEXid dongle driver must be installed and running.
• The FLEXid dongle must be plugged into the workstation before the application starts and it must remain
plugged until the application exits. If it is removed while the application is still running, the application
will detect that its license is lost and exit prematurely.
B.2 Installing the FLEXid dongle driver
B.2.1 Under Windows
For the Windows platform, the dongle driver is provided in the licensing/FLEXlm/driver directory of
the Dolphin Solutions installation or directly from the url:
https://www.dolphin-integration.com/medal/downloads/license/FLEXID9_windows.zip
To install the driver, uncompress the downloaded archive, and run the FLEDId_Dongle_Driver_Installer.bat
program.
B.2.2 Under Linux
For the Linux platform, the dongle driver is provided in the licensing/FLEXlm directory of the Dolphin
Solutions installation.
Warning: Installing the FLEXid dongle driver on Linux requires root privileges
The driver is made of two files:
• The aksusbd file, which is the driver daemon.
• The S99aksusbd file, which is a workstation start up script that allows to automatically run the FLEXid
dongle driver when the workstation starts.
To start the driver, you have to
1. edit the S99aksusbd script, and update the AKSUSBD variable with the correct full path to the aksusbd
file on your system
2. make the script run when the workstation starts by copying it to /etc/rc2.d and /etc/rc3.d
directories

Your Feedback
3. start the driver with the command:
/etc/rc2.d/S99aksusbd start
On some Linux distributions, the driver does not detect when a FLEXid dongle is plugged in after it is started.
When this happens, you have to restart the driver with the command:
/etc/rc2.d/S99aksusbd restart
B.3 Finding the FLEXid dongle hostid
The easiest way to find the FLEXid dongle hostid is to read it on the key itself.
On one side of the key, you can find the text “FLEXid=9-HHHHHHHH” (replace H with hexadecimal charac-
ters). This whole text is the FLEXid dongle hostid.
You can also use programs to read the FLEXid dongle hostid from the machine into which it is plugged.
B.3.1 Under Windows
For the Windows platform, you can obtain the hostid by going into the licensing/FLEXlm/x64_n6
directory of the Dolphin Solutions installation and running the application lmtools.exe
Select the System Settings tab and get the hostid in the FLEXID text field.
B.3.2 Under Linux
For the Linux platform, you can obtain the hostid by going into the licensing/FLEXlm directory of the
Dolphin Solutions installation and running the command:
./lmutil lmhostid -flexid
Note
The FLEXid driver has to be installed before you run this command.

Your Feedback
List of Figures
1 FLEXlm Service Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 FLEXlm Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 SLED Licensing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 SMASH & SCROOGE Licensing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5 FLEXlm Server Control Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6 Example of floating counted tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Your Feedback

MEDAL How To Install

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MEDAL How To Install

Caricato da

Copyright:

Formati disponibili

How To Install

DOLPHIN INTEGRATION is a brand of Dolphin Design.

SMASH is a registered trademark of Dolphin Design.

Mac OS is a registered trademark of Apple Inc.

Microsoft Windows is a registered trademark of Microsoft Corporation.

Verilog is a registered trademark of Cadence Design Systems Inc.

December 17, 2018 Page 2/35

2 Downloads & Options 6

3 How to Install the Software 8

4 How to Install the Access Codes 13

Page 3/35 December 17, 2018

5 How to Update Access Codes 22

6 How to Obtain Support 27

A FLEXlm Server and License Data File 29

B FLEXid Dongle Usage 33

December 17, 2018 Page 4/35

Page 5/35 December 17, 2018

2 Downloads & Options

• the Schematic Link EDitor SLED,

• the mixed-signal multi-language single kernel simulator SMASH,

• the power consumption estimator SCROOGE, powered by SMASH,

• the Interactive Curve Display ICD.

2.1 What is an Evaluation kit?

December 17, 2018 Page 6/35

2.2 What is a Discovery option?

Commercial Other commercial options provide unlimited use.

2.3 What is a Commercial option?

Page 7/35 December 17, 2018

3 How to Install the Software

<y> Replace with the year.

3.1 How to install under Windows

This will start the installer in graphic mode:

• Select a location to install the software and follow the instructions.

3.2 How to install under Linux

3.2.1 Preparing the installation

December 17, 2018 Page 8/35

4. Now run the installer (see 3.2.2).

3.2.2 Running the installer

The web download provides an installer:

• Make sure that it can be executed:

• Run the installer:

This will start the installer in graphic mode:

• Select a location to install the software and follow the instructions.

3.2.3 Installing in batch mode

Page 9/35 December 17, 2018

• Typical: install everything (Applications, examples, tutorials,

• “Applications and examples”: install SLED,

• “Applications only”: install SLED, SMASH,

• “Examples only”: install the examples and tutorials for

• “Run environments”: install the system packages required

• “License server”: install only the licensing utilities, and

Run the installer:

% ./dolphin_solutions_<y>_<q>_linux.install --mode default \

3.2.4 Installing system dependencies

December 17, 2018 Page 10/35

3.2.4.1 Red Hat Enterprise Linux / CentOS

% yum install glibc-devel

% yum install redhat-lsb-core

3.2.4.2 Suse Linux Enterprise 11

% zypper install glibc-devel

% dnf install redhat-lsb-core

3.2.4.4 Ubuntu older than 17.10

% apt-get install lsb-core