SSHAFT Setup

BWRC
Home

SSHAFT
Home

User
Guide

  This page lists the steps which need to be taken to set up your UNIX and Windows NT environments to use the SSHAFT design flow. 

• Exceed

• Matlab

  • Library Path Setup

  • Using the Xilinx System Generator

• UNIX

  • Copying the dot-files

  • Sourcing the setup script

  • Setting the DISPLAY variable

Exceed

Tools such as Cadence Design Planner and Synopsys Design Analyzer seem to have trouble with some versions of Exceed.  To avoid these problems, it's best to use the Exceed version 6.1.0.19 executable available in \\HITZ\Tools\Exceed61.nt\exceed.exe (no need to re-install Exceed).  You may want to create a desktop shortcut to this executable.

Once you have Exceed 6.1.0.19 running, right click on the icon in the toolbar and choose Tools-> Configuration.  The following settings work well:

• Screen Definition -> Server Visual = Pseudo Color
• Performance -> System Resource Usage =10 (Dynamic Adjust checked)
• Performance -> Draft Mode (checked)
• Performance -> Batch Requests (checked)
• Performance -> Save Unders (unchecked)
• Performance -> Maximum Backing Store = When Mapped
• Performance -> Default Backing Store = When Mapped
• Performance -> Minimum Backing Store = None

Matlab

The entry point for the SSHAFT flow is Simulink, which is an add-on package to Matlab.  We are currently transitioning from using the 5.x (R11) version to the 6.x (R12) version.  Users of the flow should run 5.x (R11) and follow the library path-setup instructions below.  Developers should run 6.x (R12) and follow the additional instructions for setting up the Xilinx System Generator.

Library Path Setup

Users The SSHAFT fundamental libraries must be added to your Matlab search path.  Do this with one of the following commands:

• Windows NT:  
      path(path,'\\HITZ\designs\sshaft\lib\icmake\mdl\R11\');
• UNIX: 
      path(path,'/tools/sshaft/lib/icmake/mdl/R11');

In order to automatically load the supported libraries, create a file called startup.m in the directory where you normally start Matlab.  This file should contain the line listed above.

If you want to configure the Windows NT version of Matlab to start in your NT home directory, modify the properties of the shortcut on your desktop.  Set the "Start  In" text box to "U:\[username]" (assuming that U: is mapped to \\HITZ\Users)

Using the Xilinx System Generator

The easiest way to run Matlab 6.x (R12) with the Xilinx System Generator is to login to the Windows 2000 terminal server beehive with the Terminal Services Client.  This client should be available through the start-menu on most workstations.  If not, you can install it by double-clicking the "Terminal Services Client.msi" file in \\HITZ\dist\Terminal Services Client.

Once the client is installed, run it and connect to beehive in the WIRELESS domain.  Login and run Matlab 6.1.  The Xilinx System Generator should already be installed.

UNIX

Before you can use the any of the UNIX back-end flow, you must first be a member of the appropriate UNIX group.  Talk to Gary Kelson (gkelson@eecs.berkeley.edu) about signing the NDA and Kevin Zimmerman (kwz@eecs.berkeley.edu) about being added to the ST technology group.

Copying the dot-files

Our group uses a utility which copies certain initialization files to your home directory which are tailored for a specific technology.  This allows the group to have a uniform design environment but makes customization difficult.  Follow these simple steps to set up your environment for the supported design flow:

1. You will need to create a symbolic link in your home
   directory to the system-wide initialization file directory:
   
       ln -s /tools/cds99/local/setup/cdsdot/   ~/.cdsdot
   
   Note that this command will return "permission denied" if
   the link already exists.
   

2. Source the setup script corresponding to the desired technology.  As of February 2002, only 0.18 is supported.
   

   Technology	Setup command
   ST 0.13 um (HCMOS7)	source /tools/cds99/local/setup/sft0st013_setup.csh.swap
   ST 0.18 um (HCMOS8D)	source /tools/cds99/local/setup/sft0st018_setup.csh.swap

   The script will notify you that it is over-writing the initialization files (dotfiles) every time your source it.  Your environment is now set up to run the SSHAFT design flow.

Sourcing the setup script

The script above can be added to your .cshrc file, but if you do not wish your dot-files to be overwritten each time you log in, simply source the script with the same name, minus the .swap extension.  For example, use the following command with the ST 0.25 um (HCMOS7 technology):

source /tools/cds99/local/setup/sft0st018_setup.csh

This script sets environment variables and adds new directories to your path.  Beware of "Ridiculously long path truncated" warnings when you source the script.  You may not be able to utilize the entire flow if you get these warnings.

Setting the DISPLAY variable

You may have problems routing if you set the DISPLAY environment variable in your .cshrc or .login file.  Some users set the DISPLAY environment variable at login time with the parenthost command.  Since the router (IC Craftsman) is invoked through a remote procedure call, the DISPLAY variable will be set incorrectly, causing IC Craftsman to crash.  This problem can be avoided in one of the following two ways:

1. Remove the DISPLAY settings from your .cshrc or .login file.  You may instead create a simple alias to set the DISPLAY variable.

2. Turn off the graphics when routing.