Hier Editor

Cadence Hierarchy Editor User Guide
Product Version 5.0 September 2002
1990-2002 Cadence Design Systems, Inc. All rights reserved. Printed in the United States of America. Cadence Design Systems, Inc., 555 River Oaks Parkway, San Jose, CA 95134, USA Trademarks: Trademarks and service marks of Cadence Design Systems, Inc. (Cadence) contained in this document are attributed to Cadence with the appropriate symbol. For queries regarding Cadences trademarks, contact the corporate legal department at the address shown above or call 1-800-862-4522. All other trademarks are the property of their respective holders. Restricted Print Permission: This publication is protected by copyright and any unauthorized use of this publication may violate copyright, trademark, and other laws. Except as specied in this permission statement, this publication may not be copied, reproduced, modied, published, uploaded, posted, transmitted, or distributed in any way, without prior written permission from Cadence. This statement grants you permission to print one (1) hard copy of this publication subject to the following conditions: 1. The publication may be used solely for personal, informational, and noncommercial purposes; 2. The publication may not be modied in any way; 3. Any copy of the publication or portion thereof must include all original copyright, trademark, and other proprietary notices and this permission statement; and 4. Cadence reserves the right to revoke this authorization at any time, and any such use shall be discontinued immediately upon written notice from Cadence. Disclaimer: Information in this publication is subject to change without notice and does not represent a commitment on the part of Cadence. The information contained herein is the proprietary and condential information of Cadence or its licensors, and is supplied subject to, and may be used only by Cadences customer in accordance with, a written agreement between Cadence and its customer. Except as may be explicitly set forth in such agreement, Cadence does not make, and expressly disclaims, any representations or warranties as to the completeness, accuracy or usefulness of the information contained in this document. Cadence does not warrant that use of such information will not infringe any third party rights, nor does Cadence assume any liability for damages or costs of any kind that may result from use of such information. Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR52.227-14 and DFAR252.227-7013 et seq. or its successor.
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Typographic and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Cadence Hierarchy Editor Overview
............................ 9 11 11 13 16 16 17 17 18 18 18 20 22 22 24 25 25 26 26 26 28 29
What You Can Do with the Hierarchy Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Hierarchy Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Hierarchy Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Top Cell Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Bindings Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Bindings Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Instance Bindings Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Command-Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing Hierarchy Editor Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Attributes to Display in the Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Options Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resizing Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Conguration Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expanding and Collapsing Branches of Your Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Tree Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Cellviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the View Filters Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
September 2002
Product Version 5.0
Viewing the Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Hierarchy Editor Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Custom Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting the Hierarchy Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31 32 32 33
2 Creating Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
About the Conguration View of a Design Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening Congurations in Read-Only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Open Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering the Congurations in the Open Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Browser Filters Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the New Conguration Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Choose the Top Cell Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing the Cell Bindings and Instance Bindings Tables . . . . . . . . . . . . . . . . . . . . . . . Verifying Conguration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Description File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Cell Binding Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Explain Form for a Selected Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Instance Binding Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Explain Form for a Selected Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Occurrence Binding Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Explain Form for a Selected Occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Use Template Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying Your Created Template to Another Location . . . . . . . . . . . . . . . . . . . . . . . . . Saving Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving a Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Save As Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving VHDL Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 37 39 39 40 41 43 45 46 46 47 50 50 51 52 53 53 54 55 56 56 57 57 58 59 59 60 61
September 2002
Product Version 5.0
About the Save As VHDL Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Verilog Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Save As Verilog Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating a Virtuoso Schematic Composer Conguration Using the Hierarchy Editor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62 62 64 64
3 Changing Design Components
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 69 69 69 70 71 71 72 72 73 74 75 77 77 78 79 80 82 82 84 85 87 89 91 92 92 93 95
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Instance Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Occurrence Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How a Library Is Selected for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How a View Is Selected for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Rules at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening a View List at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening a Library List at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening a Stop List at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Rules at the Cell Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Library Bindings on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing View Bindings on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Stop Points on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Bind-to-Open on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Rules at the Instance Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing View Bindings on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Library Bindings on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . Dening Stop Points on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Bind-to-Open on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Instance Bindings Inside a Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Instance Bindings Created by a Generate Statement . . . . . . . . . . . . . . . . Dening Rules at the Occurrence Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Occurrences Are Different from Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Occurrence Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
September 2002
Product Version 5.0
Dening Occurrence Stop Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dening Occurrence-Level Bind-to-Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Binding Data Color Denitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Edit Constants Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Views in the View Choices List Box . . . . . . . . . . . . . . . . . . . . . . . . . . Using Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
102 103 105 106 106 108 109 110 110
4 Using Plug-Ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

About Plug-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Loading Plug-In Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Removing Plug-In Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
A The hierEditor.env File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
September 2002
Product Version 5.0
Preface
The Cadence Hierarchy Editor User Guide describes the Cadence Hierarchy Editor, which lets you browse a design hierarchy and create and edit design congurations. The preface discusses the following:
I I
Related Documents Typographic and Syntax Conventions
Related Documents
To nd information about other Cadence products that are used with the hierarchy editor, refer to the following manuals:
I
Virtuoso Schematic Composer User Guide describes how to use the schematic capture product. Cadence Design Framework II User Guide describes terms and how to start your system. Cadence AMS Environment User Guide describes the analog mixed signal environment.
Typographic and Syntax Conventions

This section describes typographic and syntax conventions used in this manual. text variable [ ] Indicates text you must type exactly as it is presented. Indicates text that you must replace with an appropriate value. Denotes optional arguments. When used with vertical bars, they enclose a list of choices from which you can choose one. Used with vertical bars and encloses a list of choices from which you must choose one.
{ }
September 2002
Product Version 5.0
Cadence Hierarchy Editor User Guide Preface | text Separates a choice of options. Indicates that you can repeat the previous argument. Indicates names of manuals, menu commands, form buttons, and form elds.
September 2002
Product Version 5.0
1
Cadence Hierarchy Editor Overview
This chapter covers the following topics:
I I
What You Can Do with the Hierarchy Editor on page 11 Opening the Hierarchy Editor on page 11

About the Hierarchy Editor Menus on page 13 Using the Toolbar on page 16 Top Cell Section on page 16 Global Bindings Section on page 17 Cell Bindings Table on page 17 Instance Bindings Table on page 18 Messages on page 18 Status Bar on page 18
I I
Setting Command-Line Options on page 20 Customizing Hierarchy Editor Columns on page 22

Specifying Attributes to Display in the Columns on page 22 About the Options Form on page 24 Changing Column Order on page 25 Resizing Columns on page 25
I I
Updating the Conguration Automatically on page 26 Expanding and Collapsing Branches of Your Design on page 26
Displaying the Tree Structure on page 26
Filtering Cellviews on page 28

9 Product Version 5.0
September 2002
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

I I I I
About the View Filters Form on page 29
Viewing the Legend on page 31 Changing the Hierarchy Editor Fonts on page 32 Saving Custom Settings on page 32 Exiting the Hierarchy Editor on page 33
September 2002
10
Product Version 5.0
What You Can Do with the Hierarchy Editor

The Cadence Hierarchy Editor lets you view many levels of a single design using either a table view or a tree view. The hierarchy editor also lets you create a conguration le that provides expansion information for mixed-signal partitioning. A conguration le is the expand.cfg le, which species how a design is to be expanded. You can use the hierarchy editor to
I I I I I I I
Display the conguration le in order to traverse the hierarchy of your design Display default cell and instance bindings Change global library, view, and stop lists Change cell and instance bindings Change the inherited view list and library list for cells and instances Specify occurrence bindings Create new congurations
Opening the Hierarchy Editor

You can open the hierarchy editor from your Cadence application or from a UNIX shell.
To open the hierarchy editor from a UNIX shell, type

cdsHierEditor &
The Cadence hierarchy editor window appears. Note: When you start the hierarchy editor, you can also specify various options with the cdsHierEditor command. For more information on the options you can use, refer to
September 2002
11
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview Setting Command-Line Options on page 20.
Menu bar Toolbar Top cell information Global bindings section
Cell bindings section
Viewing area
Message area
Status bar
September 2002
12
Product Version 5.0
About the Hierarchy Editor Menus

The menu bar displays the hierarchy editor menus.
File Menu
File New creates a new conguration. File Open opens an existing conguration for editing. File Open (Read-Only ) opens a conguration for viewing. File Save (Needed) saves the opened conguration. File Save As saves the opened conguration under a new name. File Save As VHDL saves the opened conguration as a VHDL le. File Save As Verilog saves the opened conguration as a Verilog le. File Save Defaults saves your settings. Exit closes the hierarchy editor.
September 2002
13
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview Edit Menu
Edit Undo removes the last action. You can undo an unlimited number of actions. Edit Redo redoes the previously undone action. Edit Constants opens the Constants form to let you create or edit constants. Edit Description opens the Edit Description form to let you edit the description of the conguration. View Menu View menu commands let you set the display options for the hierarchy editor. You can hide the table, tree, top cell, global bindings, toolbar, message area, and status bar in the hierarchy editor window.
September 2002
14
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview View Update recomputes the hierarchy based on the rules you entered. This command is unavailable until you have opened a conguration. Note: You can also select the Automatic Update option, which is available in the Options form, to automatically update your conguration every time you make a change. View Tree displays cell or instance bindings in a tree structure. View Table displays cell or instance bindings in a table structure. View Instance Table displays the instance table. This option is not available when View Tree is selected. View Top Cell shows or hides the top cell information. View Global Bindings shows or hides the global library, view, and stop lists. View Toolbar shows or hides the toolbar. View Message Area shows or hides the message area. View Status Bar shows or hides the status bar. View Filters opens the View Filters form to let you set or edit display lters. View Options opens the Options form to let you select the columns you want to display in the hierarchy editor. The Options form also lets you set the Automatic Update option. You can save the display options to use when you restart the hierarchy editor. See Saving Custom Settings on page 32 for more information.
September 2002
15
Product Version 5.0
Using the Toolbar

You can access frequently used commands by clicking the icons on the toolbar (open, update, explain, undo, redo, and display the table or tree structure). You can move the toolbar to a separate window for easy access.
Create a new cong Open a cellview for editing Open a cellview for viewing Explain Table view
Save a cong Open a cong Undo Redo
Update Tree view Show/hide instance table
Click here and drag the mouse to dock and undock the toolbar
To undock the toolbar,
Click and drag the left edge of the toolbar to the location you want. A window appears with the toolbar in it.
To dock the toolbar,
Click and drag the left edge of the toolbar to any edge of the hierarchy editor window. Note: If you dock the toolbar outside the hierarchy editor window, it becomes a oating toolbar on your desktop.
Top Cell Section

The Top Cell section contains the library, cell, and view names of the top cellview of the conguration you opened. This is the root cellview of your hierarchy.
September 2002
16
Product Version 5.0
Global Bindings Section

The values in the library, view, and stop lists in the Global Bindings section are the default values from the conguration.
Library List is a list of libraries from which cells are selected. Libraries are listed in order of preference. View List is the list of views or default rules specied in order of preference. For example, if the view list contains the views tbench_1, schematic, and dataflow in this order, the netlister rst looks for a tbench_1 view. If none is found, it looks for a schematic view. Again, if none is found, the netlister looks for a dataflow view. Stop List is the list of views used to determine when the hierarchy expansion will stop and when a cell should be considered a leaf node in the hierarchy.
Cell Bindings Table
Icon indicating top-level cell
The Cell Bindings table displays the views that are bound to a cell.
September 2002
17
Product Version 5.0
Instance Bindings Table

Maximize button Minimize button
The Instance Bindings table displays all the instances in the block you selected and their bindings. Instances are described in a library-cell-view format. Use the maximize button to expand the Instance Bindings table and the minimize button to contract the table.
Messages
The message area near the bottom of the window displays error and warning messages and information for hierarchy editor actions. Scroll bars appear if the window is not large enough to display the full message.
Status Bar
The status bar at the bottom of the window displays the state of the hierarchy editor, whether filters are on or off, and the name space in which you are operating. When you position the
September 2002
18
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview cursor over a menu item or toolbar icon, the status bar tells you what will happen if you click on the item or icon.
September 2002
19
Product Version 5.0
Setting Command-Line Options

When you run the hierarchy editor from the command line, you can specify the following options. Syntax
cdsHierEditor [-h[elp]] [-lib libname ] [-cell cellname ] [-view viewname ] [-mode {r|w|a}] [-namespace nmpName ] [-cdslib filepath ] [-log filename ] [-mpshost host ] [-mpsession session ] [-restore dirname ] [-tree] [-version] [-ignoreRootConfig] [-plugin pluginName [pluginOptions ...]]
Note: If you use the -plugin option, you must specify it as the last argument. The hierarchy editor ignores all arguments after -plugin, except another -plugin argument. Arguments
-h[elp] -lib libname -cell cellname -view viewname
Prints a list and a brief description of the command-line options. Species the library name of the conguration to be opened. Species the cell name of the conguration to be opened. Species the view name of the conguration to be opened. You must specify all three parts of the -lib, -cell, and -view options for the command to be complete.
September 2002
20
Product Version 5.0
-mode {r|w|a}
Species the mode (read, write, or append) the hierarchy editor uses to open the conguration. The default mode is append. Note: The -mode w (write) option erases all data in the conguration le you specify and opens the empty conguration le.
-namespace nmpName
Species the name space to operate in, for example, Verilog, VHDL, or CDBA . All names are then displayed in that name space, regardless of the source description that is used. The default name space is CDBA. Species the cds.lib le to load. The cds.lib le species the libraries to use. Species the path and name of a log le in which commands and messages are recorded. If you do not specify this option, no log le is created. Species the Message Passing System (MPS) host on which the cdsNameServer is running and to which you want to connect. If the host is not specied, the hierarchy editor connects to the local host. Species which MPS session to join. Loads the hierEditor.env le from the specied directory after other hierarchy editor les (found with the Cadence File Search facility) have been loaded. Indicates that the tree view is to be displayed at startup. If this argument is not specied, the table view is displayed. Prints the version and copyright information and exits. Ignores the root conguration in select and highlight messages between the hierarchy editor and Cadence Design Framework II (DFII) applications. By default, if you are not editing the same root conguration in your DFII application and the hierarchy editor, select and highlight messages between the two applications are ignored. If you set the -ignoreRootConfig option, the hierarchy editor ignores the root conguration.
-cdslib filepath -log filename
-mpshost host
-mpssession session -restore dirname
-tree
-version -ignoreRootConfig
September 2002
21
Product Version 5.0
-plugin pluginName [pluginOptions ...]
Loads the plug-ins you specify. You can specify command-line options for the plug-ins. To load more than one plug-in, type -plugin before each plug-in name. If you use the -plugin option, you must specify it as the last argument. The hierarchy editor ignores all arguments after -plugin, except another -plugin argument. For more information about plug-ins, see Chapter 4, Using Plug-Ins. Note: The plug-ins you specify must be installed in the your_install_dir /share/cdssetup/ hierEditor/plugins directory.
Customizing Hierarchy Editor Columns

The hierarchy editor lets you specify the attributes you want to display in the columns, change the column order, and resize the columns.
Specifying Attributes to Display in the Columns

To specify the attributes you want to display in the columns, 1. From the main menu, choose View Options .
September 2002
22
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview The Options form appears.
2. Click a tab for displaying a specic set of related attributes. For example, to select the attributes you want to display in the tree structure, click the Tree tab. 3. Select the attributes you want to display. To select the default attributes, click Defaults . 4. Click OK to apply your changes and close the form.
September 2002
23
Product Version 5.0
About the Options Form

The Options form lets you specify the attributes you want to display in the cell table, instance table, and tree view of the hierarchy editor. It also lets you specify the automatic update option. The Cell Table tab lets you select the columns that appear in the cell table. Show Cell Columns Info displays information about the cellview. For example, a triangle in this column indicates the top-level cell view. For a complete list of icons that can be displayed in this column and their meanings, choose Help Legend to display the Legend dialog box. View to Use displays a eld in which you can type a specic view to use for the cell. Inherited View List displays a eld in which you can modify the inherited view list for the cell. The default inherited view list is the global view list. Inherited Lib List displays a eld in which you can modify the inherited library list for the cell. The default inherited library list is the global library list. The Instance Table tab lets you select the columns that appear in the instance table. Show Instance Columns Info displays information about the instance. For example, a triangle in this column indicates the top-level cell view. For a complete list of icons that can be displayed in this column and their meanings, choose Help Legend to display the Legend dialog box. View to Use displays a eld in which you can type a specic view to use for the instance. Inherited View List displays a eld in which you can modify the inherited view list for the instance. Inherited Lib List displays a eld in which you can modify the inherited library list for the instance. The Tree tab lets you select the columns that appear in the tree structure. Show Tree Columns View to Use displays a eld in which you can type a specic view to use for the cell.
September 2002
24
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview Inherited View List displays a eld in which you can modify the inherited view list. Inherited Lib List displays a eld in which you can modify the inherited library list. Expand Mode By Instance displays all the instances for the selected cell when you expand a branch. By Instance Grouping displays similar instances grouped together when you expand a branch. The number of instances is displayed. The General tab lets you set the following option: Automatic Update updates the conguration automatically every time you make a change. If this option is selected, you do not have to click the Update icon in the toolbar or choose View Update to recompute the hierarchy or view your changes. OK applies your selections and closes the form. Cancel closes the form without applying your selections. Defaults resets the values to their defaults. Help opens this manual.
Changing Column Order

You can change the order of the columns in the table view or tree view. For example, you can have the Cell column appear before the Library column. To move a column,
Drag the column heading to where you want the column to appear, then release the mouse.
Resizing Columns
You can change the width of any column by dragging the inside edge of its heading. To resize a column, 1. Click on the right edge of the column heading border. 2. Drag the border to the right to widen the column or drag the border to the left to narrow the column.
September 2002 25 Product Version 5.0
Updating the Conguration Automatically

You can set an option to update the conguration automatically whenever you make a change. For example, if you open a conguration and add a view to the global view list, the hierarchy editor will automatically recompute the hierarchy and display the updated bindings. If you do not set the automatic update option, you need to click the Update icon or choose View Update to view the changes you make. The default setting of the automatic update option is off. To update congurations automatically, 1. From the menu bar, choose View Options . The Options form appears. 2. Select the General tab. 3. Select Automatic Update . 4. Click OK . The Options form closes.
Expanding and Collapsing Branches of Your Design

You can use the expansion icon to view the hierarchy of a design. The expansion icon is one of the following: UNIX NT [+] [-] Meaning Item contains instances not shown. The substructure is hidden (collapsed or locked). Item contains instances that are shown. The substructure is displayed (expanded or unlocked). Item is a leaf cellview with no instances below it.
Displaying the Tree Structure

The tree view displays the hierarchy of your design. To display the tree view,
From the menu bar, choose View Tree , or from the toolbar, select the Tree View icon.
To expand the structure for a collapsed cellview, do one of the following:

Click the expansion icon for the item. Double-click on the item.
To collapse the structure for an expanded cellview, do one of the following:

Click the expansion button for the item. Double-click on the item.
The following example illustrates the expansion of the poa poa sch_1cellview in the tree structure.
September 2002
27
Product Version 5.0
Filtering Cellviews
You can nd cellviews quickly by using lters. To lter cellviews, 1. Choose View Filters . The View Filters form appears.
2. In the Library, Cell , and View elds, specify whole words or character strings to narrow your cellview search. You can use the following wildcards:
Character ? [list ] [lower - upper ] *
Match Criteria Matches any single character Matches any single character in list Matches any character in the range between lower and upper Matches any pattern
September 2002
28
Product Version 5.0
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview For example, to nd all the libraries that begin with p, in the Library eld, type p*. Pattern matching is case sensitive. You can also specify multiple patterns by separating the patterns with spaces. 3. Select the type of data (for example, items at the leaf level or unbound items) you want to see by selecting one or more of the following options:

Show leaf instances and cellviews Show instances and cellviews that are not bound Only show entries that have an explicit rule
4. Click Apply. The status bar displays Filters ON . 5. Click OK . The changes you made are saved. The View Filters form closes and the hierarchy editor uses the selected lter criteria until you turn off the lters. Note: The lter setting returns to the default setting when you start another hierarchy editor session. You must save your settings using the File Save Defaults command to save the lter settings for future sessions.
About the View Filters Form

Library lets you specify the search criteria for library names. Cell lets you specify the search criteria for cell names. View lets you specify the search criteria for view names. For the Library, Cell , and View elds, you can:

Specify whole words or character strings Specify multiple patterns; separate the patterns with spaces Use the following wildcards: Matches any single character Matches any single character in list
? [list ]
September 2002
29
Product Version 5.0
[lower-upper ] *
Matches any character in the range between lower and upper Matches any pattern
Note: Pattern matching is case sensitive. Show leaf instances and cellviews lets you specify whether you want to display instances and cellviews that are at the leaf level. Show instances and cellviews that are not bound lets you specify whether you want to display unbound instances and cellviews. Only show entries that have an explicit rule lets you specify whether you want to display all entries or only those entries that have an explicit rule. OK applies your settings and closes the form. Cancel closes the form without saving any settings. Apply applies your settings and leaves the form open. Defaults restores the default match criteria and turns the lter off. The hierarchy editor displays all cellviews and instances. The status bar displays Filters OFF. Help opens this manual.
September 2002
30
Product Version 5.0
Viewing the Legend
The Legend dialog box provides information about the icons and colors that are used in the hierarchy editor user interface. To display the Legend dialog box,
From the menu bar, choose Help Legend .
You can customize the text colors. For more information, see Changing Binding Data Color Denitions on page 105.
September 2002
31
Product Version 5.0
Changing the Hierarchy Editor Fonts

The hierarchy editors fonts are determined by the settings in the cdsresource.properties le. The default fonts are dened in the cdsresource.properties le in the your_install_dir /share/cdssetup/ symphony/resources directory. You can have multiple cdsresource.properties les. The hierarchy editor determines which le to use based on the search order dened in the setup.loc le. To change the hierarchy editor fonts, 1. Copy the following le to a directory that is in your setup.loc le (for example, your $HOME directory or current working directory):
your_install_dir /share/cdssetup/symphony/resources/cdsresource.properties
2. Modify the font settings in the new cdsresource.properties le. The font settings are dened by the CDS.textFont property, which has the following format:
CDS.textFont=fontName fontStyle fontSize
For example:
CDS.textFont=courier plain 12
3. Restart the hierarchy editor. For more information about how the hierarchy editor determines which cdsresource.properties le to use, see Chapter 3, "Cadence Setup Search File: setup.loc," of the Cadence Application Infrastructure User Guide.
Saving Custom Settings

When you exit the hierarchy editor, your settings are not automatically saved. You can save your settings with the Save Defaults form. You can save and restore the following settings:
I I I
The height and width of the hierarchy editor window The location of the hierarchy editor window on the screen The lter settings
September 2002
32
Product Version 5.0

I
The view options to show or hide the toolbar, status bar, message area, or the Global Bindings, Cell Bindings, and Instance Bindings sections The size of the instance table, tree structure, and message area The columns that are displayed The hierarchy editor form values Plug-in settings
I I I I
To save your current settings, 1. Choose File Save Defaults . The Save Defaults form appears:
2. Type the path to the directory in which you want to save the settings. 3. Click OK . The information is saved in the hierEditor.env le in the directory you specied. The next time you start the hierarchy editor, it loads the hierEditor.env le. If the hierEditor.env le is not in a directory that is found by the Cadence search mechanism, you can load the le by starting the hierarchy editor with the -restore dirname command. For more information about the hierEditor.env le, see Appendix A, The hierEditor.env File.
Exiting the Hierarchy Editor

To close the hierarchy editor, 1. Choose File Exit or press Control-q . The hierarchy editor closes.
Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview If you have not saved the conguration changes you have made, a Warning form asks you whether you want to save your changes. 2. On the Warning form, click one of the following:

Yes to save your changes and exit No to discard your changes and exit Cancel to dismiss the form without exiting
Note: The Exit command closes only the hierarchy editor. It does not close other applications with which the hierarchy editor might have been communicating.
September 2002
34
Product Version 5.0
2
Creating Configurations
I
About the Conguration View of a Design Hierarchy on page 37

Opening Congurations on page 37 Opening Congurations in Read-Only Mode on page 39 About the Open Form on page 39 Filtering the Congurations in the Open Form on page 40 About the Browser Filters Form on page 41
Creating a New Conguration on page 43

About the New Conguration Form on page 45 About the Choose the Top Cell Form on page 46
Editing Congurations on page 46
Editing the Cell Bindings and Instance Bindings Tables on page 47
Verifying Conguration Data on page 50

Viewing the Description File on page 50 Verifying Cell Binding Rules on page 51 About the Explain Form for a Selected Cell on page 52 Verifying Instance Binding Rules on page 53 About the Explain Form for a Selected Instance on page 53 Verifying Occurrence Binding Rules on page 54 About the Explain Form for a Selected Occurrence on page 55
Working with Templates on page 56

September 2002
Cadence Hierarchy Editor User Guide Creating Congurations

I
Using Templates on page 56 Creating Templates on page 57 Copying Your Created Template to Another Location on page 58
Saving Congurations on page 59

Saving a Conguration on page 59 Saving VHDL Congurations on page 61 Saving Verilog Congurations on page 62 Updating a Virtuoso Schematic Composer Conguration Using the Hierarchy Editor Interface on page 64
September 2002
36
Product Version 5.0
About the Conguration View of a Design Hierarchy

The conguration view of a design is the denition that the hierarchy editor understands and can open. It is a cellview that stores a conguration le that contains the libraries, cells, and views of a design. You can browse
I
The library directory, which contains a collection of cells that correspond to a specic process technology The cell directory, which contains the design object that forms an individual building block of a chip or system The view, which is a dened representation of a cell such as layout or a schematic
The main components of a conguration are the top cellview, which is the root of the design and the conguration rules. designLib pulsegen
Library name
Top cell name View name
schematic
layout
mixedCong
logicCong
In the above example, the designLib library contains two conguration denitions identied by the view names mixedConfig and logicConfig. You can use the hierarchy editor to open the mixedConfig or the logicConfig conguration.
Opening Congurations
To open an existing conguration when you start the hierarchy editor,
In a UNIX window, type

cdsHierEditor -lib libname -cell cellname -view viewname
All of the above options must be specied for the hierarchy editor to open a conguration and load the data.
Cadence Hierarchy Editor User Guide Creating Congurations If you do not specify a cellview (library, cell, and view names) when you run the cdsHierEditor command, the hierarchy editor opens without loading a conguration. Note: A cellview is the library, cell, and view names. To open a conguration from the hierarchy editor, 1. From the menu bar, choose File Open or press Control-o. The Open form appears.
2. If you want the Browse section of the form to display only a specic set of libraries, cells, and views, click Filters and type your search criteria in the Browser Filters form. 3. In the Browse section, select the name of the library where your design is located, or type the name in the Library field. The libraries are displayed in outline form. The cds.lib le is at the top of the design hierarchy. The libraries dened in the cds.lib le are at the next level, the cells are a level below the libraries, and the views are a level below the cells. For more information about Cadence library structures, refer to the Cadence Application Infrastructure User Guide . The selected library name appears in the Library eld.
September 2002
38
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations 4. Click the expansion icon for the library, then select the cell you want. The selected cell name appears in the Cell eld. 5. Click the expansion icon of the cell, then select the view you want. Note: The browser displays only conguration views and expands only those cells that contain conguration views. The selected view name appears in the View eld. 6. When all the elds in the form are lled, click OK . The hierarchy editor displays your data in the Top Cell , Global , and Cell Bindings sections. Note: Cadence Design Framework II (DFII) users can use the libSelect application to open congurations in the hierarchy editor. You must enable libSelect by setting the compatibility mode in the hierEditor.env le. For more information on the hierEditor.env le, refer to Appendix A, The hierEditor.env File.
Opening Congurations in Read-Only Mode

To open a conguration in read-only mode from the hierarchy editor, 1. From the menu bar, choose File Open (Read-Only) . The Open (Read-Only) form appears. 2. Refer to the steps in Opening Congurations on page 37. The conguration is opened but cannot be edited. If the hierarchy editor cannot open a conguration, an Open Error dialog box appears.
About the Open Form

Configuration Library lets you type the name of a library specied in your cds.lib le. You can also ll in this eld by selecting a library in the Browse section. Cell lets you type the name of the cell you want to open. You can also ll in this eld by selecting a cell in the Browse section. View lets you type the name of the conguration view you want to open. You can also ll in this eld by selecting a view in the Browse section.
September 2002
39
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations Browse lets you select the library, cell, and view. The library, cell, and view that you select are displayed in the Library, Cell , and View text elds in the Configuration section. Note that the browser displays only conguration views and expands only those cells that contain conguration views. You can set lters to display only a specic set of libraries, cells, and views in the Browse section. See Filtering the Congurations in the Open Form on page 40 for more information. OK opens the conguration you selected and closes the form. Cancel cancels the selections and closes the form. Filters opens the Browser Filters form that lets you specify search criteria to display only parts of the library structure that match your lter criteria. Help opens this manual.
Filtering the Congurations in the Open Form

You can set lters to display only a specic set of libraries, cells, and views in the Browse section of the Open form. 1. In the Open form, click Filters . The Browser Filters form appears.
2. In the Library, Cell , and View elds, specify whole words or character strings to narrow your search.
September 2002
40
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations You can use the following wildcard characters:
Character ? [list ] [lower - upper ] *
Match Criteria Matches any single character Matches any single character in list Matches any character in the range between lower and upper Matches any pattern
For example, to nd all the libraries that begin with p, in the Library eld, type p*. Pattern matching is case sensitive. You can also specify multiple patterns by separating the patterns with spaces. 3. Click OK . The changes you made are applied and the Browser Filters form closes. The hierarchy editor refreshes the display in the Browse section of the Open form, based on the lters you set. Note: To return to the default lter settings, in the Browser Filters form, click Defaults .
About the Browser Filters Form

Library lets you specify the search criteria for library names. Cell lets you specify the search criteria for cell names. View lets you specify the search criteria for view names. For the Library, Cell , and View elds, you can:

Specify whole words or character strings Specify multiple patterns; separate the patterns with spaces Use the following wildcards:
?
September 2002
Matches any single character

[list ] [lower-upper ] *
Matches any single character in list Matches any character in the range between lower and upper Matches any pattern
Note: Pattern matching is case sensitive. OK sets the search criteria and closes the Browser Filters form. Cancel closes the form without saving your selections. Apply sets the search criteria for libraries, cells, views, and views but does not close the form. Defaults restores the default settings. Help opens this manual.
September 2002
42
Product Version 5.0
Creating a New Conguration

Use these steps to create and use a conguration with the hierarchy editor:
Open a new conguration le Dene a global library list Dene a global view list Dene a global stop list Specify cell bindings Specify instance bindings Update the conguration cellview Save the conguration cellview le Open or reopen the application where the design was generated
Run your application Check results Verify the conguration cellview No OK? Yes Quit the hierarchy editor required optional
To create a new conguration, 1. Open the hierarchy editor. The hierarchy editor window appears. 2. Choose File New or press Control-n .
September 2002
43
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations The New Conguration form appears.
3. In the Top Cell section, do one of the following:
In the Library, Cell , and View elds, type the name of the library, cell, and view that you want to use as the top cellview of your design. Click Browse and select the top cellview from the Choose the Top Cell form.
4. In the Global Bindings section, do one of the following:
In the Library List, View List, and Stop List elds, type a library list, view list, and stop list to specify the default bindings for the entire design. The global library list is a list of libraries that determines the libraries from which each cell is obtained. The global view list is a list of views that determines which view is selected for each object in the design. The global stop list species a list of views that are to be treated as leaf nodes, that is, they are not to be expanded. List the libraries and views in the order of preference. Separate entries with spaces.
September 2002
44
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations You can use constants in the view list and stop list. A constant is a symbolic name used to represent a set of views. For more information on creating and using constants, refer to Using Constants on page 106. The Stop List eld can be empty.
Click Use Template to select a template that is compatible with the simulator you are running. Templates for simulators provide lists of views that are most often used for those simulators. Refer to Working with Templates on page 56 to use prepared templates or to create your own templates. Note: If the template you selected has lled in the Top Cell section of the New Conguration form, replace the names in the Library, Cell , and View elds with the top cellview you want to use.
5. (Optional) In the Description eld, type a brief statement describing the new conguration. 6. Click OK . The New Conguration form closes. The hierarchy editor displays the new conguration. See Saving Congurations on page 59 for information about saving your new conguration.
About the New Conguration Form

Top Cell species the cell at the highest level of the conguration, the top cellview. Library species the name of the library that contains the top cellview. Cell species the cell name of the top cellview. View species the view name of the top cellview. Browse opens the Choose the Top Cell form for selecting the top cellview of the conguration. Global Bindings specify default bindings for the entire design. Library List lets you specify libraries for cells that do not have library bindings. List the libraries in the order you want them searched. View List lets you specify the views you want in your conguration in order of preference. The view list applies to every level of the conguration and determines which
September 2002
45
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations view is selected for every object in the design, unless overridden by a cell or instance binding. Stop List lets you specify cellviews that are to be treated as leaf nodes, that is, they are not to be expanded. This eld can be empty. Description lets you enter a brief statement describing the conguration. OK sets the values you entered and closes the form. Cancel closes the New Conguration form without applying your values. Use Template lets you select a template from a list of predened templates. Help opens this manual.
About the Choose the Top Cell Form

Top Cell Library lets you specify the name of the library that contains the cell at the highest level of the conguration, the top cellview. Cell lets you specify the cell name of the top cellview of the conguration. View lets you specify the view name of the top cellview of the conguration. Browse lets you select the top cellview of the conguration. The library, cell, and view you select are displayed in the Library, Cell , and View text elds in the Top Cell section. OK sets the values you entered and closes the form. Cancel cancels your selections and closes the form. Filters displays the Browser Filters form that lets you specify search criteria to display only parts of the library structure. Help opens this manual.
Editing Congurations
This section provides an overview of how to edit a conguration. For a more detailed description on how to make changes and specify rules for congurations, see Chapter 3, Changing Design Components..
Cadence Hierarchy Editor User Guide Creating Congurations Note: You cannot edit sub-congurationsa sub-conguration is a conguration that is contained within a conguration. To edit a sub-conguration, you must open it separately as a conguration in the hierarchy editor. To edit a conguration using the hierarchy editor, 1. Open the conguration you want to edit. 2. Edit the conguration.
In the Top Cell section, edit the library name, cell name, or view name of the top cellview of the conguration. In the Global Bindings section, edit the library list, view list, and stop list. Separate the entries in the lists with spaces. Note: Library bindings in CDBA are xed and cannot be overridden. If your data is CDBA (DFII only), the hierarchy editor ignores any library list you enter in the Global Bindings section. Note: The view list that applies to the root cellview of the design cannot be edited. In the Cell Bindings table, the root cellview is identied with a green triangle in the Info column, if the Info column is displayed.
Edit the Cell Bindings and Instance Bindings sections.
3. Choose View Update to see the results of your changes in the Cell Bindings or Instance Bindings sections. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. Note: Updating the display is optional, but you must save the information to be able to use the edited conguration. 4. Click File Save or press Control-s . Note: Other Cadence software tools cannot access new or changed conguration les until they have been saved.
Editing the Cell Bindings and Instance Bindings Tables

Changing Cell or Instance View Bindings 1. In the Cell Bindings or Instance Bindings section, select the cell or instance you want to change.
September 2002
47
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations 2. Do one of the following:
Click in the View to Use column of the cell or instance, type the new view, then press Return. Right-click anywhere in the row of the cell or instance you want to change and select a view from the list of views in the pop-up menu.
The new view appears in the View to Use column in the color used to display user bindings. 3. Choose View Update to see the results of your changes. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 4. To save the changes, choose File Save or press Control-s . Adding Views to Cell or Instance Bindings To add a new view, 1. In the Cell Bindings or Instance Bindings section, click in the Inherited View List column and move the cursor to the end of the list. 2. Type the name of the view you want to use. Separate entries with spaces. 3. Press Return . The modied view list appears in the Inherited View List column in the color used to display user bindings. 4. To view your changes, choose View Update . If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 5. To save the changes, choose File Save or press Control-s . Deleting Views from Cell or Instance Bindings You can remove any views from the cell or instance bindings. To remove a view,
September 2002
48
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations 1. In the Cell Bindings or Instance Bindings section, select the cell or instance you want to change. 2. In the Inherited View List column, double-click on the view you want to remove. The view becomes highlighted. 3. Press Delete . 4. To view your changes, choose View Update . If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 5. To save the changes, choose File Save or press Control-s . Viewing Instances Contained by Other Instances To see instances contained by other instances, 1. Choose View Tree to display the tree view of the hierarchy editor. 2. Right-click on the instance you want to browse. A pop-up menu appears. 3. Select Expand Instance . The hierarchy below the instance is displayed. To collapse an expanded instance, 1. Right-click on the name of the expanded instance. A pop-up menu appears. 2. Select UnExpand Instance . The hierarchy below the instance is collapsed. Performing a Global Change on a Group of Instances To perform a global view change on a group of instances, you can display all instances that share the same rules, 1. Choose View Options . The Options form appears.
September 2002
49
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations 2. Select the Tree tab. 3. In the Expand Mode section, select By instance grouping . 4. Click OK . 5. Choose View Tree to display the tree view of the hierarchy editor. 6. Select the group of instances that you want to change. 7. Click in the View to Use column and type the name of the new view for the group of instances. 8. Press Return . The view you selected is applied to all the instances and appears in the color used to display user bindings. 9. To see the results of your changes, choose View Update . If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 10. To save the changes, choose File Save or press Control-s .
Verifying Conguration Data

You can check the conguration data of your design in the following ways:
I I
Viewing the Description File Seeing what binding rules were used to select any view in the hierarchy. You can do this by

Verifying Cell Binding Rules Verifying Instance Binding Rules Verifying Occurrence Binding Rules
Looking at the structure of the hierarchy using the table or the tree structure.
Viewing the Description File

To view the description le,
Choose Edit Description .
September 2002
50
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations The Edit Description form appears.
Description displays a description of the conguration, which you can edit. OK applies the changes you made and closes the form. Cancel cancels the changes you made and closes the form. Help opens this manual. To edit the description of your conguration, 1. In the Edit Description form, edit the description in the Description eld. 2. Click OK . The hierarchy editor saves the edited description.
Verifying Cell Binding Rules

To see which binding rules were used for a cell, do one of the following:
I
In the Cell Bindings table, right-click on a cellview and, from the pop-up menu, select Explain . In the Cell Bindings table, select a cellview and, from the toolbar, click the Explain icon.
September 2002
51
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations The Explain form appears.
About the Explain Form for a Selected Cell

Selection displays the master cellview for the selected cell Library species the master library of the cell. Cell species the master cell of the cell. View species the master view of the cell. Note: If the Library, Cell , or View elds display **UNBOUND**, the cell has a bind-toopen attribute. Instantiations lists all the cellviews where the selected cell is used. Explanation describes the bindings for the selected cell. Close closes the form.
September 2002
52
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations Help opens this manual.
Verifying Instance Binding Rules

To see which binding rules were used for an instance, do one of the following:
I
In the Instance Bindings table, right-click on the instance whose rules you want to check and, from the pop-up menu, select Explain . In the Instance Bindings table, select the instance and, from the toolbar, click the Explain icon.
The Explain form appears.
About the Explain Form for a Selected Instance

Selection displays the cellview that contains the selected instance Library species the library of the cellview that contains the selected instance. Cell species the cell that contains the selected instance.
September 2002
53
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations View species the view of the cellview that contains the selected instance. Instance species the name of the instance in the cellview that contains it. Bound To displays the results of the rules that are used by the selected instance. Library species the master library of the selected instance. Cell species the master cell of the selected instance. View species the master view of the selected instance. Note: If the Library, Cell , or View elds display **UNBOUND**, the instance has a bindto-open attribute. Explanation describes the bindings for the selected instance. Close closes the form. Help opens this manual.
Verifying Occurrence Binding Rules

To see which binding rules were used for an occurrence, 1. In the tree view of the hierarchy editor, in the Tree View section, right-click on the occurrence. 2. From the pop-up menu, select Explain .
September 2002
54
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations The Explain form appears.
About the Explain Form for a Selected Occurrence

Selection species the full path from the top cellview to the occurrence. Bound To displays the library, cell, and view to which the occurrence is bound. Library species the library of the selected occurrence. Cell species the cell of the selected occurrence. View species the view of the selected occurrence. Note: If the Library, Cell , or View elds display **UNBOUND**, the occurrence has a bind-to-open attribute. Explanation describes the bindings for the selected occurrence. Close closes the form.
September 2002
55
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations Help opens this manual.
Working with Templates

Templates let you build congurations using pre-dened view lists and stop lists. The hierarchy editor includes templates for some simulators that are compatible with Cadence software. You can also create your own templates.
Using Templates
To use a template, 1. Choose File New or press Control-n . The New Conguration form appears. 2. In the New Conguration form, click Use Template . The Use Template form appears.
3. Do one of the following:
If you want to use a pre-dened template, or a template that you have created and placed in the your_install_dir /share/cdssetup/hierEditor/ templates directory, select the template from the Name listbox. If you want to use a template that is not in the your_install_dir /share/ cdssetup/hierEditor/templates directory,

Select <Other> from the Name listbox. In the From File eld, type the path to the template.
September 2002
Cadence Hierarchy Editor User Guide Creating Congurations 4. Click OK . The Use Template form closes. The New Conguration form is lled in with the view list and stop list data from the template. Note: If there is already information in the Top Cell section, selecting a template does not overwrite that information. If the Top Cell elds are empty when you select a template, the hierarchy editor lls them in with the default values. 5. In the New Conguration form, click OK . The hierarchy editor displays the new data.
About the Use Template Form

Template Name lets you select a template from a list of pre-dened templates for simulators that are compatible with Cadence software. The listbox also lists any other templates that you placed in the your_install_dir /share/cdssetup/hierEditor/templates/ directory. If you want to use a template that is not in this directory, select <Other> and specify the path in the From File eld. From File lets you type the path to the template you want to use. OK applies your settings and closes the form. Cancel closes the form without applying your settings. Apply sets your selections and leaves the form open. Help opens this manual.
Creating Templates
You can create your own template using your own view lists and stop lists for your simulator or other design-specic requirements. To create your own template, 1. In the hierarchy editor, choose File New or press Control-n . Note: If you have made changes to the current hierarchy, the hierarchy editor prompts you to save your changes. The New Conguration form appears.
Cadence Hierarchy Editor User Guide Creating Congurations 2. In the Top Cell section, type the library, cell, and view name of the root of your hierarchy. 3. In the Global Bindings section, specify the library list, view list and stop list. Separate entries with spaces. You can use constants in the view list and stop list. Refer to Using Constants on page 106. 4. (Optional) In the Description eld, type a brief statement about the new template. 5. Click OK . The New Conguration form closes. The hierarchy editor displays the new conguration. 6. Choose File Save As to save your new conguration. The Save As form appears. 7. In the Browse section, select the library in which you want to save the new conguration. The library is displayed in the Library eld in the Configuration section. 8. In the Cell field, type the name of the cell. 9. In the View eld, type the name of the view. Note: The name you give to the cell and view of the conguration do not have to match the name of the cell and view of the top-level cell. 10. Click OK .
Copying Your Created Template to Another Location

You can copy the templates you create to another location and access them from the Use Template button on the New Configuration form. By default, congurations are saved in the expand.cfg le, which is located in your library/cell/configuration_view directory. To copy your template to another location, 1. Change directories to the /library/cell/view directory in which you saved the template. 2. Use a text editor such as vi to verify that the conguration le is correct.
September 2002
58
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations 3. Copy the conguration le to the templates directory with the following command:
cp expand.cfg your_install_dir /share/cdssetup/hierEditor/templates/ yourtemplatename
4. Restart the hierarchy editor. Your new template is available from the Use Template button on the New Configuration form.
Saving Congurations
When you save a conguration in the hierarchy editor, it is saved in the expand.cfg le in the conguration view. The conguration view directory also contains an expand.cfg% le, which is the previously-saved version of the expand.cfg le. You can also save VHDL and Verilog congurations. See the following topics for more information:
I I
Saving VHDL Configurations on page 61 Saving Verilog Congurations on page 62
If you are a Virtuoso Schematic Composer user, see Updating a Virtuoso Schematic Composer Conguration Using the Hierarchy Editor Interface on page 64. Note: Other applications cannot access changed conguration les until they have been saved in the hierarchy editor.
Saving a Conguration
To save a conguration,
Choose File Save or press Control-s . The hierarchy editor saves the conguration.
To save a conguration using the File Save As command, 1. Choose File Save As .
September 2002
59
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations The Save As form appears.
(For details about the Save As form, see About the Save As Form on page 60.) 2. Specify the library in which you want to save the conguration by typing the name in the Library eld or selecting the library from the Browse section. 3. Specify the cell in which you want to save the conguration by typing the name in the Cell eld or selecting the cell from the Browse section. 4. In the View eld, type the name of the new conguration view. Note: The name you give to the cell and view of the conguration do not have to match the name of the cell and view of the top-level cellview. 5. Click OK . The next time you want to use this conguration, you can access it from the Open Browse section by selecting the library, cell, and view.
About the Save As Form

Configuration Library lets you specify the name of the library in which you want to save a copy of the conguration. Cell lets you specify the name of the cell in which you want to save the conguration.
September 2002
60
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations View lets you specify the name of the new conguration view. OK saves the le you selected. Cancel cancels your selections and closes the form. Browse lets you select the library, cell, and view for the new conguration. The library, cell, and view you select are displayed in the Library, Cell , and View text elds in the Configuration section. Note that the browser displays only conguration views and expands only those cells that contain conguration views. Filters lets you narrow your search by displaying a subset of libraries and cells that match your search criteria. Help opens this manual.
Saving VHDL Congurations

The hierarchy editor provides the File Save As VHDL command to save a conguration in VHDL syntax that can be read by VHDL tools. A VHDL conguration is always saved in a view called configuration. To save a conguration for VHDL applications, 1. Choose File Save As VHDL . The Save As VHDL form appears.
September 2002
61
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations 2. Specify the name of the library and cell in which you want to save the VHDL conguration by doing one of the following:

Type the names in the Library and Cell elds. Select the library and cell from the Browse section.
The View eld is automatically set to configuration. 3. Click OK . Note: Saving a VHDL conguration does not save it in a format that can be read and edited by the hierarchy editor. You must also save the conguration with the File Save or File Save As command in order for it to be read by the hierarchy editor.
About the Save As VHDL Form

Configuration Library species the name of the library in which you want to save the conguration. Cell species the name of the cell in which you want to save the conguration. View species the name of the conguration view. For VHDL congurations, the view name is always configuration. OK saves the conguration. Cancel discards your selections and closes the form. Filters lets you narrow your search by displaying a subset of libraries and cells that match your search criteria. Help opens this manual.
Saving Verilog Congurations

The hierarchy editor provides the File Save As Verilog command to save a conguration in Verilog syntax that can be read by Verilog tools. To save a conguration for Verilog applications, 1. Choose File Save As Verilog .
September 2002
62
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations The Save As Verilog form appears.
2. Specify the le in which you want to save the Verilog conguration by doing one of the following: a. In the Look in eld, type the path to the directory in which you want to save the conguration. b. In the File eld, type the name of the le. The default value of this eld is verilog.f. or a. Select the le in which you want to save the Verilog conguration from the le browser. Note: You can also type a lter expression in the Filters eld to narrow your search for the directory to which you want to save your Verilog le. 3. Click OK .
September 2002
63
Product Version 5.0
About the Save As Verilog Form

Look in lets you type the path to a directory or use the arrow button to display a dropdown menu of all the directories in the path to the root directory. The file browser displays all the directories and subdirectories of the current directory displayed in the Look in eld. File lets you type a name for the Verilog le. Filters let you type a lter expression to display the directories you want to see. For example, to display all the directories that begin with c, type *.c The les that match the lter are shown in the viewing area. OK applies your selections and closes the form. Cancel closes the form without applying your selections. Help opens this manual.
Updating a Virtuoso Schematic Composer Conguration Using the Hierarchy Editor Interface
The Virtuoso schematic composer provides an interface to the hierarchy editor. Using the interface, you can update the conguration of a cellview. To update a conguration which was generated from the schematic composer, do the following: 1. Open the conguration view of the design you want to recongure. The hierarchy editor and the congured schematic view appears. 2. Edit the conguration using the hierarchy editor and save the le. 3. From the schematic composer window, open the Hierarchy Editor interface by choosing Tools Hierarchy Editor. The hierarchy editor menu appears on the schematic composer menu banner. The Update menu is grayed-out until you update the conguration. 4. Choose Hierarchy Editor Update . The hierarchy editor displays the updated conguration.
September 2002
64
Product Version 5.0
Cadence Hierarchy Editor User Guide Creating Congurations Note: The conguration cellview on the save form in the schematic composer must be checked in order to have your changes communicated and saved to the hierarchy editor. The Cellviews Need Saving Warning form appears if you do not check the conguration cellview on the save form in the schematic composer.
To dismiss this form, click OK , return to the save form and check the conguration cellview. Your conguration is automatically updated and the hierarchy editor and the schematic composer are synchronized.
September 2002
65
Product Version 5.0
September 2002
66
Product Version 5.0
3
Changing Design Components
I
Overview on page 69

Global Bindings on page 69 Cell Bindings on page 69 Instance Bindings on page 70 Occurrence Bindings on page 71 How a Library Is Selected for an Object on page 71 How a View Is Selected for an Object on page 72
Dening Rules at the Global Level on page 72

Dening a View List at the Global Level on page 73 Dening a Library List at the Global Level on page 74 Dening a Stop List at the Global Level on page 75
Dening Rules at the Cell Level on page 77

Changing Library Bindings on a Per-Cell Basis on page 77 Changing View Bindings on a Per-Cell Basis on page 78 Dening Stop Points on a Per-Cell Basis on page 79 Dening Bind-to-Open on a Per-Cell Basis on page 80
Dening Rules at the Instance Level on page 82

Changing View Bindings on a Per-Instance Basis on page 82 Changing Library Bindings on a Per-Instance Basis on page 84 Dening Stop Points on a Per-Instance Basis on page 85
September 2002
Cadence Hierarchy Editor User Guide Changing Design Components

I
Dening Bind-to-Open on a Per-Instance Basis on page 87 Changing Instance Bindings Inside a Block on page 89 Changing Instance Bindings Created by a Generate Statement on page 91
Dening Rules at the Occurrence Level on page 92

About Occurrences on page 92 How Occurrences Are Different from Instances on page 93 Dening Occurrence Bindings on page 95 Dening Occurrence Stop Points on page 102 Dening Occurrence-Level Bind-to-Open on page 103
I I
Changing Binding Data Color Denitions on page 105 Using Constants on page 106

Creating Constants on page 106 About the Edit Constants Form on page 109 Editing Constants on page 108 Using Constants on page 110
September 2002
68
Product Version 5.0
Overview
With the hierarchy editor, you can control the expansion of your design for any given purpose such as simulation or netlisting. You do this by creating and editing rules that dene a design conguration. You can specify the following conguration rules in the hierarchy editor:
I I
Library Binding: Library binding determines the library from which a cell is obtained. View Binding: View binding determines which view of a cell is to be used in the conguration. For example, a cell might have different representations such as schematic, Verilog, and VHDL; the view binding determines which of these representations is used in the conguration. Stop Lists and Stop Points : Stop lists and stop points prevent further expansion of any part of a design. Bind-to-Open: The bind-to-open attribute is a way of specifying that an object in the design is unbound, that is, it is not bound to a particular library, cell, and view. The bindings for the object can be set later by another application.
You create and edit these rules at different levels of the design. You can specify global rules that apply to every level of the design. You can also specify rules at the cell, instance, and occurrence levels.
Global Bindings
Global bindings are conguration rules that are dened at the global level. At the global level, you can dene a library list, view list, and stop list. These global bindings become the default rules for the conguration and apply to every level of the hierarchy, unless they are overridden at lower levels of the hierarchy. For more information about global bindings, see Dening Rules at the Global Level on page 72.
Cell Bindings
Cell bindings are conguration rules that are dened at the cell level. Cell bindings override global bindings for a cell. Cell bindings apply to all instantiations of a cell. You can dene the following rules at the cell level:
September 2002
69
Product Version 5.0

I
View binding that determines which view of the cell is used in the conguration You can dene view bindings for a cell in the following ways:
Binding rules for a specic cell that apply to that cell and to components below it in the hierarchy, until they are overridden by another binding Binding for a specic cell that applies only to that cell and is not inherited by components below the cell
Library binding that determines the library from which the cell is obtained. This is done by specifying a library list for the cell. Cell-level library lists are inherited by components below the cell in the hierarchy. Stop point on the cell that prevents the cell from being expanded. Bind-to-open attribute that species that the cell is unbound. You can put a bind-to-open attribute on a cell in a specic library or on just a cell.
I I
For more information about cell bindings, see Dening Rules at the Cell Level on page 77.
Instance Bindings
Instance bindings are conguration rules that are dened at the instance level. Instance bindings override global bindings and cell bindings for an instance. Instance bindings apply to a single instantiation of a cell. Note, however, that if the cell that contains the instance is used in multiple places in the design, the binding applies to the instance in all those places. If you want to specify a binding for only one instance at a specic path, you need to specify occurrence bindings instead of instance bindings. You can dene the following rules at the instance level:
I
View binding that determines which view of the cell is used in the conguration You can dene view binding for an instance in the following ways:
Binding rules for a specic instance that apply to that instance and to components below it in the hierarchy, until they are overridden by another binding Binding for a specic instance that applies only to that instance and is not inherited by components below it in the hierarchy
Library binding that determines the library from which the instance is obtained. This is done by specifying a library list for the instance. Instance-level library lists are inherited by components below the instance in the hierarchy.
September 2002
70
Product Version 5.0

I I
Stop point on the instance that prevents the instance from being expanded. Bind-to-open attribute that species that the instance is unbound, that is, it is not bound to a particular library, cell, or view.
For more information about instance bindings, see Dening Rules at the Instance Level on page 82.
Occurrence Bindings
Occurrence bindings are conguration rules that are dened at the occurrence level. An occurrence is an instance that is dened by the full path from the top-level design to the instance. Therefore, occurrence bindings apply to a single object at a specic path in the design. You can specify the following rules at the occurrence level:
I I I
Library, cell, and view binding for a single object at a specic path in the design Stop point that prevents the occurrence from being expanded Bind-to-open attribute that species that the occurrence is unbound, that is, it is not bound to a specic library, cell, or view.
For more information about occurrence bindings, see Dening Rules at the Occurrence Level on page 92. Note: Not all Cadence tools support occurrences. Please refer to the documentation for the applications you are using to check if those applications support occurrences.
How a Library Is Selected for an Object

You can dene library binding rules at different levels of a design. The hierarchy editor uses the following order of precedence (listed from highest precedence to lowest precedence) to select the library for an object: 1. Occurrence binding 2. Instance-level Inherited Library List 3. Cell-level Inherited Library List 4. Global Library List
September 2002
71
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components You can see which binding rules were used to select the library for an object by reading the description in the Explain form in the hierarchy editor. See Verifying Conguration Data on page 50 for more information.
How a View Is Selected for an Object

You can dene view binding rules in different ways and at different levels of a design. The hierarchy editor uses the following order of precedence (listed from highest precedence to lowest precedence) to select the view for an object: 1. Occurrence binding 2. Instance-level View to Use binding 3. Cell-level View to Use binding 4. Instance-level Inherited View List 5. Cell-level Inherited View List 6. Global View List You can see which binding rules were used to select the view for an object by reading the description in the Explain form in the hierarchy editor. See Verifying Conguration Data on page 50 for more information.
Dening Rules at the Global Level

You can dene rules at the global level that become the default rules for the entire conguration. These rules are inherited by every level of the hierarchy until they are overridden by rules lower in the hierarchy. You specify global rules, referred to as global bindings, in the Global Bindings section of the hierarchy editor. You can specify these rules in either the table view or the tree view of the hierarchy editor. You can specify the following rules at the global level:
I I I
Library List View List Stop List
September 2002
72
Product Version 5.0
Dening a View List at the Global Level

When you dene views at the global level, the views apply to every level of the conguration and must be listed in the order in which you want them searched. For example, if your View List is
spectreS schematic cmos.sch verilog
the hierarchy editor searches for each instance as shown in the gure.
Inherited View List: spectreS schematic cmos.sch verilog
Top cell inv1

First view found in View List
inv2
Cell contained by top cell
symbol
schematic
verilog
symbol
schematic
verilog
Views of inv2
nmos
pmos
nmos
pmos
Instances within inv1
Instances within inv2
symbol spectreS
symbol spectreS
symbol spectreS
symbol spectreS
The gure shows how the hierarchy editor searches for the rst view listed in the View List. For example, in the cell inv1 , the symbol , schematic , and verilog views are in the table. If the hierarchy editor nds a match, it selects that view for the design. If it does not nd a match, it continues to look until a match is found. In the example, the second view in the view list, schematic , is the rst view that is found. The View List determines which view is selected for every object in the design, unless overridden by a cell binding, instance binding, or occurrence binding. If the hierarchy editor does not nd a view for a cell or instance, it displays **NONE** for that cell or instance in the View Found column of the Cell or Instance Bindings table.
September 2002
73
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components **NONE** indicates a binding error that prevents you from netlisting until you correct the error. The global view list that you dene becomes the default Inherited View List for each cell and instance. You can override the default at the cell, instance, or occurrence levels. You can also check which binding rules were used to select the view for an object; see Verifying Conguration Data on page 50 for more information. To create or change the global View List, 1. In the Global Bindings section, click in the View List eld. 2. Type the views you want in the order of preference. Note: You can also dene a constant, such as $default, $digital, or $analog, to represent a view list, and use this constant in inherited view lists. Constants are easier to read than a long view list, and they can be re-used in any view list. See Using Constants on page 106. 3. Press Return . 4. To see the changes in the Cell Bindings table, from the toolbar, click the Update icon. The Cell Bindings table changes to show the new conguration resulting from the change in the View List. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 5. To save the changes, from the menu bar, choose File Save or press Control-s. To delete a view from the global View List, 1. In the Global Bindings section, click in the View List eld. 2. Highlight the view you no longer want and press Delete. 3. To see the changes in the Cell Bindings table, from the toolbar, click the Update icon.
Dening a Library List at the Global Level

Library lists determine the library from which each component in the design is obtained. Libraries are listed in the order of preference. The hierarchy editor searches the libraries in the order in which they are listed and uses the component from the rst library in which it is found.
September 2002
74
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Global library lists apply to every level of the conguration. Global library lists can be overridden by library lists at the cell and instance levels and by specic library.cell:view binding on an occurrence. You can see which binding rules were used to select a library for a component; see Verifying Conguration Data on page 50 for more information. To create or change a library list at the global level, 1. In the Global Bindings section of the hierarchy editor, click in the Library List eld. 2. Do one of the following:

To create a new library list, type the libraries in the order of preference. To add a library to an existing library list, type the new library in the appropriate place. Note that the libraries are searched in the order in which they are listed. To remove a library from the library list, highlight the view and press Delete.
3. Press Return. 4. To see the changes in the conguration, from the toolbar, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 5. To save the changes, choose File Save or press Control-s .
Dening a Stop List at the Global Level

A stop list is a list of views that are to be treated as if they are at the leaf level, that is they are to be treated as if they do not have any levels of hierarchy below them and cannot be expanded further. The stop list is optionalthe hierarchy editor does not require you to have a stop list in your conguration. You can use the stop list to designate cellviews that contain no instances. In addition, you can use the stop list to indicate cases where you do not want the conguration to descend further into the hierarchy. For example, in attening for placement, you can use the stop list to indicate a cellview that is preplaced, even though it contains instances, so that the placement tool will leave it intact. A stop list at the global level applies to every level of the conguration. Views must be listed in the order of preference. For example, if your stop list is
spectreS verilog
September 2002
75
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components the hierarchy editor expands the design as shown in the gure below. Stop List: spectreS verilog Top cell inv1 inv2
symbol
schematic
verilog
symbol schematic
verilog
nmos
pmos
nmos
pmos
symbol spectreS
symbol spectreS
symbol spectreS
symbol spectreS
To create or change the Stop List, 1. In the Global Bindings section, click in the Stop List eld. 2. Do one of the following:

To create a new stop list, type the views in the order of preference. To add a view to an existing stop list, type the new view in the appropriate place. Note that the views are searched in the order in which they are listed. To remove a view from the stop list, highlight the view and press Delete.
3. Press Return . 4. To see the changes in the Cell Bindings table, from the toolbar, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. The Cell Bindings section of the hierarchy editor changes to show the new conguration resulting from the change in the Stop List. 5. To save the changes, choose File Save or press Control-s .
September 2002
76
Product Version 5.0
Dening Rules at the Cell Level

You can dene rules at the cell level that override the global rules for an individual cell. Note that these rules apply to all instantiations of the cell. In addition, some of these rules can also apply to the hierarchy below the cell. You specify cell-level rules, also referred to as cell bindings, in the Cell Bindings section of the hierarchy editor. You must specify cell binding rules in the table view of the hierarchy editor; you cannot specify them in the tree view. You can specify the following rules at the cell level:
I I I I
Library Binding View Binding Stop Point Bind-to-Open
Changing Library Bindings on a Per-Cell Basis

You can dene a cell-level library list that overrides the global library list for an individual cell. The library list determines the library from which the specic cell is obtained. Libraries are listed in the order of preference. The hierarchy editor searches the libraries in the order in which they are listed and uses the cell from the rst library in which it is found. Note that the cell-level library list
I I
Applies to every instantiation of the cell Is inherited by all components in the hierarchy below the cell
Cell-level library lists can be overridden at the instance and occurrence levels. To create a cell-level library list, 1. Choose View Table . 2. In the Cell Bindings section, click in the Inherited Lib List column of the cell whose binding you want to change. The eld becomes editable. If the eld does not become editable, the library is xed for your design and cannot be changed. CDBA data typically does not allow you to change the library.
September 2002
77
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components 3. Edit the inherited library list. The library list that is currently displayed is the global library list. Type the libraries you want to use in the order of preference. 4. Press Return. 5. To view the changes in the conguration, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 6. To save the changes, choose File Save or press Control-s . In the Instance Bindings table, you can see the changes applied to the instances the cell contains. If an instance has an instance-level library list, the cell-level list does not apply to that instance.
Changing View Bindings on a Per-Cell Basis

You can dene cell-level view binding that overrides the global view list for an individual cell. Cell-level view binding applies to every instantiation of the cell. You can either change the binding for only the cell you specify or you can change it in a way that it is also inherited by the components below the cell in the hierarchy. To make the cell binding apply only to the cell, you specify the view in the View to Use column. To make the cell binding applicable to components below the cell, you specify a view or view list in the Inherited View List column. To specify a cell binding that applies to the cell as well as to objects below it in the hierarchy, 1. In the Inherited View List eld, type the new view or list of views for the cell and press Return . 2. To see the results of your changes, from the toolbar, click the Update icon or from the menu bar, choose View Update. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. The view list you entered is now the view list used for that cell and for any other cells below that cell in the hierarchy (unless they are overridden by other cell or instance bindings lower in the hierarchy). 3. To save the changes, from the menu bar, click File Save or press Control-s . To change a binding for a cell on a per cell basis,
September 2002
78
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components 1. From the Cell Bindings table, right-click anywhere in the row of the cell whose bindings you want to change. 2. From the pop-up menu, select Set Cell View. 3. You can do one of the following:

From the cascaded menu list of views available, click the view you want. Click in the View to Use column and type the new view(s) separated by spaces for the cell and press Return .
The new view name(s) appears in the View to Use column in the color used to display user bindings. If you previously selected a binding you no longer want to use, from the Set Cell View menu item, you can select <none> from the cascaded menu list of views to remove the view binding. 4. To see the results of your changes, from the toolbar, click the Update icon. You can also from the menu bar, choose View Update. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 5. To save the changes, from the menu bar, click File Save or press Control-s . Note: This new cell binding is not inheritable.
Dening Stop Points on a Per-Cell Basis

In addition to a global stop list that applies to the entire conguration, you can specify stop points on individual cells. A stop point on a cell prevents the cell from being expanded when the hierarchy is expanded. Note that a stop point on a cell applies to all the instantiations of the cell. To add a stop point to a cell, 1. Choose View Table . 2. In the Cell Bindings section, right-click on the cell to which you want to add a stop point. 3. From the pop-up menu, select Add Stop Point .
September 2002
79
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The icon (stop icon) appears in the Info column of the cell row. All the instantiations of the cell will now be considered leaf nodes in the hierarchy; none of them will be expanded when the hierarchy is traversed. To see a list of the instantiations to which the stop point applies, 1. In the Cell Bindings section, right-click on the cell. 2. From the pop-up menu, select Explain . The Explain dialog box appears. The Instantiations section lists the instantiations of the cell. The stop point applies to all these instantiations.
Dening Bind-to-Open on a Per-Cell Basis

You can specify that a cell is unbound, that is, it is not bound to a specic library or view, by setting a bind-to-open attribute on it. The bindings for the cell can be set later by other tools that use the conguration. Note that a bind-to-open attribute on a cell applies to all the instantiations of the cell. You can set the attribute on a cell in two ways:
I I
Bind-to-open on a cell Bind-to-open on a cell in a specic library
The hierarchy editor displays the string **UNBOUND** to indicate that a cell has a bind-toopen attribute. **UNBOUND** is not an error, unlike **NONE* . **UNBOUND** indicates that the cell is deliberately unbound while **NONE** indicates that the binding for the cell could not be determined from the binding rules. To set a bind-to-open attribute on a cell, 1. Choose View Table . 2. In the Cell Bindings section, right-click on the cell to which you want to add a bind-toopen attribute. 3. From the pop-up menu, select Add Bind To Open .
September 2002
80
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The Add Bind To Open dialog box appears.
4. In the Add Bind To Open dialog box, do one of the following:
If you want the cell to be unbound, regardless of which library it comes from, select Add Bind To Open on Cell "cellname" . If you want the cell to be unbound when it is obtained from a specic library, select Add Bind To Open on Lib "libname" , Cell "cellname" .
5. Click OK . The cell is now unbound. The Library, View Found and View to Use columns in the Cell Bindings section display **UNBOUND**. If you selected Add Bind to Open on Library "libraryname", Cell "cellname" , only the View Found and View to Use columns display **UNBOUND**. For example:
Also, the instances contained in the cell are no longer displayed in the Instance Bindings section because the cell is now unbound. To see a list of the instantiations to which the bind-to-open attribute applies, 1. In the Cell Bindings section, right-click on the cell. 2. From the pop-up menu, select Explain . The Explain dialog box appears. The Instantiations section lists the instantiations of the cell. The bind-to-open attribute applies to all these instantiations.
September 2002
81
Product Version 5.0
Dening Rules at the Instance Level

You can dene rules at the instance level that override global rules and cell rules. Instance rules apply to only one instantiation of a cell, unlike cell-level rules that apply to all the instantiations of a cell. Note, however, that if the cell that contains the instance is used in multiple places in the design, the binding applies to the instance in all those locations. Some instance-level rules can also apply to the hierarchy below the instance. You specify instance-level rules, also referred to as instance bindings, in the Instance Bindings section of the hierarchy editor. You can specify instance binding rules in the table view or the tree view of the hierarchy editor. You can specify the following rules at the instance level:
I I I I
Library Binding View Binding Stop Point Bind-to-Open
Instance-level rules can be overridden at the occurrence level.
Changing View Bindings on a Per-Instance Basis

You can specify view bindings for a single instantiation of a cell. You can make the view binding apply to only the instance you specify (effective no lower in the hierarchy) or you can change it in a way that it is also inherited by the components below the instance in the hierarchy. To make the binding apply only to the instance, you specify the view in the View to Use column. To make the binding applicable to components below the instance, you specify a view or view list in the Inherited View List column. To display all of the instances for a particular cell, 1. In the Cell Bindings table, click on the name of a cell. 2. From the toolbar, click the Instance Table icon. The hierarchy editor displays the Instance Bindings table. To specify an instance binding that applies only to the instance,
September 2002
82
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components 1. From the toolbar, click the Tree View icon. 2. Right-click in the instance you want to change. The pop-up menu appears.
3. Click the Set Instance View menu item. 4. You can do one of the following:

From the cascaded menu list of views available, click the view you want. Click in the View to Use column and type the new view.
The new view name appears in the View to Use column in the color used to display user bindings. If you previously selected a binding you no longer want to use, from the Set Instance View menu item, you can select <none> from the cascaded menu list of views to remove the view binding. 5. To see the results of your changes, from the toolbar, click the Update icon.
September 2002
83
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 6. To save the changes, from the menu bar, click File Save or press Control-s . Note: This new instance binding is not inheritable. To specify an instance binding that applies to the instance as well as to objects below it in the hierarchy, 1. Click in the Inherited View List eld and type a new view or list of views for the instance and press Return . 2. To see the results of your changes, from the toolbar, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 3. To save the changes, from the menu bar, click File Save or press Control-s . You may also create a symbolic name, to represent a view list. Refer to Using Constants on page 110 if you want to represent multiple views by one name.
Changing Library Bindings on a Per-Instance Basis

You can dene an instance-level library list that overrides the global and cell library lists for a single instantiation of a cell. The library list determines the library from which the instance is obtained. Libraries are listed in the order of preferenceif the instance is found in the rst library in the list, it is used; if it is not found, the second library is searched, and so on. Note that the instance-level library list
I I
Applies to only one instantiation of a cell Can apply to multiple objectsif the cell that contains the instance is used in multiple places in the design, the library binding applies to the instance in all those locations Is inherited by all components in the hierarchy below the instance
An instance level library binding can be overridden by an occurrence binding. To create an instance-level library list, 1. Choose View Table .
September 2002
84
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components 2. In the Cell Bindings table, select the cell that contains the instance you want to change. 3. In the Instance Bindings section, click in the Inherited Lib List column of the instance whose binding you want to change. The eld becomes editable. If the eld does not become editable, the library is xed for your design and cannot be changed. CDBA data typically does not allow you to change the library. 4. Edit the inherited library list. The library list that is currently displayed is the library list inherited from higher levels of the hierarchy. Type the libraries in the order of preference. 5. Press Return. 6. To view the changes in the conguration, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 7. To save the changes, choose File Save or press Control-s .
Dening Stop Points on a Per-Instance Basis

You can specify a stop point on a single instantiation of a cell that prevents the instance from being expanded when the hierarchy is expanded. Note that a stop point on an instance can apply to multiple objectsif the cell that contains the instance is used in multiple places in the design, the stop point applies to the instance in all those places. For example, if you put a stop point on instance I2 of cell OpAmp and cell OpAmp is used in three places in the design, the stop point applies to instance I2 in all three instantiations of OpAmp. You can add a stop point to an instance from either the tree view or the table view of the hierarchy editor. To add a stop point to an instance from the tree view, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the instance on which you want to add a stop point. 3. From the pop-up menu, select Add Stop Point .
September 2002
85
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The Set Stop Point dialog box appears.
Note: If the instance has already been identied as an occurrence and has the icon (occurrence icon), when you select Add Stop Point , the Set Stop Point dialog box does not appear. Instead, the stop point is added to the occurrence. For more information about occurrence stop points, see Dening Occurrence Stop Points on page 102. 4. In the Set Stop Point dialog box, select Add Stop Point on Instance "instance" , where instance is the instance you selected. 5. Click OK . The stop icon appears in the Info column of the instance row. The instance cannot be expanded. To add a stop point to an instance from the table view, 1. Choose View Table and View Instance Table to display the table view of the hierarchy editor, if it is not already displayed. 2. In the Cell Bindings section, select the cell that contains the instance to which you want to add a stop point. The Instance Bindings section displays the instances contained in the cell. 3. In the Instance Bindings section, right-click on the instance to which you want to add a stop point. 4. From the pop-up menu, select Add Stop Point . The icon (stop icon) appears in the Info column of the instance row. The instance can no longer be expanded. If the cellview that contains the instance is used in multiple places in the design, the stop point will apply to the instance in all those places.
September 2002
86
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components To see which objects the stop point applies to, 1. In the Cell Bindings section, right-click the cell that contains the instance to which you added the stop point. 2. From the pop-up menu, select Explain . The Explain dialog box appears. The Instantiations section lists the instantiations of the cell. The stop point will apply to the instance in all these instantiations of the cell. Note: You cannot add an instance stop point to an object that has already been dened as an occurrence (identied by a icon). When you add a stop point to such an object, it is added to the occurrence, not the instance, and applies only to one object at a specic path. For information about occurrence stop points, see Dening Occurrence Stop Points on page 102.
Dening Bind-to-Open on a Per-Instance Basis

You can specify that a single instantiation of a cell is unboundthat is, it is not bound to a specic library, cell, and viewby setting a bind-to-open attribute on it. The bindings for the instance can be set later by other tools that use the conguration. Note that a bind-to-open attribute on an instance can apply to multiple objectsif the cell that contains the instance is used in multiple places in the design, the bind-to-open applies to the instance in all those places. For example, if you specify that instance I2 in cell OpAmp is unbound and cell OpAmp is used in three places in the design, I2 will be unbound in all three instantiations of OpAmp. The hierarchy editor displays the string **UNBOUND** to indicate that an instance has a bindto-open attribute. **UNBOUND** is not an error, unlike **NONE**. **UNBOUND** indicates that the instance is deliberately unbound while **NONE** indicates that the binding for the instance could not be determined from the binding rules. You can add a bind-to-open attribute to an instance from either the tree view or the table view of the hierarchy editor. To add a bind-to-open attribute to an instance from the tree view, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the instance on which you want to add a bind-toopen. 3. From the pop-up menu, select Add Bind To Open .
September 2002
87
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The Add Bind To Open dialog box appears.
4. In the Add Bind To Open dialog box, select Add Bind To Open on Instance "instance" , where instance is the instance you selected. Note: If the instance has already been identied as an occurrence and has the icon (occurrence icon), the Add Bind To Open on Instance instance option will be greyed out. In this case, you can only add the bind-to-open attribute to the occurrence. For more information about occurrence-level bind-to-open, see Dening OccurrenceLevel Bind-to-Open on page 103. 5. Click OK . The instance is now unbound. The library, cell, and view name of the instance are replaced by **UNBOUND**. For example:
To add a bind-to-open attribute to an instance from the table view, 1. Choose View Table and View Instance Table to display the table view of the conguration, if it is not already displayed. 2. In the Cell Bindings section, select the cell that contains the instance to which you want to add a bind-to-open attribute. The Instance Bindings section displays the instances contained in the cell. 3. In the Instance Bindings section, right-click on the instance to which you want to add a bind-to-open. 4. From the pop-up menu, select Add Bind To Open .
September 2002
88
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The instance is now unbound. The Library, Cell , View Found , and View to Use columns display **UNBOUND**. For example:
If the cellview that contains the instance is used in multiple places in the design, the bind-toopen will apply to the instance in all those places. To see which objects the bind-to-open applies to, 1. In the Cell Bindings section, right-click on the cell that contains the instance to which you added the bind-to-open. 2. From the pop-up menu, select Explain . The Explain dialog box appears. The Instantiations section lists the instantiations of the cell. The bind-to-open will apply to the instance in all these instantiations of the cell. If any of the instances has an occurrence binding on it already, the bind-to-open will not apply to it.
Changing Instance Bindings Inside a Block

A block is a group of instances used in simulators like VHDL. Blocks can contain other blocks and other instances. You can bind instances inside a block the same way you can bind instances in a cellview. Blocks are better displayed in the tree structure of the hierarchy editor. To change the instance bindings inside a block, 1. From the toolbar, click the Tree View icon. 2. Select the block containing the instance you want to change.
September 2002
89
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components 3. Click the expand button to display the instances within the selected block.
Block name
Expanded block
Generate statement Instance
4. Right-click the instance whose bindings you want to change. The pop-up menu appears. 5. From the pop-up menu, select Set Instance View. 6. You can do one of the following:

From the cascaded menu list of views available, click the view you want. Click in the View to Use column and type the new view for the instance and press Return .
The new view name(s) appears in the View to Use column in the color used to display user bindings. If you select a binding you no longer want to use, from the Set Instance View menu item, you can select <none> from the cascaded menu list of views to remove the view binding. 7. To see the results of your changes, from the toolbar, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated. 8. To save the changes, from the menu bar, click File Save or press Control-s .
September 2002
90
Product Version 5.0
Changing Instance Bindings Created by a Generate Statement

VHDL users can bind instances created by generate statements. You can collectively bind all the instances (such as a0, a1,...an ) that were created by a generate statement. The instance name is preceded by a label for the generate statement. For example, FOR_GEN: g1, the instance g1 is the label assigned to the block statement FOR_GEN. Generate statements are not displayed in the cell table.
I I I
Bindings are not allowed on a generate statement. You cannot change a subset of instances created by a generate statement. You can collectively bind instances created by a generate statement the same way you can bind instances inside a cellview.
To change instance bindings created by a generate statement, 1. Click the generate statement you want to change. You may click the expand button to see instances or cellviews inside a generate statement. 2. Right-click the instance you want to change. The pop-up menu appears. 3. From the pop-up menu, select Set Instance View. 4. You can do one of the following:

From the cascaded menu list of views available, click the view you want. Click in the View to Use column and type the new view for the instance and press Return .
The new view name(s) appears in the View to Use column in the color used to display user bindings. If you select a binding you no longer want to use, from the Set Instance View menu item, you can select <none> from the cascaded menu list of views to remove the view binding. 5. To see the results of your changes, from the toolbar, click the Update icon. If you selected the Automatic Update option in the Options form, this step is not required because your conguration is automatically updated.
September 2002
91
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components 6. To save the changes, from the menu bar, click File Save or press Control-s .
Dening Rules at the Occurrence Level

About Occurrences
An occurrence is an instance that is uniquely identied by its full path from the top-level design to the instance. Occurrences provide the ability to uniquely identify an object in the design and assign attributes to that object. Occurrence binding is useful for mixed-signal simulation. In the hierarchy editor, you can assign the following attributes to an occurrence:
I I I
Occurrence binding, that is, library, cell, and view binding Occurrence stop point Occurrence-level bind-to-open
Setting any of the above attributes identies the object as an occurrence. Note: Not all Cadence tools support occurrences. Before you use the occurrence feature of the hierarchy editor, please refer to the documentation for the applications you are using to check if those applications support occurrences. In the hierarchy editor, occurrences are represented by the following icons: The object has an occurrence binding The tree node contains an occurrence The object has an occurrence stop point The object has an occurrence binding and an occurrence stop point
To see a complete list of icons and color conventions used in the Cadence hierarchy editor,
Choose Help Legend . The Legend dialog box appears. This dialog box describes all the icons and color conventions.
September 2002
92
Product Version 5.0
How Occurrences Are Different from Instances

Occurrences are unique, while instances are not. When you put an attribute (such as a stop point) on an instance, it can apply to more than one object because instances cannot be identied uniquely. An instance is identied by the cell it is contained in. If the cell is used in multiple places in the design, the instance is in multiple places in the design. An occurrence, on the other hand, is identied uniquely by its full path from the top-level design. When you put an attribute (such as a stop point) on an occurrence, it only applies to that single object. The following example illustrates the difference between instances and occurrences. Both Figure 1 and Figure 2 display the design mixSigLib.tutorial:schematic. In this design, the cell OpAmp is used twiceits instantiations are mixSigLib.tutorial:schematic.I0.I0.I144 and mixSigLib.tutorial:schematic.I0.I0.I145. The cell OpAmp contains several instances, including Q60. In Figure 1, an instance stop point is specied on Q60 in I144. Notice that Q60 in I145 (the other instantiation of cell OpAmp) automatically gets the stop point, too.
September 2002
93
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Figure 1: Example of an Instance-Level Stop Point
Stop Point placed on instance Q60
In Figure 2, an occurrence stop point is specied on Q60 in I144. Notice that Q60 in I145 (the other instantiation of cell OpAmp) is not affected by the stop point. This is because the stop point was put on the occurrence and not on the instance.
September 2002
94
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Figure 2: Example of an Occurrence Stop Point
Stop point placed on occurrence Q60
Dening Occurrence Bindings

You create an occurrence binding by specifying a library, cell, and view for a single object at a specic path in the design. Unlike cell or instance binding, occurrence binding applies only to one object. When you do an occurrence binding, none of the other binding rulessuch as inherited library lists or view listsapply to that occurrence. You can create an occurrence binding only in the tree view of the hierarchy editor; you cannot create it in the table view. Note: If the library or cell is xed by some other rules in the design data, you will not be able to change that binding. For example, design data in DFII typically does not allow you to change the library.
September 2002
95
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Creating an Occurrence Binding To specify a binding for an occurrence, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the instance to which you want to add an occurrence binding. 3. From the pop-up menu, select Add Occurrence Binding . The Add Occurrence Binding dialog box appears.
4. Specify the library, cell, and view to which you want to bind the occurrence by doing one of the following in the Add Occurrence Binding dialog box:

In the Occurrence Binding section, type the library, cell, and view. In the Browse section, select the library, cell, and view. You can use lters to limit the data displayed in the Browse section. Click Filters to display the Browser Filters form.
If you want the occurrence to be unbound so that its binding can be set later by another tool, select Enable Bind To Open . The Library, Cell , and View elds display **UNBOUND**. These elds are greyedout and are not editable when Enable Bind To Open is selected.
September 2002
96
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components (For more information about the Bind To Open option, see Dening OccurrenceLevel Bind-to-Open on page 103) Note: If the library or cell is xed by some other rules in the design data, you will not be able to edit the corresponding elds in the Occurrence Binding section. For example, design data in DFII typically does not allow you to change the library. 5. Click OK . The dialog box closes. The object is now identied as an occurrence and a library.cell:view binding is set on it. The leaf node or tree node icon that was displayed for the instance is replaced by the icon (occurrence icon). If the object already had an occurrence stop point, the icon is replaced by the icon (occurrence binding and stop point icon). Editing an Occurrence Binding To edit an occurrence binding, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the occurrence whose binding you want to change. 3. If you want to change only the view, from the pop-up menu, select Set Occurrence View and then select the new view from the list of views. Skip the remaining steps in this section. 4. If you want to change the library or cell, from the pop-up menu, select Edit Occurrence Binding .
September 2002
97
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The Edit Occurrence Binding dialog box appears.
5. Edit the library, cell, and view to which the occurrence is bound by doing one of the following:
Edit the Library, Cell , and View elds in the Occurrence Binding section or select the library, cell, and view from the Browse section. You can use lters to limit the data displayed in the Browse section. Click Filters to display the Browser Filters form.
If you want the occurrence to be unbound so that its binding can be set later by another tool, select Enable Bind To Open . The Library, Cell , and View elds display **UNBOUND**. These elds are greyedout and are not editable when Enable Bind To Open is selected. (For more information about the Bind To Open option, see Dening OccurrenceLevel Bind-to-Open on page 103)
Note: If the library or cell is xed by some other rules in the design data, you will not be able to edit the corresponding elds in the Occurrence Binding section. For example, design data in DFII typically does not allow you to change the library. 6. Click OK . The dialog box closes.
September 2002
98
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Removing an Occurrence Binding To remove an occurrence binding, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. The hierarchy editor displays the tree view of the conguration. 2. In the Tree View section, right-click on the occurrence whose binding you want to remove. 3. From the pop-up menu, select Remove Occurrence Binding . The occurrence binding is removed from the object. The icon (occurrence icon) is replaced by the leaf or folder icon. The object is no longer uniquely identied, unless it also has an occurrence stop on it. About the Add Occurrence Binding and Edit Occurrence Binding Forms Add Occurrence Binding Form
Occurrence Binding Library lets you specify the library to which you want to bind the occurrence. Cell lets you specify the cell to which you want to bind the occurrence.
Cadence Hierarchy Editor User Guide Changing Design Components View lets you specify the view to which you want to bind the occurrence. Note: You will not be able to edit the Library, Cell , or View elds if
The library or cell is xed by some rules in the design data For example, design data in DFII typically does not allow you to change the library.
Enable Bind To Open is selected The Enable Bind To Open option species that the library, cell, and view are unbound.
Browse lets you select the library, cell, and view to which you want to bind the occurrence. The library, cell, and view that you select are displayed in the Library, Cell , and View text elds in the Occurrence Binding section. Enable Bind To Open lets you specify that the occurrence is unbound, that is, it is not bound to a particular library, cell, or view. The binding for the occurrence can be set later by another tool that uses the conguration. If Enable Bind To Open is selected, the Library, Cell , and View elds cannot be edited. OK applies your changes and closes the form. Cancel cancels your changes and closes the form. Filters displays the Browser Filters form which lets you specify search criteria to display only part of the library structure in the Browse section. Help opens this manual.
September 2002
100
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Edit Occurrence Binding Form
Occurrence Binding Library lets you specify the library to which you want to bind the occurrence. Cell lets you specify the cell to which you want to bind the occurrence. View lets you specify the view to which you want to bind the occurrence. Note: You will not be able to edit the Library, Cell , or View elds if
The library or cell is xed by some rules in the design data For example, design data in DFII typically does not allow you to change the library.
Enable Bind To Open is selected The Enable Bind To Open option species that the library, cell, and view are unbound.
Browse lets you select the library, cell, and view to which you want to bind the occurrence. The library, cell, and view that you select are displayed in the Library, Cell , and View text elds in the Occurrence Binding section. Enable Bind To Open lets you specify that the occurrence is unbound, that is, it is not bound to a particular library, cell, or view. The binding for the occurrence can be set later by another tool that uses the conguration. If Enable Bind To Open is selected, the Library, Cell , and View elds cannot be edited.
Cadence Hierarchy Editor User Guide Changing Design Components OK applies your changes and closes the form. Cancel cancels your changes and closes the form. Filters displays the Browser Filters form which lets you specify search criteria to display only part of the library structure in the Browse section. Help opens this manual.
Dening Occurrence Stop Points

An occurrence stop point is a stop point on a specic path and applies only to one object in the design. If an object has already been dened as an occurrence (an object is dened as an occurrence if it has one of the following occurrence attributes: occurrence binding, occurrence stop point, or occurrence bind-to-open), when you add a stop point, you are automatically adding it to the occurrence, not to the instance. You can only add an occurrence stop point in the tree view of the hierarchy editor; you cannot add it in the table view. Adding an Occurrence Stop Point To add an occurrence stop point, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the instance on which you want to add a stop point. 3. From the pop-up menu, select Add Stop Point .
September 2002
102
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The Set Stop Point dialog box appears.
Note: If the instance has already been identied as an occurrence and has the icon, when you select Add Stop Point , the Set Stop Point dialog box does not appear. The stop point is added to the occurrence and the icon (occurrence binding and stop point icon) appears next to the occurrence. 4. In the Set Stop Point dialog box, select Add Stop Point on Path "path" , where path is the full path to the instance from the top-level design. 5. Click OK . The icon (occurrence stop point icon) appears next to the occurrence. The occurrence cannot be expanded until the stop point is removed. Removing an Occurrence Stop Point To remove an occurrence stop point, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the occurrence. 3. From the pop-up menu, select Remove Stop Point . The occurrence stop point is removed. The icon is replaced by the leaf or folder icon. The object is no longer uniquely identied, unless it also has an occurrence binding.
Dening Occurrence-Level Bind-to-Open

You can specify that an occurrence is unboundthat is, it is not bound to a specic library, cell, and viewby setting a bind-to-open attribute on it. The bindings for the occurrence can be set later by other tools that use the conguration.
Cadence Hierarchy Editor User Guide Changing Design Components The hierarchy editor displays the string **UNBOUND** to indicate that an occurrence has a bind-to-open attribute. **UNBOUND** is not an error, unlike **NONE**. **UNBOUND** indicates that the occurrence is deliberately unbound while **NONE** indicates that the binding for the occurrence could not be determined from the binding rules. You can only add an occurrence-level bind-to-open attribute in the tree view of the hierarchy editor; you cannot add it in the table view. Setting Bind-to-Open on an Occurrence To add a bind-to-open attribute to an occurrence, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the instance on which you want to add an occurrence-level bind-to-open. 3. From the pop-up menu, select Add Bind To Open . The Add Bind To Open dialog box appears.
4. In the Add Bind To Open dialog box, select Add Bind To Open on Path "path" , where path is the full path to the instance from the top-level design. 5. Click OK . The bind-to-open attribute is set on the occurrence. The icon (occurrence icon) appears next to the occurrence and the library, cell, and view names are replaced by **UNBOUND**. For example:
September 2002
104
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components Note: You can also specify a bind-to-open attribute from the Add Occurrence Binding and Edit Occurrence Binding forms by selecting the Enable Bind To Open option. Removing Occurrence-Level Bind-to-Open To remove an occurrence-level bind-to-open attribute, 1. Choose View Tree to display the tree view of the conguration, if it is not already displayed. 2. In the Tree View section, right-click on the occurrence from which you want to remove the bind-to-open attribute. 3. From the pop-up menu, select Remove Bind To Open . The occurrence is no longer unbound. The library, cell, and view name are determined based on the other binding rules and displayed.
Changing Binding Data Color Denitions

The hierarchy editor displays color-coded cell and instance binding data. The following table lists the default colors:
Color Black Blue Red Orange
Denition Default binding User-dened binding Error Not in Use
Note: As you type new binding information into the Cell Bindings or Instance Bindings table, the user-dened binding color is used. You can change the default colors by adding variables to a local hierEditor.env le. To change the default colors, 1. If you do not have a hierEditor.env le, create a le named hierEditor.env in a directory that is in your setup.loc le (for example, your $HOME directory or current
September 2002
105
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components working directory). You can create the le with a text editor or with the File Save Defaults command. Note: If you have multiple hierEditor.env les, the hierarchy editor determines which value to use based on the search order dened in the setup.loc le. 2. Add the following variables to the hierEditor.env le:
hierEditor.display.colorChooser hierEditor.display.colorChooser hierEditor.display.colorChooser hierEditor.display.colorChooser bindingError string newColor nil userBinding string newColor nil defaultBinding string newColor nil notInUse string newColor nil
For example, if you want to change the default binding color to green, add the following variable:
hierEditor.display.colorChooser defaultBinding string green nil
Note: Add only those variables that you want to change from the default. You do not need to add variables that you are not changing. 3. Save the hierEditor.env le. Your changes are displayed the next time you start the hierarchy editor. For more information about the hierEditor.env le, see Appendix A, The hierEditor.env File.
Using Constants
A constant is a symbolic name that represents a view list. Constants provide a way to store and retrieve long view lists. You can create a constant and use it anywhere you use a View List and a Stop List.
Creating Constants
To create a constant, 1. Choose Edit Constants .
September 2002
106
Product Version 5.0
Cadence Hierarchy Editor User Guide Changing Design Components The Edit Constants form appears.
2. Add views to the Value eld by doing one of the following:
In the View Choices list box, select the view that you want to include in the new constant, then click Insert . In the View Choices list box, double-click the view that you want to include in the new constant.
Note: If a view that you want to include in the constant is not available in the View Choices list, you can type the name of the view in the Value eld. You can also change the default list of views in the View Choices list box. See Changing the Views in the View Choices List Box on page 110 for more information. 3. In the Constant eld, type the name you want to use to represent the list of views you added to the Value eld. 4. Click Set . Note: The Set button is greyed-out if you have not assigned a constant name to the selected views. The hierarchy editor creates the constant.The constant and its value appear in the table at the top of the form.
Cadence Hierarchy Editor User Guide Changing Design Components Note: The view names must appear in the Value eld in the order in which you want the hierarchy editor to use them. Either insert or type them into the Value eld in that order or highlight a view in the View Choices list box and use the Remove and Insert buttons to rearrange the order.
Editing Constants
To edit the views included in an existing constant, 1. Choose Edit Constants . The Edit Constants form appears. 2. In the table at the top of the form, click the constant whose views you want to change. The constant name is displayed in the Constant eld and its views are displayed in the Value eld. 3. To add a view, a. In the Value eld, place the cursor where you want to add the new view. Note that the order of views is importantthe hierarchy editor uses the views in the order in which they are listed. b. In the View Choices list box, select the view that you want to add. c. Click Insert . 4. To remove a view, a. In the Value eld, double-click the view. b. Press the Delete key. 5. When you have nished editing the Value eld, click Set . Note: The Set button is greyed-out if the Constant eld is empty.
September 2002
108
Product Version 5.0
About the Edit Constants Form
Constant is a symbolic name that represents a view list. Value contains the list of views in the constant. Either type the view names or select them from the View Choices list box. View Choices contains the list of views from which you select views for the constant. You can customize the View Choices list. See Changing the Views in the View Choices List Box on page 110 for more information. Insert adds the selected views to the constant. Remove removes views from the constant. Set assigns the views to the constant and leaves the form open. Delete removes the constant name and its values. Close closes the form and saves your new or edited constants for the current session only. Help opens this manual.
September 2002
109
Product Version 5.0
Changing the Views in the View Choices List Box

The default list of views in the View Choices list box is dened by the hierEditor.constants variable in the your_install_dir /share/cdssetup/ hierEditor/env/hierEditorReg.env le. You cannot edit this registration le but you can change the list of views by adding the variable to a local hierEditor.env le. To change the views in the View Choices list box, 1. If you do not have a hierEditor.env le, create a le named hierEditor.env in a directory that is in your setup.loc le (for example, your $HOME directory or current working directory). Note: If you have multiple hierEditor.env les, the hierarchy editor determines which value to use based on the search order dened in the setup.loc le. 2. Add the following variable to the hierEditor.env le:
hierEditor.constants viewChoices string "view1 view2 view3 view4 ..."
where view1 , view2 , view3 , and view4 are the views that you want the View Choices list box to display. For example:
hierEditor.constants viewChoices string "abstract ahdl behavioral cdsSpice cmos_sch functional schematic spectre spectreS symbol"
For more information about the hierEditor.env le, see Appendix A, The hierEditor.env File.
Using Constants
To use a constant,
Type the name of the constant, preceded by a dollar sign ($), in any view list or stop list eld.
By default, the hierarchy editor displays the constant in the view lists or stop lists in which it is used. However, you can choose to display the expanded form of the constant (the list of views that the constant represents) instead of displaying the constant name. To display the expanded form of the constant,
Add the following variable to the hierEditor.env le:

hierEditor.display showConstInViewList boolean nil
For more information about the hierEditor.env le, see Appendix A, The hierEditor.env File.
September 2002
110
Product Version 5.0
4
Using Plug-Ins
I I I
About Plug-Ins on page 112 Loading Plug-In Applications on page 113 Removing Plug-In Applications on page 115
September 2002
111
Product Version 5.0
Cadence Hierarchy Editor User Guide Using Plug-Ins
About Plug-Ins
Plug-ins are applications that are added to the hierarchy editor and that are used from the hierarchy editor user interface. Some Cadence products are added to the hierarchy editor as plug-ins. The Plug-Ins Menu If at least one plug-in is added to the hierarchy editor, the hierarchy editor menu bar displays the Plug-Ins menu. If the Plug-Ins menu is not present, no plug-ins have been added to the hierarchy editor.
Plug-Ins Menu
September 2002
112
Product Version 5.0
Loading Plug-In Applications

The Plug-Ins menu contains all the applications that are available from the hierarchy editor. To use any application listed in the menu, you must rst load it. The hierarchy editor does not load the plug-ins by default. When you load a plug-in application, it appears in the hierarchy editor, typically as a menu on the menu bar or an icon on the tool bar. You can load a plug-in either from the command line when you start the hierarchy editor or from the hierarchy editor user interface. Loading a Plug-In from the Hierarchy Editor User Interface To load a plug-in application from the hierarchy editor user interface, 1. Start the hierarchy editor. The Plug-Ins menu appears on the menu bar. The menu lists the applications that you can load. A checked box next to a menu item indicates the application is already loaded; an unchecked box indicates the application is not loaded. Note: The Plug-Ins menu appears on the menu bar only if plug-ins have been added to the hierarchy editor. 2. From the Plug-Ins menu, select the plug-in application you want to load. For example, choose Plug-Ins AMS.
The application appears in the hierarchy editor as specied by the plug-in. For instance, a plug-in could appear as an additional menu in the hierarchy editor menu bar or an icon in the hierarchy editor tool bar. Also, in the Plug-Ins menu, the plug-in check box is now selected, which indicates that the plug-in is loaded.
September 2002
113
Product Version 5.0
Cadence Hierarchy Editor User Guide Using Plug-Ins For example, if you choose Plug-Ins AMS, the AMS menu appears in the menu bar.
AMS Menu
3. (Optional) If you want the hierarchy editor to automatically load the plug-in application every time it starts, save the hierarchy editor defaults with the File Save Defaults command. Loading a Plug-in from the Command Line To load a plug-in application from the command line, 1. Start the hierarchy editor with the following command:
cdsHierEditor -plugin pluginName [pluginOptions ]
To load more than one plug-in, use the following format:

cdsHierEditor -plugin pluginName [pluginOptions ] -plugin pluginName [pluginOptions ] ...
Note: -plugin must be the last argument specied with the cdsHierEditor command. It can be followed only by other -plugin arguments. When the hierarchy editor starts, the plug-in application appears in the hierarchy editor graphical user interface, typically as a menu in the menu bar or an icon in the tool bar. 2. (Optional) If you want the hierarchy editor to automatically load the plug-in application every time it starts, save the hierarchy editor defaults with the File Save Defaults command.
September 2002
114
Product Version 5.0
Removing Plug-In Applications

To remove a plug-in application from the hierarchy editor,
From the Plug-Ins menu, choose the application that you want to remove. The application menu or toolbar icon disappears from the hierarchy editor. Also, in the Plug-Ins menu, the plug-in check box is no longer selected, which indicates that the plug-in is not loaded.
You can load the plug-in application again by selecting it from the Plug-Ins menu.
September 2002
115
Product Version 5.0
September 2002
116
Product Version 5.0
A
The hierEditor.env File
The default display and form settings of the hierarchy editor are dened by variables that are registered in the your_install_dir /share/cdssetup/hierEditor/env/ hierEditorReg.env le. You cannot edit the hierEditorReg.env le but you can change the settings by creating a local environment le named hierEditor.env. The local hierEditor.env le is typically created with the File Save Defaults command and must be in a directory that is listed in your setup.loc le (for example, your home directory or current working directory). The hierEditor.env le contains only those settings that are different from the hierEditorReg.env le. The hierEditor.env le is read by the hierarchy editor when it is started. If you have multiple hierEditor.env les, the hierarchy editor determines which value to use for each variable based on the search order dened in the setup.loc le. For more information about the setup.loc le, see Chapter 3, Cadence Setup Search File: setup.loc, of the Cadence Application Infrastructure User Guide . Some of the form and display settings, typically the general user interface settings, are saved when you use the File Save Defaults command. For example, the options that you select in the Options form or in the View Filters form are saved to the hierEditor.env le when you use the File Save Defaults command. Other settings, such as the list of views in the Edit Constants form, can only be changed by editing the hierEditor.env le manually. If you want to set any of the following variables, you must add them to your local hierEditor.env le manually:
I
hierEditor.compatibility uselibSelect boolean nil useLibSelect species that the libSelect application is used to browse a library to open a conguration. It is used for compatibility with DFII applications.
hierEditor.constants viewChoices string "view1 view2 view3 ..." viewChoices denes the list of views in the View Choices list box in the Edit Constants form.
hierEditor.display.colorChooser bindingError string "red "
September 2002
117
Product Version 5.0
Cadence Hierarchy Editor User Guide The hierEditor.env File bindingError denes the color used to display text when there is a binding error.
I
hierEditor.display.colorChooser userBinding string "blue " userBinding denes the color used to indicate the bindings that users have changed.
hierEditor.display.colorChooser defaultBinding string "black " defaultBinding denes the color used to indicate that this is the default binding.
hierEditor.display.colorChooser notInUse string "darkOrange2 " notInUse denes the color used to indicate objects that are not in use.
hierEditor.display.colorChooser highlight string "khaki1 " highlight denes the color used to indicate an object that an external application wants to nd. For example, Virtuoso schematic composer users can add an instance probe and see it in the hierarchy editor.
hierEditor.display.colorChooser rowSelection string "#ccccff " rowSelection denes the color used to indicate a row selection in the table and the tree. Specify colors as hex rgb values in the format "# rrggbb " where rr is a two digit hex number for red, gg is a two digit hex number for green, and bb is a two digit hex number for blue.
hierEditor.display showConstInViewList boolean nil showConstInViewList, when set to nil, species that instead of displaying a constant, the hierarchy editor should display the expanded view list that the constant represents. The default value of this variable is t.
hierEditor.options.update autoGenPcdbFiles boolean t autoGenPcdbFiles, when set to t, species that the hierarchy editor should automatically generate a pc.db le from Verilog or VHDL.
hierEditor.options.update useNCCompilers boolean t useNCCompilers is used in conjunction with the autoGenPcdbFiles variable. When set to t, useNCCompilers species that the NC compilers (NC-Verilog and NC-VHDL) be used when generating a pc.db le from Verilog or VHDL.
September 2002
118
Product Version 5.0

Hier Editor

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Hier Editor

Hochgeladen von

Copyright:

Verfügbare Formate

Cadence Hierarchy Editor User Guide

Product Version 5.0 September 2002

Cadence Hierarchy Editor User Guide

1 Cadence Hierarchy Editor Overview

Product Version 5.0

Cadence Hierarchy Editor User Guide

Product Version 5.0

Cadence Hierarchy Editor User Guide

3 Changing Design Components

Product Version 5.0

Cadence Hierarchy Editor User Guide

102 103 105 106 106 108 109 110 110

4 Using Plug-Ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

A The hierEditor.env File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Product Version 5.0

Cadence Hierarchy Editor User Guide

Related Documents Typographic and Syntax Conventions

Typographic and Syntax Conventions

Product Version 5.0

Product Version 5.0

Cadence Hierarchy Editor User Guide

Setting Command-Line Options on page 20 Customizing Hierarchy Editor Columns on page 22

Displaying the Tree Structure on page 26

Filtering Cellviews on page 28

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

About the View Filters Form on page 29

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

What You Can Do with the Hierarchy Editor

Opening the Hierarchy Editor

To open the hierarchy editor from a UNIX shell, type

Product Version 5.0

Menu bar Toolbar Top cell information Global bindings section

Cell bindings section

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

About the Hierarchy Editor Menus

Product Version 5.0

Product Version 5.0

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

Using the Toolbar

Save a cong Open a cong Undo Redo

Update Tree view Show/hide instance table

To undock the toolbar,

To dock the toolbar,

Top Cell Section

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

Global Bindings Section

Cell Bindings Table

Icon indicating top-level cell

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

Instance Bindings Table

Product Version 5.0

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

Setting Command-Line Options

-h[elp] -lib libname -cell cellname -view viewname

Product Version 5.0

Cadence Hierarchy Editor User Guide Cadence Hierarchy Editor Overview

-cdslib filepath -log filename

-mpssession session -restore dirname