Specman Elite

Installation Guide
Specman Elite 4.3.4
Legal Notice
Copyright © 1998-2004 Verisity Design, Inc. All rights reserved.

Trademarks
Verisity, the Verisity logo, eAnalyzer, eCelerator, eRM, Invisible Specman, LicenseE,
Pure IP, Specman, Specman Elite, SpeXsim, SpeXtreme, SureCov, SureLint, SureSolve,
sVM, Verification Advisor, Verification Alliance, Verification Vault, Verification
Viewport, Visualization Toolkit, vManager, vPlan, Xbench, Xchange, Xcite, Xoc, Xpert,
Xsim, and Xtreme are either trademarks or registered trademarks of Verisity Design, Inc.
in the United States and/or other jurisdictions. All other trademarks are the exclusive
property of their respective owners.

Confidentiality Notice
Verisity confidential, do not distribute. The contents of this document constitute valuable
proprietary and confidential property of Verisity Design, Inc. No part of this information
product may be reproduced, transmitted, or translated in any form or by any means,
electronic, mechanical, manual, optical, or otherwise without prior written permission
from Verisity Design, Inc.

Information in this product is subject to change without notice and does not represent a
commitment on the part of Verisity. The information contained herein is the proprietary
and confidential information of Verisity or its licensors, and is supplied subject to, and may
be used only by Verisity’s customers in accordance with, a written agreement between
Verisity and its customers. Except as may be explicitly set forth in such agreement,
Verisity does not make, and expressly disclaims, any representations or warranties as to the
completeness, accuracy, or usefulness of the information contained in this document.
Verisity does not warrant that use of such information will not infringe any third party
rights, nor does Verisity assume any liability for damages or costs of any kind that may
result from use of such information.

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in
subparagraphs (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.227-7013.

Destination Control Statement

All technical data contained in this product is subject to the export control laws of the
United States of America. Disclosure to nationals of other countries contrary to United
States law is prohibited. It is the reader’s responsibility to determine the applicable
regulations and to comply with them.
Contents

1 About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

1.1 Conventions in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2 Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

2.1 Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1.1 Required Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.2 Required License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.3 Downloading the Installation Files from the Verification Vault . . . . . . . . . . . 2-2
2.2 Running the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.3 Extending Your Installation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

3 Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

3.1 Complete Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Install eRM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3 Change Default Backward Compatibility Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4 Install Patches or a Non-eRM Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.5 Uninstall an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.6 Customize Initialization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.7 Link Specman with Your Simulator(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.8 Install the License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.8.1 Installing the License Server and Setting the License File . . . . . . . . . . . . . . . 3-6
3.8.2 Updating Your License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.8.2.1 Automatically Updating the FLEXlm License Server with the Latest
Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.8.2.2 Updating the FLEXlm License Server Manually . . . . . . . . . . . . . . . 3-7

Installation Guide iii

Contents

3.9 Install the Specman Documentation and Verification Advisor . . . . . . . . . . . . . . . . . . . 3-8

3.9.1 Installing the HTML Help System with Specman . . . . . . . . . . . . . . . . . . . . . . 3-8
3.9.2 Installing the PDF Documentation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.9.2.1 Hyperlinks in the PDF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.9.3 Installing the HTML Help System Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

4 Environment and GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4.1 System Environment Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Customizing the Initialization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

5 Supported Platforms and Third-Party Tools . . . . . . . . . . . . . . . . . .5-1

5.1 Updates for This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.3 Supported Simulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.4 Supported Waveform Viewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.5 Other Supported Third Party Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

A Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A.1 License Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
A.2 Installation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

iv Installation Guide
1 About This Book
The Specman Elite® verification system is the Verisity® test bench automation tool. The Specman Elite
system, which can run stand-alone or integrated with an HDL simulator, automates many of the common
tasks involved in building the test environment and test suite, including writing tests, checking stimulus
and timing protocols, and collecting functional test metrics.

The Specman Elite Installation Guide explains how to install the Specman Elite verification system and
the installation options.

1.1 Conventions in This Book

This manual uses visual cues to help you locate and interpret information easily. These cues are
explained in Table 1-1.

Table 1-1 Document Conventions

Visual Cue Represents

courier The Courier font indicates e or HDL code. For example, the following line
indicates e code:
keep opcode in [ADD, ADDI];

courier bold In examples that show commands and their results, Courier bold indicates the
commands. For example, the following line shows the usage of the load
command:
vrst-tool> load test1

Installation Guide 1-1

About This Book
Conventions in This Book

Table 1-1 Document Conventions (continued)

Visual Cue Represents

bold The bold font indicates keywords in descriptive text. For example, the following
sentence contains the keyword “commands”:

You can enter multiple -commands arguments. Specman Elite executes the
commands in their usage order.

italic The italic font represents user-defined variables that you must provide. For
example, the following line instructs you to type the “write cover” as it appears,
and then the actual name of a file:

write cover filename

[ ] square Square brackets indicate optional parameters. For example, in the following
brackets construct the keywords “list of” are optional:

var name: [list of] type

[ ] bold brackets Bold square brackets are required. For example, in the following construct you
must type the bold square brackets as they appear:

extend enum-type-name: [name,…]

construct, … An item, followed by a separator (usually a comma or a semicolon) and an

ellipsis is an abbreviation for a list of elements of the specified type. For
example, the following line means you can type a list of zero or more names
separated by commas.

extend enum-type-name: [name,…]

| The | character indicates alternative syntax or parameters. For example, the

following line indicates that either the bits or bytes keyword should be used:

type scalar-type (bits | bytes: num)

% Denotes the UNIX prompt.

C1>, C2>, … Denotes the SpeXsim prompt (VHDL, Verilog, or mixed -HDL designs).

> Denotes a third-party VHDL simulator prompt.

vrst-tool> Denotes the prompt for the Verisity tool you are running, including
Specman Elite, vManager, SpeXsim, or SpeXtreme.

1-2 Installation Guide

2 Installation Process
This chapter explains how to install Specman Elite.

This chapter includes:

• “Preparing for Installation” on page 2-1

• “Running the Installation Script” on page 2-3
• “Extending Your Installation Environment” on page 2-4

See Also
For details on installation options, see Chapter 3 “Installation Options”.

For details on customizing your system environment, initialization file, or graphical user interlace, see
Chapter 4 “Environment and GUI”.

For details about supported platforms, simulators, and third-party tools, see Chapter 10 “Supported
Platforms and Third-Party Tools”.

2.1 Preparing for Installation

This section includes:

• “Required Disk Space” on page 2-2

• “Required License File” on page 2-2
• “Downloading the Installation Files from the Verification Vault” on page 2-2

Installation Guide 2-1

Installation Process
Required Disk Space

2.1.1 Required Disk Space

Specman Elite requires approximately 175 MB of disk space. The online documentation, which includes
both the Specman Elite manuals and the Verification Advisor, requires approximately an additional 70
MB.

2.1.2 Required License File

To run the Specman Elite verification system, you need a FLEXlm license file from Verisity. Verisity
emails this file to you. You can save the license file in “${SPECMAN_HOME}/license/verisity.lic” or
in any other directory on your system.

See Also
• “Install the License” on page 3-5

2.1.3 Downloading the Installation Files from the

Verification Vault
1. Open the following website:
www.verificationvault.com

2. Log in to the Verification Vault.

Note If you have not previously registered with the Verification Vault, do so by clicking on the
“Register here” link.

3. Under “software downloads”, choose the software version that you want to download.

4. Follow the instructions provided.

2-2 Installation Guide

 Installation Process
Running the Installation Script

2.2 Running the Installation Script

Figure 2-1 Installation Script Main Screen

>> S P E C M A N E L I T E I N S T A L L A T I O N S C R I P T <<
---------------------------------------------------------------------------------------------
To install Specman Elite for the first time or to install Specman Elite
on an additional platform, select option 1.
Note: Throughout this script, you can press Enter for default selections.
Select one of the following options:
1) Complete installation
2) Install eRM packages
3) Change default backward compatibility settings
4) Install patches or a non-eRM package
5) Uninstall an installation
6) Customize initialization file
7) Link Specman Elite with your simulator(s)
8) Install the license
9) Install the Specman Elite Documentation and Verification Advisor
10) Exit
Your selection:

To run the installation script:

1. Log in to a machine of the OS type on which you are installing Specman Elite.

For example, if you are installing on Solaris, log in to a Solaris machine.

2. Change to the directory containing the tar files.

For example:
% cd /opt

3. Run the installation script via the Bourne shell.

% sh ./install_specman<x.x>.sh
The installation script main screen appears (see Figure 2-1).
Note If you have already installed Specman Elite, you can also start the installation script from the
${SPECMAN_HOME}/install directory.
% ${SPECMAN_HOME}/install/install_specman.sh

Installation Guide 2-3

Installation Process
Extending Your Installation Environment

4. Enter the number of the desired installation option. Then follow the on-screen instructions,
providing appropriate answers to questions. (For details on each of the installation options, see
Chapter 3 “Installation Options”.)

2.3 Extending Your Installation Environment

The install_specman.sh script and its associated link scripts create a baseline environment that is
suitable at the start of a verification project, when you are focused on creating and debugging e code. As
your environment develops, you might want to compile your debugged e code on top of Specman Elite
or link in other tools, such as waveform viewers, C code, or Denali memory models. In that case, the
install_specman.sh script and the standard link scripts may not meet all your needs.

See Also
For more information on these compilation and linking needs, please refer to the following documents:

• Chapter 2 “Compiling and Linking Overview” in the Specman Elite Integrator’s Guide
• “The Compilation and Linking Interface” on page 2-3 in the Specman Elite Integrator’s Guide
• Chapter 10 “Using a Waveform Viewer” in the Specman Elite Integrator’s Guide,which covers these
topics:
• “Overview of Waveform Viewers Usage” on page 10-2
• Chapter 7 “Analyzing Coverage” in the Usage and Concepts Guide for e Testbenches, or, more
specifically:
• “Compiling and Linking Specman with SureCov” on page 7-75
• Chapter 11 “Using the C Interface” in the Usage and Concepts Guide for e Testbenches
• Chapter 11 “Co-Verification with Seamless CVE” in the Specman Elite Integrator’s Guide, or, more
specifically:
• “Running Specman Elite with Seamless” on page 11-10
• Chapter 12 “Using the Co-Verification Link (CVL)” in the Usage and Concepts Guide for e Testbenches,
or, more specifically:
• “Makefile Example” on page 12-19
• Chapter 13 “Using the Specman Denali Interface” in the Usage and Concepts Guide for e Testbenches,
or, more specifically:
• “Compiling and Linking SNDI with Simulators” on page 13-45

2-4 Installation Guide

3 Installation Options
This chapter explains the various installation options.

This chapter includes:

• “Complete Installation” on page 3-1

• “Install eRM Packages” on page 3-3
• “Change Default Backward Compatibility Settings” on page 3-3
• “Install Patches or a Non-eRM Package” on page 3-3
• “Uninstall an Installation” on page 3-5
• “Customize Initialization File” on page 3-5
• “Link Specman Elite with Your Simulator(s)” on page 3-5
• “Install the License” on page 3-5
• “Install the Specman Elite Documentation and Verification Advisor” on page 3-8

See Also
For details on the installation process, see Chapter 2 “Installation Process”.

For details on customizing your system environment, initialization file, or graphical user interface, see
Chapter 4 “Environment and GUI”.

3.1 Complete Installation

Choose this option if you want to:

• Install a new version of Specman Elite. (It does not matter if you have a previously installed version.)

Installation Guide 3-1

Installation Options
Complete Installation

• Install Specman Elite for an additional platform.

Complete installation lets you install the following:

• Full Specman Elite verification system (both platform-independent and platform-specific files)
• Specman Elite license (optional)
• eRM packages (optional)
• Specman Elite web-based Help system, which includes the Specman Elite manuals, Verification
Advisor, and e Reuse Methodology (eRM) Developer Manual (optional)
• Linking of Specman Elite with simulator(s) (optional)
• Configuration of default backward compatibility settings (optional)
• Patches to change the behavior of the Specman Elite executable (optional)

Notes
• All optional elements in a complete installation can be done at a later time by choosing the relevant
option on the installation script main screen.
• The PDF documentation tar file (sn_reln.n.pdf.docs.tar.gz) is not installed as part of a full installation.
Install the PDF documentation after a full installation, as described in “Install the Specman Elite
Documentation and Verification Advisor” on page 3-8.

See Also
The following sections describe the individual options provided on the main menu for the installation
script:

• “Install eRM Packages” on page 3-3

• “Change Default Backward Compatibility Settings” on page 3-3
• “Install Patches or a Non-eRM Package” on page 3-3
• “Uninstall an Installation” on page 3-5
• “Customize Initialization File” on page 3-5
• “Link Specman Elite with Your Simulator(s)” on page 3-5
• “Install the License” on page 3-5
• “Install the Specman Elite Documentation and Verification Advisor” on page 3-8

3-2 Installation Guide

 Installation Options
Install eRM Packages

3.2 Install eRM Packages

Choose this option if you want to install the eRM packages.

To use eRM, you must install the evc_util package. Other packages are optional.

To install only evc_util:

• When prompted by the Installation script, provide the full path to evc_util_top.e:
$SPECMAN_HOME/erm_lib/evc_util/e/evc_util_top.e

To install evc_util and some additional eRM packages:

1. Create an e file that imports the top file for evc_util (evc_util_top.e) and the top file for each of the
other packages that you want to compile into Specman Elite.

2. When prompted by the Installation script, provide the full path to the e file that you created in Step 1.

Note You can also make eRM available for selected runs by either loading it on top of Specman Elite
or compiling it on top of Specman Elite as user code. For more information, see “Installing eRM” on page
6-2 in About This Specman Elite Release.

For details on eRM, see the e Reuse Methodology (eRM) Developer Manual.

3.3 Change Default Backward Compatibility

Settings
Choose this option if you want to change one or more of the default 3.3 backward compatibility settings
for the Specman Elite executable.

Note You can still override these default compatibility settings before invoking Specman Elite or
before loading or compiling e files.

See Also
For details on the 3.3 backward compatibility options and how to use them as well as any other known
compatibility issues, see “Upgrading from Version 3.3” on page 8-30 and, in particular, “Setting
Compatibility Flags” on page 8-34 in About This Specman Elite Release.

3.4 Install Patches or a Non-eRM Package

Patches are e files containing code that changes the behavior of the Specman Elite executable.

Non-eRM packages include:

Installation Guide 3-3

Installation Options
Install Patches or a Non-eRM Package

• Tar files containing additional or updated libraries or scripts

• Other supplementary material
Choose this option if you want to:

• Add a non-eRM package to enhance an existing Specman Elite installation.

• Install a patch or patches to change the behavior of the Specman Elite executable of an existing
installation.
Patches are installed on top of an existing installation, creating a new executable named “specman”
in the $SPECMAN_HOME/OS directory. It is not possible to install a patched executable anywhere
but in the $SPECMAN_HOME/OS directory or with any name but “specman”.
Before installing a patch, test the patch to verify that it solves your problem. To do so, load or
compile the patch on top of Specman Elite, as required by the instructions that come with the patch.
Then run a simulation to check that the problem is solved.

To install a patch or a non-eRM package:

1. Place the patch or non-eRM package file in a directory (for example, /cad/verisity/patches).

Note If you want to install multiple patches, create an e file that imports all of the patches, because
you can install only one patch file at a time. When the installation script prompts you for the patch
pathname, you can specify the e import file.

2. Invoke the Installation script and select Option 3 “Install patches or a non-eRM package”.

Tip You can also install patches during a full installation (Option 1).

3. Follow the instructions given by the script.

You will be prompted for the full path to the patch or package file, for example,
/cad/verisity/patches/patches_tip.e.
When the installation is complete, a new executable named “specman” is created.

4. Check that all the patches are installed by:

a. Launching the new “specman” executable.

b. Entering the show patch command at the vrst-tool> prompt.

5. Relink the new “specman” executable with the simulators you use.

Tip You can uninstall all of your patches by specifying an empty e file as your patch file. The empty
file should contain:
<'
'>

3-4 Installation Guide

 Installation Options
Uninstall an Installation

3.5 Uninstall an Installation

You can have multiple installations of Specman Elite on your disk.

Choose this option if you want to remove an installation of Specman Elite from your disk.

3.6 Customize Initialization File

Choose this option if you want to customize the initialization files for an existing Specman Elite
installation.

Note You can customize compiling and linking options by editing the initialization file. For more
information, see “Customizing Compilation” on page 2-30 and “Customizing Linking” on page 2-34 in the
Specman Elite Integrator’s Guide.

See Also
For more information on the initialization files, see “Initialization Files” on page 7-25 in the Specman
Elite Integrator’s Guide.

3.7 Link Specman Elite with Your Simulator(s)

Specman Elite can run stand-alone or integrated with an HDL simulator.

Choose this option if you want to:

• Link an existing Specman Elite installation with your simulator(s).

• Set the environment for integration of Specman Elite with your simulator(s).

See Also
• Chapter 2 “Compiling and Linking Overview” in the Specman Elite Integrator’s Guide

3.8 Install the License

Typically, installation of the license or upgrade of the license server and tools (if required) is done as part
of a complete installation (see “Complete Installation” on page 3-1). However, you can also do it by
choosing this option.

Choose this option if you want to:

• Install the license server for an existing Specman Elite installation.

Installation Guide 3-5

Installation Options
Installing the License Server and Setting the License File

• Set the license file for an existing Specman Elite installation.

• Update your FLEXlm license server and tools.
This section describes:

• “Installing the License Server and Setting the License File” on page 3-6
• “Updating Your License Server” on page 3-6
Note If you need help getting your Verisity license file or have questions regarding the Verisity license,
please email [email protected].

3.8.1 Installing the License Server and Setting the License

File
As mentioned in “Required License File” on page 2-2, you need a FLEXlm license to run Specman Elite.
You can use this option either to install the license server or to set the SPECMAN_LICENSE_FILE
environment variable in the env.sh and env.csh scripts if the license server is already installed.

When installing the license server:

• The script creates a new license file based on the license file you obtained from Verisity via email
• Activates the license server
• Updates the SPECMAN_LICENSE_FILE environment variable
• Optionally creates the rc.specman file.

3.8.2 Updating Your License Server

If you are running an earlier version of the FLEXlm license server than is required for a particular
release, you must update the server.

If you used the Specman Elite install scripts to install the FLEXlm license server, then the installation
script should be able to start the new license daemon automatically. If you choose not to upgrade
automatically or if the automatic upgrade fails, you must start the new license daemon manually.

Note Whether you update automatically or manually, this update shuts down your license server for a
short period. During that time, new Specman Elite invocations suspend and other applications that use
the same license server may also be affected.

3-6 Installation Guide

 Installation Options
Updating Your License Server

3.8.2.1 Automatically Updating the FLEXlm License Server with the

Latest Daemon
1. Start the Specman Elite installation script and choose the menu option 6) Install the license.

2. Choose menu option 4) Update your license server and tools automatically.

After you respond to some license-related prompts, the installation script shuts down your old
license daemon and starts the new one. Then, the installation script completes the installation
process.
Note If you do not see options 4 and 5 on the license installation menu and you have not yet
upgraded your FLEXlm license daemon to version 7.2, the installation script failed to detect your
current license and therefore assumes that this is a new installation rather than an upgrade. In that
case, you must specify your Specman Elite license file by choosing menu option 2) Set
SPECMAN_LICENSE_FILE. Thereafter, the installation script will re-present the license
installation menu with options 4 and 5.

3. Edit your UNIX boot scripts as needed to ensure that they start the new license daemon. You may
use the rc.specman script created by the installation for starting the daemon. If necessary, consult
your system administrator for assistance.

This completes the automatic update process.

3.8.2.2 Updating the FLEXlm License Server Manually

1. On a UNIX terminal, shut down your old Specman Elite license server with the command:
lmdown -c your_license_file

2. Update your license server to the version found in $SPECMAN_HOME/license/platform. If

necessary, consult your system administrator for assistance.

3. Start the new daemon with the command:

lmgrd -c your_license_file
Verify that the started verisityd is version 7.2.

4. Return to the Specman Elite installation terminal and press Enter to resume the installation process.

5. Edit your UNIX boot scripts as needed to ensure that they start the new license daemon. If necessary,
consult your system administrator for assistance.

This completes the manual update process.

Installation Guide 3-7

Installation Options
Install the Specman Elite Documentation and Verification Advisor

See Also
For more information on FLEXlm licensing tools, see the FLEXlm End Users Guide at
http://www.macrovision.com/solutions/esd/support/enduser/TOC.htm.

3.9 Install the Specman Elite Documentation and

Verification Advisor
Choose this option if you want to install the:

• Specman Elite HTML browser-based Help system

Release tar file: sn_reln.n.docs.tar.gz
• Optional full-book PDF documentation files
Release tar file: sn_reln.n.pdf.docs.tar.gz

Both the HTML Help system and the PDF documentation include:

• The Specman Elite manuals

• Verification Advisor
• e Reuse Methodology (eRM) Developer Manual.
This section describes the following:

• “Installing the HTML Help System with Specman Elite” on page 3-8
• “Installing the PDF Documentation Files” on page 3-9
• “Installing the HTML Help System Locally” on page 3-9

3.9.1 Installing the HTML Help System with Specman Elite

During a full installation, you are prompted to install the Specman Elite documentation and Verification
Advisor. If you respond “yes”, the HTML Help system is installed with the Specman Elite software.

You can also choose to install the HTML Help system at a later time, after installing the Specman Elite
software. To do so, run the installation script and select option 9, as described in “Installing the PDF
Documentation Files”.

3-8 Installation Guide

 Installation Options
Installing the PDF Documentation Files

3.9.2 Installing the PDF Documentation Files

To install the full-book PDF documentation files:

1. Ensure that the PDF tar file sn_reln.n.pdf.docs.tar.gz has been downloaded for installation.

You can downloaded sn_reln.n.pdf.docs.tar.gz from the Verification Vault

(www.verificationvault.com) software downloads page.

2. Run the installation script and select option 9, Install the Specman Elite Documentation and
Verification Advisor.

The script prompts you for the path to the documentation tar files.

3. Enter the path to the PDF tar file.

The script lists the documentation tar files available at the path you enter. For example, if both 4.2
documentation tar files were available at the path you enter, the script would prompt you:
Please select the upgrade version:
1) 4.2
2) 4.2.pdf
3) None of the above

Your selection:

4. Enter the option number that identifies the PDF tar file (option 2 in the example above).

5. Respond to the remaining prompts, which ask you for the path to the Specman Elite home directory
and for permission to install the documentation files.

The installation script installs the PDF files in the $SPECMAN_HOME/docs/pdf_docs directory.

3.9.2.1 Hyperlinks in the PDF Files

As long as you leave the PDF files in the installed directory structure (each manual in a separate
directory), the hyperlinks between the PDF manuals will work. If you move the PDF files, the links
between manuals will be broken.

3.9.3 Installing the HTML Help System Locally

The Specman Elite HTML Help system is platform-independent and can be installed locally on your
machine for viewing in Netscape Navigator or Internet Explorer.

To install the Help locally:

1. Copy the $SPECMAN_HOME/docs/online_help directory to your local machine.

Installation Guide 3-9

Installation Options
Installing the HTML Help System Locally

The $SPECMAN_HOME/docs/online_help directory is created when you install the

documentation with the installation script.

2. Open the file online_help/VerisityHelp.htm in your web browser.

3-10 Installation Guide

4 Environment and GUI
This chapter explains how to adjust your system environment, initialization, and graphical user
interface.

This chapter includes:

• “System Environment Scripts” on page 4-1

• “Customizing the Initialization File” on page 4-2

See Also
• For details on the installation process, see Chapter 2 “Installation Process”.
• For details on installation options, see Chapter 3 “Installation Options”.
• For information about customizing Specview, see “Customizing Specview” on page 2-16 in Usage
and Concepts Guide for e Testbenches.

4.1 System Environment Scripts

During installation, Specman Elite modifies the system environment scripts so that you can use the
scripts to set up a working user environment. There are two scripts, one for Bourne shell or ksh (env.sh)
and one for C shell or tcsh (env.csh). These scripts are located in ${SPECMAN_HOME}.

If you use a different script to set up your environment, be sure it sets all the environment variables and
the path with similar results.

These scripts do the following:

• Sets the SPECMAN_HOME environment variable to install-dir/sn-release-number.

• Sets your path to include the path to the Specman Elite executable.

Installation Guide 4-1

Environment and GUI
Customizing the Initialization File

• Sets SPECMAN_LICENSE_FILE to the path to the Specman Elite license.

• Sources the ld_env.[c]sh file for your platform.
The ld.[c]sh scripts do the following:

• Depending on the operating system, sets the appropriate library path environment variable:
Solaris LD_LIBRARY_PATH
HP-UX SHLIB_PATH
Linux LD_LIBRARY
AIX LIBPATH

Setting the shared library path ensures that the simulator will find all the shared libraries at run time,
when it is linked with Specman Elite.
• Issues a warning that the library path environment variable has been modified.

4.2 Customizing the Initialization File

The standard initialization file is ${SPECMAN_HOME}/system.specman. This file is modified
automatically during installation, based on the choices you make.

For full control of initialization, you can keep a private copy of the initialization file. In the local
initialization file, you can define only those entries you want to change. Any entry not defined in the
local file is taken from ${SPECMAN_HOME}/system.specman.

On invocation Specman Elite looks for a .specman file in two places:

• The current directory

• The $HOME directory
The system.specman initialization file is split into two parts:

• The first part defines any machine-independent variables. This part can only be changed manually.
• The second part defines machine-dependent variables, such as compilation variables and the scripts
and simulation interface files used to link Specman Elite with a simulator. These variables can only
be set during the installation process.

Notes
• Avoid changing the second part of the initialization file manually. Any manual editing in the second
part can cause errors during automatic updates of the initialization file.

4-2 Installation Guide

 Environment and GUI
Customizing the Initialization File

• The Specman Elite initialization files require standard Bourne shell syntax. When changing the first
part of the initialization file or when creating a local .specman file, white spaces are not allowed in
assignments:
LICENSE_QUEUEING=yes // is valid
LICENSE_QUEUEING = yes // is not valid

See Also
For more information, see UNIX man pages for ‘sh’.

For more information on the machine-independent variables in the first part of the initialization file, see
“Setting Up the Specman Elite Environment” on page 7-24 in the Specman Elite Integrator’s Guide.

For more information on the compilation and linking variables and scripts, see Chapter 2 “Compiling and
Linking Overview” in the Specman Elite Integrator’s Guide.

Installation Guide 4-3

Environment and GUI
Customizing the Initialization File

4-4 Installation Guide

A Troubleshooting
This appendix includes:

• “License Troubleshooting” on page A-1

• “Installation Troubleshooting” on page A-2

A.1 License Troubleshooting

Error Possible Cause/Solution
%>specman Cause 1: Invalid License File.
%>**** Fatal error - leaving Specman:
%>Specman: Never acquired license Cause 2: Corrupted file, lmcksum failed.
%>
Solution: Request a new license file by sending
email to [email protected].
Invalid path to verisityd daemon Detect by lmstat, (Vendor daemon line contains
error message)
Port number already in use SERVER Solution:
carmel 7200499a 7320
1. Look for message “port in use” in lmgrd log
(The port number in this case is 7320) file (created by installer).

2. Change the port number in the first line of

the license file.
No permission to invoke remote shell Solution 1: Add remote host to ~/.rhosts file list.
(from install_specman.sh) Solution 2: Run install license script on the
license server as the user who owns the license.

Installation Guide A-1

Troubleshooting
Installation Troubleshooting

Error Possible Cause/Solution

Inappropriate Specman version Look for outdated lines in the license file. For
example:
%> cat $SPECMANLICENSE_FILE | grep
“FEATURE specman”
FEATURE specman verisityd 3.3
1-jan-01 100
1BDC30A193FDC53C0C96 ck=60

Solution: Obtain a new license.

Note The sim_specman feature must refer to

the correct version.

A.2 Installation Troubleshooting

Error Possible Cause/Solution
tar ‘HELP’ error message Resources exhaustion, such as lack of disk space or memory.

Look for: “tar:...’HELP’....” message during extraction (in

terminal).

Solution: Free up additional resources before installation.

For example:
%> rm -rf <junk-dir>

Error during extraction Clean the disk and reactivate installer.

Compiler and compiler Modify the init file (system.specman) and re-invoke the
flags problem: installer using the “link with simulator” option.
gcc/cc not installed on
destination machine

A-2 Installation Guide

 Troubleshooting
Installation Troubleshooting

Error Possible Cause/Solution

Self Test Failed After linking Specman Elite with a simulator, the install script
runs the appropriate XOR example in the install_dir/examples
directory to verify that the linking was successful. If the test
fails, it is usually due to environment problems. Check
variables settings (for Specman Elite & simulator) after
sourcing env.csh.

For example, check that LD_LIBRARY_PATH is set

correctly.
Licensing problems: No Look for “FEATURE xl_specman inspec...” line in license
license for sim_specman file.
Link with Simulator Failed Cause 1: Native home variable not set correctly (for example,
CDS_INST_DIR).

Solution:

1. Set native home variable.

2. Re-invoke installer.

3. Select link Specman Elite with simulator option.

Cause 2: Selected simulator version does not match user

environment.

Look for the link script version in the compilation output. For
example:
link_xl97B.sh - matches xl 97B

Cause 3: Incomplete simulator installation.

The simulator should work without Specman Elite before

linking it with Specman Elite.

Installation Guide A-3

Troubleshooting
Installation Troubleshooting

A-4 Installation Guide

Index

A F
AIX files
versions and simulators, supported 5-1 PDF documentation tar file 3-3
system.specman 4-2
B FLEXlm
required version 3-6
backward compatibility, default, setting 3-3
H
C
Help system
Cadence Design Systems installing 3-8
supported simulators 5-2 installing locally 3-9
compatibility, backward, default settings 3-3 HP-UX
compilation versions, supported 5-1
customizing 3-5
I
D
initialization file
Denali interface customizing 4-2
versions, supported 5-3 installation 2-1
documentation backward compatibility, default settings 3-3
conventions 1-1 complete installation 3-1
customizing the initialization file 3-5
E disk space required 2-2
env.csh script 4-1 environment scripts 4-1
env.sh script 4-1 environment variables, setting 4-1
environment variables environment, extending 2-4
setting during installation 4-1 initialization file
eRM packages, installing 3-3 customizing 4-2
installation script

Installation Guide Index-1

Index

options 3-1 patches

running 2-3 installing 3-3
license file 2-2 PDF documentation
installing 3-5 hyperlinks in 3-9
troubleshooting A-1 installing 3-9
linking simulators 3-5 PDF documentation for Specman Elite 3-3
online documentation, installing 3-8 platforms, supported 5-1
packages, eRM 3-3
packages, non-eRM 3-3 Q
patches 3-3
preparing for 2-1 Quickturn
troubleshooting A-2 supported simulators 5-2
self test A-3
uninstalling 3-5 R
upgrading 3-3 Red Hat Linux
versions, supported 5-1
L
license file 2-2 S
getting help for 3-5 Seamless co-verification
installing 3-5 versions, supported 5-3
license server Signalscan
upgrading 3-6 versions, supported 5-2
linking simulators
customizing 3-5 and waveform viewers, supported
combinations 5-3
M supported 5-2
Model Technology SimVision
supported simulators 5-2 versions, supported 5-2
ModelSim Solaris
versions, supported 5-2 versions, supported 5-1
Specman Elite
Help system
N installing 3-8
NC Simulator installing locally 3-9
versions, supported 5-2 installing 2-1
Novas Debussy license file 2-2
versions, supported 5-2 installing 3-5
Speedsim
P versions, supported 5-2
Synopsis
packages, eRM, installing 3-3 supported simulators 5-2
packages, non-eRM system environment scripts 4-1
installing 3-3
Index-2 Installation Guide
 Index

system.specman file 4-2

T
tools, third party, supported 5-3

U
Undertow
versions, supported 5-2

V
VCS
versions, supported 5-2
Verilog-XL
versions, supported 5-2
VirSim
versions, supported 5-2

W
waveform viewers
and simulators, supported combinations 5-3
Novas Debussy
versions, supported 5-2
waveform viewers, supported 5-2

Installation Guide Index-3