2 SOFTWARE INSTALLATION

This chapter contains the following sections:

Introduction

Note about Filenames

Installation for Windows
Requirements

Installation for UNIX Hosts

Configuring the X Windows Motif Environment

Using X Resources

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

2.1 Introduction

This chapter describes the procedure for the installation of the TASKING CrossView Pro debugger for the DSP56xxx Family on Windows and several UNIX hosts.

2.2 Note about Filenames

Members of the CrossView Pro family of debuggers use the following name convention for their executables:

2.3 Installation for Windows

1. Start Windows (95/98/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.

The CrossView Pro debugger simulator version is part of the TASKING tools package, so no separate installation is required. If you want to use a hardware execution environment you have to install the package in a preferred order (to prevent uninstall problems):
Please install the compiler tools first, then the debugger, and install them in the same directory. This procedure has the advantage that the device drivers for the hardware can be uninstalled successfully; the compiler package can be removed manually.

If your target execution environment is the ADS RedCap for the DSP5665x family, and you already have CrossView Pro installed for another ADS execution environment, you must first uninstall CrossView Pro before installing this version. It is also possible to install both device drivers, but then you need two ADS I/O cards in your PC, mapped to different addresses.

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. 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.

8. License the software product as explained in section 2.7, Licensing TASKING Products.

2.3.1 Requirements

The hardware/software requirements are:

2.4 Installation for UNIX Hosts

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 debugger (By default it will be installed in /usr/local).

2. 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 manual pages 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:

3. For CD-ROM install: go to the directory on which the CD-ROM is mounted:

For tape install: copy the contents of the tape to the temporary workspace using the following commands:

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.

4. Run the installation script:

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.7, Licensing TASKING Products.

If the script detects that the software has been installed before, the following messages appear on the screen:

Answering n (no) to this question causes installation to abort and the following message being displayed:

Answering y (yes) to this question causes installation to continue. And the final message will be:

For the DSP5600x the directory c56 will be created. For the DSP563xx/DSP566xx this directory will be c563.

5. For tape install: remove the temporary installation directory with the following commands:

6. Make sure that the directory containing the installed executable files is present in the PATH environment variable.

7. If you purchased a protected TASKING product, license the software product as explained in section 2.7 , Licensing TASKING Products.

X Windows is required to run CrossView Pro.

2.5 Configuring the X Windows Motif Environment

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:

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):

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.

2.6 Using X Resources

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).

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.

2.7 Licensing TASKING Products

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).

Node-locked license (PC only)

This license type locks the software to one specific PC so you can use the product on that particular PC only.

Floating license

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.

2.7.1 Obtaining License 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.

Node-locked license (PC only)

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.7.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.

Floating license

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.7.7, How to Determine the Hostid and section 2.7.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.

2.7.2 Installing Node-Locked Licenses

Keep your "License Information Form" ready. If you do not have such a form read section 2.7.1, Obtaining License Information, before continuing.

Step 1

Install the TASKING software product following the installation procedure described in section 2.3, Installation for Windows.

Step 2

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.7.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.7.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.

2.7.3 Installing Floating Licenses

Keep your "License Information Form" ready. If you do not have such a form read section 2.7.1, Obtaining License Information, before continuing.

Step 1

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:

Step 2

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.7.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).

Step 3

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).

Step 4

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.7.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.7.6 , Modifying the License File Location, for additional information.

Step 5

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.7.6, Modifying the License File Location, for more information.

Step 6

Now all license infomation is entered, the license manager must be started (see section section 2.7.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):

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.

Where to go from here?

The license manager (daemon) must always be up and running. Read section 2.7.4 on how to start the daemon and read section 2.7.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.

2.7.4 Starting the License Daemon

The license manager (daemon) must always be up and running. To start the daemon complete the following steps on each license server:

Windows

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.

UNIX

1. Log in as the operating system administrator (usually root).

2. Change to the FLEXlm installation directory (default /usr/local/flexlm):

3. For C shell users, start the license daemon by typing the following:

Or, for Bourne shell users, start the license daemon by typing the following:

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.

2.7.5 Setting Up the License Daemon to Run Automatically

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:

Windows

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.

UNIX

In performing any of the procedures below, keep in mind the following:

SunOS4

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):

SunOS5 (Solaris 2)

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):

3. Make it exacutable:

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:

num must be an approriate sequence number. Refer to you operating system documentation for more information.

2.7.6 Modifying the License File Location

The default location for the license file on Windows is:

On UNIX this is:

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:

Example UNIX:

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:

See Appendix A , Flexible License Manager (FLEXlm), for detailed information.

2.7.7 How to Determine the Hostid

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 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.

2.7.8 How to Determine the Hostname

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 2-2: Determine the hostname


Copyright © 2002 Altium BV