Troubleshooting RFIC Dynamic Link

This chapter provides troubleshooting information that can help you resolve common problems is also provided in this appendix.

All errors, warnings, and other messages are directed to the Cadence CIW. When a new message is written to the CIW, the window is raised to the top of your window stack so that new messages are always visible. Error messages may also be logged in a file, idf.log.

Some known problems and solutions are listed in the following section. You may find this information helpful in determining how to resolve a particular problem however, if you're unable to resolve a problem with the RFIC Dynamic Link using the information provided, contact Agilent EEsof EDA customer support.

Known Problems and Solutions

Problem: By default, ADS does not create its own private color map, which may lead to unpredictable color behavior and/or menu buttons in place of icons.

Solution: Try one or more of the following:

  • Set HPEESOF_COLORMAP = private in the ADS configuration file $HOME/hpeesof/config/hpeesof.cfg or $HPEESOF_DIR/config/hpeesof.cfg .
  • Set CDS_NUM_USER_COLORS = 16 in your .profile or .cshrc file.
  • Restart Dynamic Link after exiting all other color-intensive applications.

Problem: When you remake a symbol, even when the old symbol is deleted, ADS does not allow you to create another symbol with the same name.

Solution: Click the instance in the ADS schematic window, then choose DynamicLink > Instance > Update Instance of Cellview . If the problem persists:

  • Delete the <lib> _ <cells> _ <view> symbol in the ADS Design.
  • Save the ADS design.
  • Exit ADS.
  • Delete all the <ADS_proj_dir> /networks/ <lib> _ <cells> _ <view> .* files.
  • Restart ADS.

Problem: *Error* Could not find `nlpglobals/ads' in library `basic'. The nlpglobals' cell view is required. Netlisting aborted. This error occurs either while netlisting in Analog Artist or after clicking Simulate in the ADS.

Solution: Copy the spectre view in the nlpglobals cell to create an ads view.

Problem: There is no distinction between a design variable X from Design A and a design variable X from a different Design B .

Solution: Use unique design variable names for different designs, unless you really intend them to be the same variable, in which case there's no problem.

Problem: Symbol generation via Cadence symbol duplication does not reproduce arcs.

Solution: Use line segments instead of arcs.

Problem: Could not spawn master program . This message appears in your parent terminal window upon attempting to use the ADS link.

Solution: Ensure that $ HPEESOF_DIR/ bin is in your PATH and that $ HPEESOF_DIR/ bin/idfmp is a valid executable. If this does not work, ask your UNIX System Administrator to reboot your system or otherwise determine if a socket address is in use.

Problem: The UNIX environment does not set up properly when an in-house script for DFII is used.

Solution: Starting DFII using an in-house script may not set up the UNIX environment properly for RFIC Dynamic link. Work with your System Administrator to ensure that you understand what environment variables need to be set in the in-house script and modify your script accordingly.

Installation and Use Checklist

This section provides a checklist that can be used to help you resolve problems with RFIC Dynamic Link. You can use the questions below to help determine what the cause of a particular problem might be.

 

Privacy Statement  | Terms of Use  | Legal | Contact Us  | © Agilent 2000-2008 

Contents
Additional Resources