This chapter contains the following sections:
Introduction
Installation for Windows
Requirements
Installation for Linux
RPM Installation
Tar.gz Installation
Configuring the X Windows Motif 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 describes the procedure for the installation of the TASKING CrossView Pro debugger for the XA on Windows, Linux and several UNIX hosts.
Members of the CrossView Pro family of debuggers use the following name convention for their executables:
xfwxa
Start Windows (95/98/NT/2000), if you have not already done so.
Insert the CD-ROM into the CD-ROM drive.
If the TASKING Welcome dialog box appears, skip to Step 5. Otherwise, continue from Step 3.
Select the Start button and select the Run... menu item.
On the command line type:
d:\setup
(substitute the correct drive letter for your CD-ROM drive) and press the <Return> or <Enter> key or click on the OK button.
The TASKING Welcome dialog box appears.
Select a product and click on Install.
Follow the instructions that appear on your screen.
You can find your serial number on the Certificate
of Authenticity or Product Update Form delivered
with the product.
Make sure that the directory containing the installed executable files is present in the PATH environment variable, when you invoke the tools from a command prompt.
License the software product as explained in section 2.8 , Licensing TASKING Products.
The hardware/software requirements are:
Each product on the CD-ROM is available as an RPM package and as a gzipped tar file. For each product the following files are present:
SWproduct-version-RPMrelease.i386.rpm SWproduct-version.tar.gz
Both files contain exactly the same information. When your Linux distribution supports RPM packages, you can install the .rpm file. Otherwise, you can install the product from the .tar.gz file.
In most situations you have to be "root" to install RPM packages, so either login as "root", or use the su command.
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.
Go to the directory on which the CD-ROM is mounted:
cd /cdrom
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.
Make sure that your path is set to include all of the executables you have just installed.
X Windows is required to run CrossView
Pro.
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.
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.
Go to the directory on which the CD-ROM is mounted:
cd /cdrom
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.
Make sure that your path is set to include all of the executables you have just installed.
X Windows is required to run CrossView
Pro.
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 debugger (By default it will be installed in /usr/local).
For CD-ROM install: insert the CD-ROM into the CD-ROM drive. Mount the CD-ROM on a directory, for example /cdrom. Be sure to use a ISO 9660 file system with Rock Ridge extensions enabled. See the UNIX manuals page about mount for details.
Or:
For tape install: insert the tape into the tape unit and create a directory where the contents of the tape can be copied to. Consider the created directory as a temporary workspace that can be deleted after installation has succeeded. For example:
mkdir /tmp/instdir
For CD-ROM install: go to the directory on which the CD-ROM is mounted:
cd /cdrom
For tape install: copy the contents of the tape to the temporary workspace using the following commands:
cd /tmp/instdir tar xvf /dev/tape
where tape is the name of your tape device.
If you have received a tape with more than one product,
use the non-rewinding device for installing the products.
Run the installation script:
sh install
and follow the instructions appearing on your screen.
First a question appears about where to install the software. The default answer is /usr/local. On certain sites you may want to select another location.
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 2.8, 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 <=
Answering y (yes) to this question causes installation to continue. And the final message will be:
Installation of SWxxxxxx xxxx.xxxx completed.
For tape install: remove the temporary installation directory with the following commands:
cd /tmp rm -rf instdir
Make sure that the directory containing the installed executable files is present in the PATH environment variable.
If you purchased a protected TASKING product, license the software product as explained in section 2.8 , Licensing TASKING Products.
X Windows is required to run CrossView
Pro.
To run the Motif version of CrossView Pro on a Sun, you must define the environment variable LD_LIBRARY_PATH to where the library file libMrm.a resides. For example:
LD_LIBRARY_PATH=/usr/dt/lib export LD_LIBRARY_PATH
CrossView Pro uses a binary resource file for appearance-related specifications for windows, menus, dialog boxes, and strings to be accessed at run-time. The name of the resource file has the same name as the executable but with .uid extension. Be sure that the .uid file is present in one of the following directories:
1. the current directory
2. the directory specified by the UIDPATH environment variable
The environment variable UIDPATH specifies the path used by Motif to locate the resource (.uid) file. If not set, it is set to a default value. The resource file is installed in the same directory as the associated executable. So, you should set UIDPATH as follows (Bourne shell syntax):
UIDPATH=path_to_uid/%U export UIDPATH
Replace path_to_uid by the path to the directory in which the resource file is installed. The %U is required.
For more details refer to MrmOpenHierarchy in the OSF/Motif Programmer's Reference manual.
X toolkit resources specify GUI object (widget) attributes. Resources are specified in either the .Xdefaults file or in application class-specific files.
The .Xdefaults file is (typically) loaded into the X server at the start of the session. Any changes take effect only in a new session, or after using xrdb. Alternatively, application class resource files may be used. Application resource files have the same name as the executable CrossView Pro version they refer to (first letter NOT capitalized). Application resource files must be present either in the directory specified by the HOME environment variable, or in the app-defaults directory. The app-defaults directory is typically located under /usr/lib/X11.
X recognizes various environment variables for specifying paths to the application resource files. For more information, consult the chapter on X resources in O'Reilly's X Toolkit Intrinsics Programming Manual and your system documentation.
The X resource specification allows either global (loosely) bound specifications (*foreground: black) or per-widget instance specifications (*button.foreground: black).
The following list shows the relevant widgets used by the Motif version of CrossView Pro:
Windows:
Dialog:
Menu:
Controls:
CrossView Pro repaints its windows in the default color as specified with the Motif widget resource settings. It is possible to overrule this behavior with a resource setting like: "*XmDrawingArea.background: blue".
CrossView Pro uses a non proportional font in all of its windows. The font size is selected using the "Desktop Setup dialog". You can use the "font" resource (*fontList on Motif) to select the font to be displayed in the menubar and dialogs, it won't affect the font displayed in the CrossView Pro windows.
The CrossView Pro stack and data windows are implemented using a XmScrolledWindow widget on Motif.
The following list show the contents of an example app-defaults file intended for Motif environments. Of course you may adjust the colors and font to your preferences. Sample app-defaults files are delivered with the product in the etc directory (app_def.mwm for Motif).
*fontList: 7x13bold *foreground: black *XmMainWindow.background: white *XmScrolledWindow*background: white *XmDrawingArea.background: white *XmBulletinBoard.background: DarkSeaGreen *XmToggleButton*background: gray *XmLabel*background: gray *XmText*background: white *XmScrollBar*background: gray *XmPushButton*background: gray *XmFrame*background: SeaGreen *XmArrowButton*background: gray *XmForm.background: SeaGreen *XmMenuShell*background: DarkSeaGreen *XmCascadeButton*background: SeaGreen
If you encounter any problems due to incorrect resource settings, like invisible text caused by identical text and background color, clear the RESOURCE_MANAGER. Use the following procedure to clear the RESOURCE_MANAGER:
1. Save a copy of the .Xdefaults file located in your home directory.
2. Install an empty .Xdefaults file.
3. Execute xrdb -all .Xdefaults to actually clear the RESOURCE_MANAGER property.
4. Restart CrossView Pro and check if windows and dialogs are displayed correctly.
5. Now you add the saved resources (one by one) back into the .Xdefaults file and execute xrdb to install them in the server. Restart CrossView Pro and check the influence of the new resource settings. Adapt your saved resources when necessary.
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 detailed information on FLEXlm.
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 2.8.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 2.8.7, How to Determine the Hostid and section 2.8.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 Infomation 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 2.8.1, Obtaining License Information, before continuing.
Install the TASKING software product following the installation procedure described in section 2.3, 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 2.8.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 2.8.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 on FLEXlm.
Keep your "License Information Form" ready. If you do not have such a form read section 2.8.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 2.8.5, Setting Up the License Deaemon 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 2.8.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 2.8.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 2.8.6, Modifying the License File Location, for more information.
Now all license infomation is entered, the license manager must be started (see section section 2.8.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 2.8.4 on how to start the daemon and read section 2.8.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 detailed information on FLEXlm.
The license manager (daemon) must always be up and running. To start the daemon complete the following steps on each license server:
1. Start the license manager tool by (Start | Programs | TASKING FLEXlm | FLEXlm License Manager).
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 approrpiate for your platform. steps on each license server:
1. Start the license manager tool by (Start | Programs | TASKING FLEXlm | FLEXlm License Manager).
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. In the directory /etc/rc.config.d create a file named rc.lmgrd with the following contents. Replace FLEXLMDIR by the FLEXlm installation directory (default /usr/local/flexlm):
#!/sbin/sh FLEXLMDIR/bin/lmgrd -2 -p -c FLEXLMDIR/licenses/license.dat >> \ /var/tmp/license.log 2>&1 &
After the -c option, you have to specify the correct location of the license file.
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 exacutable:
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 approriate 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 |
HP-UX |
lanscan (use the station address without the leading '0x') | 0000F0050185 |
SunOS/Solaris | hostid | 170a3472 |
Windows | tkhostid (or use lmhostid) | 0800200055327 |
Table 2-1: 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 | ||||||
HP-UX |
hostname
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 2-2: Determine the hostname