Home → User Notes →
LayTOOLS Installation Notes
A number of executables are available for download from the LayTOOLS ftp site:
LayTOOLS (LayED, LayCIR, LayVER and LayCON)
LayED (LayED and LayCON only)
Each of these sets is delivered in two versions related to the licensing management software used:
Aladdin-based (abbreviation ALD)
RLM-based (abbreviation RLM)
Both Windows and Linux executables are available
Obtaining the MAC address
The MAC address (required for licensing) is obtained as follows:
in a command window (which may be opened in a variety of way, including typing "run" after clicking "Start") type
Depending on your computer set-up, a number of entries for "Physical Address may be given
Provide the one that is under the category "Ethernet Adapter Local Area Connection"
A number of information items may be requested:
In a terminal window:
type "hostname" to provode the system host name
type "hostid" to obtain the system id
type "/sbin/ifconfig | grep HWaddr" to get the ethernet address
(provide the six pairs of alpha characters associated with "eth0")
These notes will assume a Windows design environment. Linux installation is covered in a document "installation.pdf" in the "doc directory
The installation executables available from the LayTOOLS web site are
laytools_ald.exe and laytools_rlm.exe (select the one that corresponds to your selected license manager)
layed_ald.exe and layed_rlm.exe (select the one that corresponds to your selected license manager)
pandr_ald.exe and pandr_rlm.exe (select the one that corresponds to your selected license manager)
Executing tone of these files will:
install the appropriate application programs
install control files and command files
install a set of documentation files
establish the root directory (install directory) environmental variable
update the environmental variable PATH with required application paths
establish a set of example project and technology directories
The example files will be placed in a sub-directory 'laytools' of the home directory (My Documents) and illustrate the format of the project and technology directories when using the LayFRAME (project solution) approach. LayFRAME is essential in the approach but may also, to advantage, be used even when the user is LayED-only based. The advantages are that a common technology file area is defined (for PGroups and standard cell libraries, for example, there is no restriction on project library access (so-called reference mode 1, and the system can easily accommodate upgrading to add other LayTOOLS applications.
Initiating the License Manager
License management may be keyed from a dongle (hard lock key) or from the machine host id (MAC address). A dongle must be used for either the Aladdin approach and may be used for the RLM license management approach. A machine host id may only be used with the RLM license manager approach.
Single-seat dongle driver installation (Aladdin)
For a single-seat system license (also referred to as a portable license) with a dongle key, the Aladdin dongle driver must be installed. This is effected using the executable hldrv32.exe provided as a separate download in the 'Aladdin Drivers' directory on the LayTools ftp site. Running this executable will install and initiate the driver. The license driver will not need to be re-initiated at any time
Network dongle driver installation (Aladdin)
For networked systems with a dongle key, the network Aladdin dongle driver must be installed on the server system only (no driver is required on the user's system). The executable hlsw32.exe provided as a separate download in the 'Aladdin Drivers' directory on the LayTOOLS ftp site must be run on the server system. It is restarted whenever the server system itself is re-booted.
In order to ensure an uninterrupted design experience, the time-out value should be set to a high value. This is done using the command:
The default (without invoking the above) would be 15 minutes. A value of 9999 suggests that the system will never time out!
Monitoring the Aladdin license manager may be done using the executables (also available from the LayTOOLS ftp sit):
aksmon32.exe: license monitor giving an overview of licenses in use
aksdiag32.exe: diagnosis program enabling detection of dongle and driver problems
In large networks, performance may be enhanced by setting the environment variable HLS_IPADDR of the user system with a value which is the license server IP address. Alternatively, one can define an alias name (hlserver) in the license 'host' line of your 'hosts' file.
Single-seat RLM installation
For a single-seat system license (also referred to as a portable license) using an RLM host id key, no additional installation is required.
Network RLM installation
Although for networked systems with an RLM host id key, the network RLM license has already been installed with the application software (sub-directory rlm), it must be initiated using the command:
rlm -c -dlog
where the full path to the command is generally required.
A set of tools for monitoring and manipulating net licenses is located in the directory rlm under the LayTOOLS installation directory:
Further information can be found on:
License files provide the license manager with information about the features required by the user or, in the case of a network system, the user base.
This information it contains consists of a MAC address or dongle identifier, a feature identifier, a license count, and an expiration date.
The license file is delivered to the user by e-mail.
The LayTOOLS software will look for this file in a full path defined by the environment variable ESY_LICENSE. If this is not defined, it will assume it to be in the LayTOOLS installation directory.
In the case of Aladdin licensing, the license file must always be named 'esy.lic' and if delivered by any other name must be renamed to this.
In the case of RLM licensing, no renaming is required and a set of license files may be included in the target license directory
The network HLSERVER uses the TCP and UDP port 3047 for communication. This port should be declared as an exception in the firewall of the HLSERVER computer