This chapter contains the following sections:
Introduction
Software Installation
Installation for Windows
Installation for Linux
Installation for UNIX Hosts
Software Configuration
Configuring the Embedded Development Environment
Configuring the Command Line Environment
Licensing TASKING Products
Obtaining License Information
Installing Node-Locked Licenses
Installing Floating Licenses
Starting the License Daemon
Setting Up the License Deaemon to Run Automatically
Modifying the License File Location
How to Determine the Hostid
How to Determine the Hostname
This chapter guides you through the procedures to install the software on a Windows system or on a Linux or UNIX host.
The software for Windows has two faces: a graphical interface (Embedded Development Environment) and a command line interface. The Linux and UNIX software has only a command line interface.
After the installation, it is explained how to configure the software and how to install the license information that is needed to actually use the software.
1. Start Windows 95/98/XP/NT/2000, if you have not already done so.
2. Insert the CD-ROM into the CD-ROM drive.
If the TASKING Showroom dialog box appears, proceed with Step 5.
3. Click the Start button and select Run...
4. In the dialog box type d:\setup (substitute the correct drive letter for your CD-ROM drive) and click on the OK button.
The TASKING Showroom dialog box appears.
5. Select a product and click on the Install button.
6. Follow the instructions that appear on your screen.
You can find your serial number on the Start-up
kit envelope, delivered with the product.
7. License the software product as explained in section 1.4, Licensing TASKING Products.
Each product on the CD-ROM is available as an RPM package, Debian package and as a gzipped tar file. For each product the following files are present:
SWproduct-version-RPMrelease.i386.rpm swproduct_version-release_i386.deb SWproduct-version.tar.gz
These three files contain exactly the same information, so you only have to install one of them. When your Linux distribution supports RPM packages, you can install the .rpm file. For a Debian based distribution, you can use the .deb file. Otherwise, you can install the product from the .tar.gz file.
1. In most situations you have to be "root" to install RPM packages, so either login as "root", or use the su command.
2. Insert the CD-ROM into the CD-ROM drive. Mount the CD-ROM on a directory, for example /cdrom. See the Linux manual pages about mount for details.
3. Go to the directory on which the CD-ROM is mounted:
cd /cdrom
4. To install or upgrade all products at once, issue the following command:
rpm -U SW*.rpm
This will install or upgrade all products in the default installation directory /usr/local. Every RPM package will create a single directory in the installation directory.
The RPM packages are 'relocatable', so it is possible to select a different installation directory with the --prefix option. For instance when you want to install the products in /opt, use the following command:
rpm -U --prefix /opt SW*.rpm
For Red Hat 6.0 users: The --prefix option
does not work with RPM version 3.0, included in the Red Hat 6.0 distribution. Please
upgrade to RPM verion 3.0.3 or higher, or use the .tar.gz file installation described in the next section if you want to install in a non-standard directory.
1. Login as a user.
Be sure you have read, write and execute permissions in the installation directory. Otherwise, login as "root" or use the su command.
2. Insert the CD-ROM into the CD-ROM drive. Mount the CD-ROM on a directory, for example /cdrom. See the Linux manual pages about mount for details.
3. Go to the directory on which the CD-ROM is mounted:
cd /cdrom
4. To install or upgrade all products at once, issue the following command:
dpkg -i sw*.deb
This will install or upgrade all products in a subdirectory of the default installation directory /usr/local.
1. Login as a user.
Be sure you have read, write and execute permissions in the installation directory. Otherwise, login as "root" or use the su command.
2. Insert the CD-ROM into the CD-ROM drive. Mount the CD-ROM on a directory, for example /cdrom. See the Linux manual pages about mount for details.
3. Go to the directory on which the CD-ROM is mounted:
cd /cdrom
4. To install the products from the .tar.gz files in the directory /usr/local, issue the following command for each product:
tar xzf SWproduct-version.tar.gz -C /usr/local
Every .tar.gz file creates a single directory in the directory where it is extracted.
1. Login as a user.
Be sure you have read, write and execute permissions in the installation directory. Otherwise, login as "root" or use the su command.
If you are a first time user, decide where you want to install the product. By default it will be installed in /usr/local.
2. Insert the CD-ROM into the CD-ROM drive and mount the CD-ROM on a directory, for example /cdrom.
Be sure to use an ISO 9660 file system with Rock Ridge extensions enabled. See the UNIX manual pages about mount for details.
3. Go to the directory on which the CD-ROM is mounted:
cd /cdrom
4. Run the installation script:
sh install
Follow the instructions appearing on your screen.
First a question appears about where to install the software. The default answer is /usr/local.
On some hosts the installation script asks if you want to install SW000098, the Flexible License Manager (FLEXlm). If you do not already have FLEXlm on your system, you must install it otherwise the product will not work on those hosts. See section 1.4, Licensing TASKING Products.
If the script detects that the software has been installed before, the following messages appear on the screen:
*** WARNING *** SWxxxxxx xxxx.xxxx already installed. Do you want to REINSTALL? [y,n]
Answering n (no) to this question causes installation to abort and the following message being displayed:
=> Installation stopped on user request <=
Answer y (yes) to continue with the installation. The last message will be:
Installation of SWxxxxxx xxxx.xxxx completed.
5. If you purchased a protected TASKING product, license the software product as explained in section 1.4 , Licensing TASKING Products.
Now you have installed the software, you can configure both the Embedded Development Environment and the command line environment for Windows, Linux and UNIX.
After installation, the Embedded Development Environment is automatically configured with default search paths to find the executables, include files and libraries. In most cases you can use these settings. To change the default settings, follow the next steps:
1. Double-click on the EDE icon on your desktop to start the Embedded Development Environment (EDE).
2. From the Project menu, select Directories...
3. Fill in the following fields:
Instead of typing the pathnames, you can click on the Configure... button.
A dialog box appears in which you can select and add directories, remove them again and change their order.
To facilitate the invocation of the tools from the command line (either using a Windows command prompt or using Linux or UNIX), you can set environment variables.
You can set the following variables:
Environment Variable | Description |
PATH | With this variable you specify the directory in which the executables reside (default: c:\ctc\bin). This allows you to call the executables when you are not in the bin directory. Usually your system already uses the PATH variable for other purposes. To keep these settings, you need to add (rather than replace) the path. Use a semicolon (;) to separate pathnames. |
CTCINC | With this variable you specify one or more additional directories in which the C compiler ctc looks for include files. The compiler first looks in these directories, then always looks in the default c:\ctc\include directory. |
ASTCINC | With this variable you specify one or more additional directories in which the assembler astc looks for include files. The assembler first looks in these directories, then always looks in the default c:\ctc\include directory. |
ASPCPINC | With this variable you specify one or more additional directories in which the assembler aspcp looks for include files. The assembler first looks in these directories, then always looks in the default c:\ctc\include directory. |
CCTCBIN | With this variable you specify the directory in which the control program cctc looks for the executable tools. The path you specify here should match the path that you specified for the PATH variable. |
CCTCOPT | With this variable you specify options and/or arguments to each invocation of the control program cctc. The control program processes these arguments before the command line arguments. |
LIBTC1V1_2 LIBTC1V1_3 LIBTC2 | With this variable you specify one or more alternative directories in which the linker ltc looks for library files for a specific core. The linker first looks in these directories, then always looks in the default c:\ctc\lib directory. |
LM_LICENSE_FILE | With this variable you specify the location of the license data file. You only need to specify this variable if your host uses the FLEXlm licence manager. |
TMPDIR | With this variable you specify the location where programs can create temporary files. Usually your system already uses this variable. In this case you do not need to change it. |
Table 1-1: Environment variables
The following examples show how to set an environment variable using the PATH variable as an example.
Add the following line to your autoexec.bat file:
set PATH=%path%;c:\ctc\bin
You can also type this line in a Command Prompt window
but you will loose this setting after you close the window.
1. Right-click on the My Computer icon on your desktop and select Properties from the menu.
The System Properties dialog appears.
2. Select the Environment tab.
3. In the list of System Variables select Path.
4. In the Value field, add the path where the executables are located to the existing path information. Separate pathnames with a semicolon (;). For example: c:\ctc\bin.
5. Click on the Set button, then click OK.
1. Right-click on the My Computer icon on your desktop and select Properties from the menu.
The System Properties dialog appears.
2. Select the Advanced tab.
3. Click on the Environment Variables button.
The Environment Variables dialog appears.
4. In the list of System variables select Path.
5. Click on the Edit button.
The Edit System Variable dialog appears.
6. In the Variable value field, add the path where the executables are located to the existing path information. Separate pathnames with a semicolon (;). For example: c:\ctc\bin.
7. Click on the OK button to accept the changes and close the dialogs.
Enter the following line (C-shell):
setenv PATH $PATH:/usr/local/ctc/bin
TASKING products are protected with license management software (FLEXlm). To use a TASKING product, you must install the licensing information provided by TASKING for the type of license purchased.
You can run TASKING products with a node-locked license or with a floating license. When you order a TASKING product determine which type of license you need (UNIX products only have a floating license).
This license type locks the software to one specific PC so you can use the product on that particular PC only.
This license type manages the use of TASKING product licenses among users at one site. This license type does not lock the software to one specific PC or workstation but it requires a network. The software can then be used on any computer in the network. The license specifies the number of users who can use the software simultaneously. A system allocating floating licenses is called a license server. A license manager running on the license server keeps track of the number of users.
See Appendix A,
Flexible License Manager (FLEXlm), for more information.
Before you can install a software license you must have a "License Information Form" containing the license information for your software product. If you have not received such a form follow the steps below to obtain one. Otherwise, you can install the license.
1. If you need a node-locked license, you must determine the hostid of the computer where you will be using the product. See section 1.4.7, How to Determine the Hostid.
2. When you order a TASKING product, provide the hostid to your local TASKING sales representative. The License Information Form which contains your license key information will be sent to you with the software product.
1. If you need a floating license, you must determine the hostid and hostname of the computer where you want to use the license manager. Also decide how many users will be using the product. See section 1.4.7, How to Determine the Hostid and section 1.4.8, How to Determine the Hostname.
2. When you order a TASKING product, provide the hostid, hostname and number of users to your local TASKING sales representative. The License Information Form which contains your license key information will be sent to you with the software product.
Keep your "License Information Form" ready. If you do not have such a form read section 1.4.1, Obtaining License Information, before continuing.
Install the TASKING software product following the installation procedure described in section 1.2.1, Installation for Windows.
Create a file called "license.dat" in the c:\flexlm directory, using an ASCII editor and insert the license information contained in the "License Information Form" in this file. This file is called the "license file". If the directory c:\flexlm does not exist, create the directory.
If you wish to install the license file in a different
directory, see section 1.4.6,
Modifying the License File Location.
If you already have a license file, add the license information
to the existing license file. If the license file already contains any
SERVER lines, you must use another license file. See section 1.4.6
, Modifying the License File Location,
for additional information.
The software product and license file are now properly installed.
See Appendix A,
Flexible License Manager (FLEXlm), for more information.
Keep your "License Information Form" ready. If you do not have such a form read section 1.4.1, Obtaining License Information, before continuing.
Install the TASKING software product following the installation procedure described earlier in this chapter on the computer or workstation where you will use the software product.
As a result of this installation two additional files for FLEXlm will be present in the flexlm subdirectory of the toolchain:
If you already have installed FLEXlm v6.1 or higher for Windows or v2.4 or higher for UNIX (for example as part of another product) you can skip this step and continue with step 3. Otherwise, install SW000098, the Flexible License Manager (FLEXlm), on the license server where you want to use the license manager.
The installation of the license manager on Windows also sets up the license daemon to run automatically whenever a license server reboots. On UNIX you have to perform the steps as described in section 1.4.5, Setting Up the License Daemon to Run Automatically.
It is not recommended to run a license manager on a Windows 95 or Windows 98 machine. Use Windows NT instead (or UNIX).
If FLEXlm has already been installed as part of a non-TASKING product you have to make sure that the bin directory of the FLEXlm product contains a copy of the Tasking daemon (see step 1).
Insert the license information contained in the "License Information Form" in the license file, which is being used by the license server. This file is usually called license.dat. The default location of the license file is in directory c:\flexlm for Windows and in /usr/local/flexlm/licenses for UNIX.
If you wish to install the license file in a different
directory, see section 1.4.6,
Modifying the License File Location.
If the license file does not exist, you have to create it using an ASCII editor. You can use the license file license.dat from the toolchain's flexlm subdirectory as a template.
If you already have a license file, add the license information
to the existing license file. If the SERVER lines in the license file
are the same as the SERVER lines in the License Information Form, you do not need
to add this same information again. If the SERVER lines are not the same,
you must use another license file. See section 1.4.6
, Modifying the License File Location,
for additional information.
On each PC or workstation where you will use the TASKING software product the location of the license file must be known. If it differs from the default location (c:\flexlm\license.dat for Windows, /usr/local/flexlm/licenses/license.dat for UNIX), then you must set the environment variable LM_LICENSE_FILE. See section 1.4.6, Modifying the License File Location, for more information.
Now all license information is entered, the license manager must be started (see section section 1.4.4 ). Or, if it is already running you must notify the license manager that the license file has changed by entering the command (located in the flexlm bin directory):
lmreread
On Windows you can also use the graphical FLEXlm Tools (lmtools): Start lmtools (if you have used the defaults this can be done by selecting Start -> Programs -> TASKING FLEXlm -> FLEXlm Tools), fill in the current license file location if this field is empty, click on the Reread button and then on OK. Another option is to reboot your PC.
The software product and license file are now properly installed.
The license manager (daemon) must always be up and running. Read section 1.4.4 on how to start the daemon and read section 1.4.5 for information how to set up the license daemon to run automatically.
If the license manager is running, you can now start using the TASKING product.
See Appendix A,
Flexible License Manager (FLEXlm), for more information.
The license manager (daemon) must always be up and running. To start the daemon complete the following steps on each license server:
1. From the Windows Start menu, select Programs -> TASKING FLEXlm -> FLEXlm License Manager.
The license manager tool appears.
2. In the Control tab, click on the Start button.
3. Close the program by clicking on the OK button.
1. Log in as the operating system administrator (usually root).
2. Change to the FLEXlm installation directory (default /usr/local/flexlm):
cd /usr/local/flexlm
3. For C shell users, start the license daemon by typing the following:
bin/lmgrd -2 -p -c licenses/license.dat >>& \ /var/tmp/license.log &
Or, for Bourne shell users, start the license daemon by typing the following:
bin/lmgrd -2 -p -c licenses/license.dat >> \ /var/tmp/license.log 2>&1 &
In these two commands, the -2 and -p options restrict the use of the lmdown and lmremove license administration tools to the license administrator. You omit these options if you want. Refer to the usage of lmgrd in Appendix A, Flexible License Manager (FLEXlm), for more information.
To set up the license daemon so that it runs automatically whenever a license server reboots, follow the instructions below that are appropriate for your platform. steps on each license server:
1. From the Windows Start menu, select Programs -> TASKING FLEXlm -> FLEXlm License Manager.
The license manager tool appears.
2. In the Setup tab, enable the Start Server at Power-Up check box.
3. Close the program by clicking on the OK button. If a question appears, answer Yes to save your settings.
In performing any of the procedures
below, keep in mind the following:
1. Log in as the operating system administrator (usually root).
2. Append the following lines to the file /etc/rc.local. Replace FLEXLMDIR by the FLEXlm installation directory (default /usr/local/flexlm):
FLEXLMDIR/bin/lmgrd -2 -p -c FLEXLMDIR/licenses/license.dat >> \ /var/tmp/license.log 2>&1 &
1. Log in as the operating system administrator (usually root).
2. In the directory /etc/init.d create a file named rc.lmgrd with the following contents. Replace FLEXLMDIR by the FLEXlm installation directory (default /usr/local/flexlm):
#!/bin/sh FLEXLMDIR/bin/lmgrd -2 -p -c FLEXLMDIR/licenses/license.dat >> \ /var/tmp/license.log 2>&1 &
3. Make it executable:
chmod u+x rc.lmgrd
4. Create an 'S' link in the /etc/rc3.d directory to this file and create 'K' links in the other /etc/rc?.d directories:
ln /etc/init.d/rc.lmgrd /etc/rc3.d/Snumrc.lmgrd ln /etc/init.d/rc.lmgrd /etc/rc?.d/Knumrc.lmgrd
num must be an appropriate sequence number. Refer to you operating system documentation for more information.
The default location for the license file on Windows is:
c:\flexlm\license.dat
On UNIX this is:
/usr/local/flexlm/licenses/license.dat
If you want to use another name or directory for the license file, each user must define the environment variable LM_LICENSE_FILE. Do this in autoexec.bat (Windows 95/98), from the Control Panel -> System | Environment (Windows NT) or in a UNIX login script.
If you have more than one product using the FLEXlm license manager you can specify multiple license files to the LM_LICENSE_FILE environment variable by separating each pathname (lfpath) with a ';' (on UNIX also ':'):
Example Windows:
set LM_LICENSE_FILE=c:\flexlm\license.dat;c:\license.txt
Example UNIX:
setenv LM_LICENSE_FILE /usr/local/flexlm/licenses/license.dat:/myprod/license.txt
If the license file is not available on these hosts, you must set LM_LICENSE_FILE to port@host; where host is the host name of the system which runs the FLEXlm license manager and port is the TCP/IP port number on which the license manager listens.
To obtain the port number, look in the license file at host for a line starting with "SERVER". The fourth field on this line specifies the TCP/IP port number on which the license server listens. For example:
setenv LM_LICENSE_FILE 7594@elliot
See Appendix A,
Flexible License Manager (FLEXlm), for detailed information.
The hostid depends on the platform of the machine. Please use one of the methods listed below to determine the hostid.
Platform | Tool to retrieve hostid | Example hostid |
SunOS/Solaris | hostid | 170a3472 |
Windows | tkhostid (or use lmhostid) | 0800200055327 |
Table 1-2: Determine the hostid
If you do not have the program tkhostid
you can download it from our Web site at: http://www.tasking.com/support/flexlm/tkhostid.zip . It
is also on every product CD that includes FLEXlm.
To retrieve the hostname of a machine, use one of the following methods.
Platform | Method | ||||
SunOS/Solaris |
hostname
Windows 95/98 |
Go to the Control Panel, open "Network", click on "Identification". Look for "Computer name". |
Windows NT |
Go to the Control Panel, open "Network". In the "Identification" tab look for "Computer Name". | |
Table 1-3: Determine the hostname