TROUBLESHOOTING

Troubleshooting
---------------

  ----------------------------------------------------------------------------
  Symptom:

    'icfb2' or other command gives this error in the UNIX shell:

    X Error of failed request:  BadName (named color or font does not exist)

  Solution:

    This usually means the XWindow manager on your local computer is either 
    not running or is missing fonts.  If you are using Xming, be sure it is
    running and also that the xming-fonts are installed 
    (http://sourceforge.net/projects/xming).   

  ----------------------------------------------------------------------------
  To resolve errors in netlists in LVS, we have set this UNIX environment 
  variable in the default 'cadence.cshrc' on the Instructional systems:

 setenv CDS_Netlisting_Mode Analog

  The CDS_Netlisting_Mode variable controls how component description format 
  (CDF) properties are interpreted during netlisting.  More information can 
  be found at 
  https://inst.eecs.berkeley.edu/~inst/pub/nis/?file=Cadence/compverref/appA.html

  [thanks to Eric Chin for this solution, Sep 19 2007]
  ----------------------------------------------------------------------------
  If a previous instance of a Cadence tool is still running, kill it using
  (for example):

    pkill -f icfb

  ----------------------------------------------------------------------------
  You can create a log of the Cadence tools activity in the local /tmp 
  directory by starting Cacence with the UNIX command:

 /share/b/bin/icfb2 -log  /tmp/${USER}.log  &

  ----------------------------------------------------------------------------
  If you run synergy with the -TEXT option, you'll see error messages that
  might otherwise be lost in windowing mode.

  ----------------------------------------------------------------------------
  Symptom:

    User's Cadence session appears to launch correctly (LSW show appropriate 
    layers, etc.), but when he draws shapes they don't appear in the window.  
    Using Ctrl+a for "select all" however shows that they are there, and are
    drawn on the correct layer.  These shapes can also be selected by drawing 
    a selection box around them, but they *cannot* be selected in the there, 
    and drawn on the correct layer.  These shapes can also be selected by
    drawing a selection box around them, but they *cannot* be selected in the
    normal way by clicking on them.  Also, markers from DRC checks, etc. do 
    not show up.  
   
  Solution:

    Be sure that the Window manager is set for "PseudoColor" (on PCs) or 
    PSEUDOCOLOR_VISUAL (on UNIX) as described above.

    If you have a previous, older version of the .cdsinit file in your UNIX 
    home directory or in your working directory, it may conflict with newer 
    settings (such as hot keys) that are set in
    /usr/eesww/cadence/setup/config/cadence.cshrc.  You can just delete your
    old .cdsinit files if you have not customized them.

    If you have a Cadence process already running on the UNIX computer you
    are logged into, kill it using:
   
 pkill -9 -f  cadence

    Start it again after updating your .cdsinit file(s).
  
  ----------------------------------------------------------------------------
  Symptom:

    'wrong authentication' error message.

   Cause:

     An X Windows program can't open a window on your workstation screen.

   Solution:

     See http://inst.eecs.berkeley.edu/connecting.html#xwindows
     for instructions about using X Windows on the Instructional computers.
  ----------------------------------------------------------------------------
  Symptoms:

    'wrong authentication' error message.
    Saved files are size 0.

  Causes:

    You are over your disk quota, which prevents X Windows and Cadence from
    writing files.

  Solution:

    Use our temporary expansion disk and create a symbolic link to it from your
    UNIX home directory so that Cadence can find it.   
  
    Example:   Say your login is "jdoe" and you have a Cadence project called 
    "Project1".  Here is how to put that project on the temporary disk space 
    so Cadence it will find it:

    1) Log into your Instructional UNIX account (jdoe@cory.eecs, etc).

    2) Create a directory for yourself on our temporary disk space:

         /home/tmp/mkhometmpdir

       See http://inst.eecs.berkeley.edu/share/b/pub/disk.quotas fo details.

    3) Create a symbolic link to it in your home directory:

         mkdir home/tmp/jdoe ~jdoe/tmp

       (If you already have a ~jdoe/tmp directory or file, you'll need to
       pick a different name.)

    4) Move the Project1 directory to the tmp space and make a sym link to 
       it for Cadence:
   mv ~jdoe/Project1 ~jdoe/tmp/Project1
   ln -s ~jdoe/tmp/Project1 ~jdoe/Project1
  ----------------------------------------------------------------------------
  Symptom:
   
     Error checking out licenses, such as
       *WARNING* feature ###: not available - NOT checked out

  Solution:

      'hostname' of your computer must match exactly (case-sensitive) the
      name as it's listed in /usr/eesww/share/cadence/admin/license/clients.

      Change one so it agrees with the other and restart the Cadence tools.
  ----------------------------------------------------------------------------
  Symptom:

    "Hot Keys" are not enabled.  

  Cause:

    The user is failing to load the expected "leBindKeys.il" file.

  Solution:

    See below for details about the "leBindKeys.il" file.   The directory in
    which you start cadence may have a .cdsinit or cds.lib file tbat is old
    or incorrect.  Make sure your cds.lib does not have
    
 INCLUDE /usr/eesww/cadence/local/cdssetup/cds.lib

    which is an obsolete reference.  There are current (Nov 2005) cds.lib 
    files in

 /usr/eesww/cadence/setup/config
 /usr/eesww/cadence/NCSU_CDK/cdssetup

  ----------------------------------------------------------------------------
  Symptom:

    "Hot Keys" are not enabled.  Unable to use R, or Ctrl-R, or i ,etc as 
    hotkeys for Rectangle, screen refresh, or Insert Instance.   Cadence 
    does not show the hotkeys in the menu, which should show

 | Reload R
 | Aim    A
 | Fire   F
 | Brush  B
 | Teeth  Ctrl-T

    The user needs to have the "leBindKeys.il" file loaded, which can be done
    by entering it into one of the .cdsinit startup files.  Cadence first 
    looks in $CDS_INST_DIR/tools/dfII/local/ then in ~/ and then in ./ .
    The .cdinit files contain many startup items including an instruction to 
    load the hotkeys files (e.g. leBindKeys.il).  
    
    But the current system local/.cdsinit file doesn't set the ACEHOME 
    environment variable and some NSCU variable, and it ends without looking 
    for other .cdinit files.  So the user can't load "leBindKeys.il".

  Solution:

    Users on Instructional systems should create their own .cdsinit files 
    that load "leBindKeys.il" and start Cadence from the directory that has 
    that file.   Also look for old ~/.cdsinit and ./.cdsinit files that are 
    incorrect.  You can create a new .cdsinit file on the Instructional
    systems by running '/share/b/bin/cadence-setup.csh'.

  ----------------------------------------------------------------------------
  Symptom:

    X connection to cory.EECS.Berkeley.EDU:10.0 broken \
    (explicit kill or server shutdown)

  Solution:

    This means you have logged into cory.EECS.Berkeley.EDU (for example) 
    and started an XWindows command (such as 'icfb') but you do not have 
    an XWindows server running on your desktop computer.  See
    http://inst.eecs.berkeley.edu/cgi-bin/pub.cgi?file=XWindows.help for
    more information.

  ----------------------------------------------------------------------------
  Symptom:
    
    Segmentation errors.

  Solution:

    This means there is a bug in the cadence software or the Operating System.
    Please email inst@imail.EECS.Berkeley.EDU the following information:

    the output of 
uname -a ; ssh -V ; java -fullversion ; date '+DATE:%a %d %b %Y TIME:%H:%M:%S'  ; dirs -v ; echo $PATH

  ----------------------------------------------------------------------------
  Symptom:
    
    You get errors like
    *WARNING* file /home/aa/users/jdoe/CDS.log.1 Malformed Lock-Stake file.
    *WARNING* file /home/aa/users/jdoe/CDS.log.2 Malformed Lock-Stake file.

  Solution:

    Delete obsolete lock files from a previous session.  The lock file names
    are determined by adding ".cdslck" to the name of the file in the error
    message.

    So for the file  /home/aa/users/jdoe/CDS.log.1 
    the lock file is /home/aa/users/jdoe/CDS.log.1.cdslck

    You can delete it with the UNIX command 

 rm /home/aa/users/jdoe/CDS.log.1.cdslck

    You can locate all of the Cadence lock files in your UNIX home directory
    with the command:

 find ~ -name \*cdslck

  ----------------------------------------------------------------------------
  Symptom:
    
    The "Help" button does not do anything.

  Solution:

    The Cadence "Help" buttons look specifically for a progam called "netscape",
    and it must be in the search path that Cadence is using.  An easy way to 
    ensure that is to create a sym link called "netscape" in a Cadence "bin"  
    directory that points to an actual WEB browser on your system.

  ----------------------------------------------------------------------------
  Symptom:
    
    Spectre fails with an error such as 

    ld.so.1: spectre: fatal: relocation error: ...
     symbol __SUNW_init_wiostreams: referenced symbol not found
     Killed

  Solution:

    See the "Cadence Spectre" section above.
  ----------------------------------------------------------------------------