Hier Editor

118
Cadence ® Hierarchy Editor User Guide Product Version 5.0 September 2002

Transcript of Hier Editor

Page 1: Hier Editor

Cadence® Hierarchy Editor User Guide

Product Version 5.0September 2002

Page 2: Hier Editor

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 thisdocument are attributed to Cadence with the appropriate symbol. For queries regarding Cadence’s 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 thispublication may violate copyright, trademark, and other laws. Except as specified in this permission statement,this publication may not be copied, reproduced, modified, published, uploaded, posted, transmitted, ordistributed in any way, without prior written permission from Cadence. This statement grants you permission toprint 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 modified 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; and4. 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 acommitment on the part of Cadence. The information contained herein is the proprietary and confidentialinformation of Cadence or its licensors, and is supplied subject to, and may be used only by Cadence’s customerin accordance with, a written agreement between Cadence and its customer. Except as may be explicitly setforth in such agreement, Cadence does not make, and expressly disclaims, any representations or warrantiesas to the completeness, accuracy or usefulness of the information contained in this document. Cadence doesnot warrant that use of such information will not infringe any third party rights, nor does Cadence assume anyliability 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 inFAR52.227-14 and DFAR252.227-7013 et seq. or its successor.

Page 3: Hier Editor

Cadence Hierarchy Editor User Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Typographic and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1Cadence Hierarchy Editor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What You Can Do with the Hierarchy Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Opening the Hierarchy Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About the Hierarchy Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Using the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Top Cell Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Global Bindings Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Cell Bindings Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Instance Bindings Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Setting Command-Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Customizing Hierarchy Editor Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Specifying Attributes to Display in the Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22About the Options Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Changing Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Resizing Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Updating the Configuration Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Expanding and Collapsing Branches of Your Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Displaying the Tree Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Filtering Cellviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

About the View Filters Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

September 2002 3 Product Version 5.0

Page 4: Hier Editor

Cadence Hierarchy Editor User Guide

Viewing the Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Changing the Hierarchy Editor Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Saving Custom Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Exiting the Hierarchy Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2Creating Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

About the Configuration View of a Design Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Opening Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Opening Configurations in Read-Only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About the Open Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Filtering the Configurations in the Open Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40About the Browser Filters Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating a New Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About the New Configuration Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45About the Choose the Top Cell Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Editing Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Editing the Cell Bindings and Instance Bindings Tables . . . . . . . . . . . . . . . . . . . . . . . 47

Verifying Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Viewing the Description File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Verifying Cell Binding Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51About the Explain Form for a Selected Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Verifying Instance Binding Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53About the Explain Form for a Selected Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Verifying Occurrence Binding Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54About the Explain Form for a Selected Occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Working with Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Using Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56About the Use Template Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Creating Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Copying Your Created Template to Another Location . . . . . . . . . . . . . . . . . . . . . . . . . 58

Saving Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Saving a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59About the Save As Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Saving VHDL Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

September 2002 4 Product Version 5.0

Page 5: Hier Editor

Cadence Hierarchy Editor User Guide

About the Save As VHDL Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Saving Verilog Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62About the Save As Verilog Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Updating a Virtuoso Schematic Composer Configuration Using the Hierarchy EditorInterface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3Changing Design Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Global Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Cell Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Instance Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Occurrence Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71How a Library Is Selected for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71How a View Is Selected for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Defining Rules at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Defining a View List at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Defining a Library List at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Defining a Stop List at the Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Defining Rules at the Cell Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Changing Library Bindings on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Changing View Bindings on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Defining Stop Points on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Defining Bind-to-Open on a Per-Cell Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Defining Rules at the Instance Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Changing View Bindings on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Changing Library Bindings on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . 84Defining Stop Points on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Defining Bind-to-Open on a Per-Instance Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Changing Instance Bindings Inside a Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Changing Instance Bindings Created by a Generate Statement . . . . . . . . . . . . . . . . 91

Defining Rules at the Occurrence Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92About Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92How Occurrences Are Different from Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Defining Occurrence Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

September 2002 5 Product Version 5.0

Page 6: Hier Editor

Cadence Hierarchy Editor User Guide

Defining Occurrence Stop Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Defining Occurrence-Level Bind-to-Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Changing Binding Data Color Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Using Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Creating Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Editing Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108About the Edit Constants Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Changing the Views in the View Choices List Box . . . . . . . . . . . . . . . . . . . . . . . . . . 110Using Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

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

About Plug-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Loading Plug-In Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Removing Plug-In Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

AThe hierEditor.env File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

September 2002 6 Product Version 5.0

Page 7: Hier Editor

Cadence Hierarchy Editor User Guide

Preface

The Cadence Hierarchy Editor User Guide describes the Cadence® Hierarchy Editor,which lets you browse a design hierarchy and create and edit design configurations.

The preface discusses the following:

■ Related Documents

■ Typographic and Syntax Conventions

Related Documents

To find information about other Cadence products that are used with the hierarchy editor, referto the following manuals:

■ Virtuoso Schematic Composer User Guide describes how to use the schematiccapture product.

■ Cadence Design Framework II User Guide describes terms and how to start yoursystem.

■ Cadence AMS Environment User Guide describes the analog mixed signalenvironment.

Typographic and Syntax Conventions

This section describes typographic and syntax conventions used in this manual.

text Indicates text you must type exactly as it is presented.

variable Indicates text that you must replace with an appropriate value.

[ ] Denotes optional arguments. When used with vertical bars, theyenclose a list of choices from which you can choose one.

{ } Used with vertical bars and encloses a list of choices from whichyou must choose one.

September 2002 7 Product Version 5.0

Page 8: Hier Editor

Cadence Hierarchy Editor User GuidePreface

| Separates a choice of options.

… Indicates that you can repeat the previous argument.

text Indicates names of manuals, menu commands, form buttons,and form fields.

September 2002 8 Product Version 5.0

Page 9: Hier Editor

Cadence Hierarchy Editor User Guide

1Cadence Hierarchy Editor Overview

This chapter covers the following topics:

■ 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

■ 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

■ Updating the Configuration 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

September 2002 9 Product Version 5.0

Page 10: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

❑ 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

Page 11: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

What You Can Do with the Hierarchy Editor

The Cadence® Hierarchy Editor lets you view many levels of a single design using either atable view or a tree view. The hierarchy editor also lets you create a configuration file thatprovides expansion information for mixed-signal partitioning. A configuration file is theexpand.cfg file, which specifies how a design is to be expanded.

You can use the hierarchy editor to

■ Display the configuration file 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 configurations

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 thecdsHierEditor command. For more information on the options you can use, refer to

September 2002 11 Product Version 5.0

Page 12: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

“Setting Command-Line Options” on page 20.

Toolbar

Viewing area

Status bar

Messagearea

Menu bar

Top cellinformation

Global bindingssection

Cell bindingssection

September 2002 12 Product Version 5.0

Page 13: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

About the Hierarchy Editor Menus

The menu bar displays the hierarchy editor menus.

File Menu

File – New creates a new configuration.

File – Open opens an existing configuration for editing.

File – Open (Read-Only) opens a configuration for viewing.

File – Save (Needed) saves the opened configuration.

File – Save As saves the opened configuration under a new name.

File – Save As VHDL saves the opened configuration as a VHDL file.

File – Save As Verilog saves the opened configuration as a Verilog® file.

File – Save Defaults saves your settings.

Exit closes the hierarchy editor.

September 2002 13 Product Version 5.0

Page 14: Hier Editor

Cadence Hierarchy Editor User GuideCadence 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 theconfiguration.

View Menu

View menu commands let you set the display options for the hierarchy editor. You can hidethe table, tree, top cell, global bindings, toolbar, message area, and status bar in the hierarchyeditor window.

September 2002 14 Product Version 5.0

Page 15: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

View – Update recomputes the hierarchy based on the rules you entered. This command isunavailable until you have opened a configuration.

Note: You can also select the Automatic Update option, which is available in theOptions form, to automatically update your configuration 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 filters.

View – Options opens the Options form to let you select the columns you want to display inthe 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 “SavingCustom Settings” on page 32 for more information.

September 2002 15 Product Version 5.0

Page 16: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

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 aseparate window for easy access.

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 floatingtoolbar on your desktop.

Top Cell Section

The Top Cell section contains the library, cell, and view names of the top cellview of theconfiguration you opened. This is the root cellview of your hierarchy.

Click here and drag the mouseto dock and undock the toolbar

Open a config

Save a config

Create anew config

Open a cellviewfor editing

Open a cellviewfor viewing

Update

Tree view

Explain

Show/hide instance table

Table view

RedoUndo

September 2002 16 Product Version 5.0

Page 17: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Global Bindings Section

The values in the library, view, and stop lists in the Global Bindings section are the defaultvalues from the configuration.

■ Library List is a list of libraries from which cells are selected. Libraries are listed in orderof preference.

■ View List is the list of views or default rules specified in order of preference. Forexample, if the view list contains the views tbench_1, schematic, and dataflow inthis order, the netlister first looks for a tbench_1 view. If none is found, it looks for aschematic 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 stopand when a cell should be considered a leaf node in the hierarchy.

Cell Bindings Table

The Cell Bindings table displays the views that are bound to a cell.

Icon indicatingtop-level cell

September 2002 17 Product Version 5.0

Page 18: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Instance Bindings Table

The Instance Bindings table displays all the instances in the block you selected and theirbindings. Instances are described in a library-cell-view format.

Use the maximize button to expand the Instance Bindings table and the minimize button tocontract the table.

Messages

The message area near the bottom of the window displays error and warning messages andinformation for hierarchy editor actions. Scroll bars appear if the window is not large enoughto display the full message.

Status Bar

The status bar at the bottom of the window displays the state of the hierarchy editor, whetherfilters are on or off, and the name space in which you are operating. When you position the

Maximize button

Minimize button

September 2002 18 Product Version 5.0

Page 19: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

cursor over a menu item or toolbar icon, the status bar tells you what will happen if you clickon the item or icon.

September 2002 19 Product Version 5.0

Page 20: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Setting Command-Line Options

When you run the hierarchy editor from the command line, you can specify the followingoptions.

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 hierarchyeditor ignores all arguments after -plugin, except another -plugin argument.

Arguments

-h[elp] Prints a list and a brief description of the command-lineoptions.

-lib libname Specifies the library name of the configuration to beopened.

-cell cellname Specifies the cell name of the configuration to beopened.

-view viewname Specifies the view name of the configuration to beopened. You must specify all three parts of the -lib,-cell, and -view options for the command to becomplete.

September 2002 20 Product Version 5.0

Page 21: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

-mode {r|w|a} Specifies the mode (read, write, or append) thehierarchy editor uses to open the configuration. Thedefault mode is append.

Note: The -mode w (write) option erases all data in theconfiguration file you specify and opens the emptyconfiguration file.

-namespace nmpName Specifies the name space to operate in, for example,Verilog, VHDL, or CDBA. All names are thendisplayed in that name space, regardless of the sourcedescription that is used.

The default name space is CDBA.

-cdslib filepath Specifies the cds.lib file to load. The cds.lib filespecifies the libraries to use.

-log filename Specifies the path and name of a log file in whichcommands and messages are recorded. If you do notspecify this option, no log file is created.

-mpshost host Specifies the Message Passing System (MPS) host onwhich the cdsNameServer is running and to which youwant to connect. If the host is not specified, thehierarchy editor connects to the local host.

-mpssession session Specifies which MPS session to join.

-restore dirname Loads the hierEditor.env file from the specifieddirectory after other hierarchy editor files (found withthe Cadence File Search facility) have been loaded.

-tree Indicates that the tree view is to be displayed atstartup. If this argument is not specified, the table viewis displayed.

-version Prints the version and copyright information and exits.

-ignoreRootConfig Ignores the root configuration in select and highlightmessages between the hierarchy editor and Cadence®

Design Framework II (DFII) applications.

By default, if you are not editing the same rootconfiguration in your DFII application and the hierarchyeditor, select and highlight messages between the twoapplications are ignored. If you set the-ignoreRootConfig option, the hierarchy editorignores the root configuration.

September 2002 21 Product Version 5.0

Page 22: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Customizing Hierarchy Editor Columns

The hierarchy editor lets you specify the attributes you want to display in the columns, changethe 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.

-plugin pluginName[pluginOptions ...]

Loads the plug-ins you specify. You can specifycommand-line options for the plug-ins. To load morethan one plug-in, type -plugin before each plug-inname.

If you use the -plugin option, you must specify it asthe last argument. The hierarchy editor ignores allarguments after -plugin, except another -pluginargument.

For more information about plug-ins, see Chapter 4,“Using Plug-Ins.”

Note: The plug-ins you specify must be installed in theyour_install_dir/share/cdssetup/hierEditor/plugins directory.

September 2002 22 Product Version 5.0

Page 23: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

The Options form appears.

2. Click a tab for displaying a specific set of related attributes.

For example, to select the attributes you want to display in the tree structure, click theTree 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

Page 24: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

About the Options Form

The Options form lets you specify the attributes you want to display in the cell table, instancetable, and tree view of the hierarchy editor. It also lets you specify the automatic updateoption.

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 acomplete 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 field in which you can type a specific view to use for the cell.

Inherited View List displays a field in which you can modify the inherited view listfor the cell. The default inherited view list is the global view list.

Inherited Lib List displays a field in which you can modify the inherited library listfor 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 acomplete 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 field in which you can type a specific view to use for theinstance.

Inherited View List displays a field in which you can modify the inherited view listfor the instance.

Inherited Lib List displays a field in which you can modify the inherited library listfor the instance.

The Tree tab lets you select the columns that appear in the tree structure.

Show Tree Columns

View to Use displays a field in which you can type a specific view to use for the cell.

September 2002 24 Product Version 5.0

Page 25: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Inherited View List displays a field in which you can modify the inherited view list.

Inherited Lib List displays a field in which you can modify the inherited library list.

Expand Mode

By Instance displays all the instances for the selected cell when you expand abranch.

By Instance Grouping displays similar instances grouped together when youexpand a branch. The number of instances is displayed.

The General tab lets you set the following option:

Automatic Update updates the configuration automatically every time you make achange. If this option is selected, you do not have to click the Update icon in the toolbaror 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 canhave 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 themouse.

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 narrowthe column.

September 2002 25 Product Version 5.0

Page 26: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Updating the Configuration Automatically

You can set an option to update the configuration automatically whenever you make achange. For example, if you open a configuration and add a view to the global view list, thehierarchy 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 chooseView – Update to view the changes you make.

The default setting of the automatic update option is off.

To update configurations 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 oneof the following:

Displaying the Tree Structure

The tree view displays the hierarchy of your design.

To display the tree view,

UNIX NT Meaning

[+] Item contains instances not shown. The substructure ishidden (collapsed or locked).

[-] Item contains instances that are shown. The substructure isdisplayed (expanded or unlocked).

Item is a leaf cellview with no instances below it.

September 2002 26 Product Version 5.0

Page 27: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

➤ 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 treestructure.

September 2002 27 Product Version 5.0

Page 28: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Filtering Cellviews

You can find cellviews quickly by using filters.

To filter cellviews,

1. Choose View – Filters.

The View Filters form appears.

2. In the Library, Cell, and View fields, specify whole words or character strings to narrowyour cellview search.

You can use the following wildcards:

Character Match Criteria

? Matches any single character

[list] Matches any single character in list

[lower-upper] Matches any character in the range between lower andupper

* Matches any pattern

September 2002 28 Product Version 5.0

Page 29: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

For example, to find all the libraries that begin with p, in the Library field, type p*.

Pattern matching is case sensitive. You can also specify multiple patterns by separatingthe patterns with spaces.

3. Select the type of data (for example, items at the leaf level or unbound items) you wantto 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 editoruses the selected filter criteria until you turn off the filters.

Note: The filter setting returns to the default setting when you start another hierarchyeditor session. You must save your settings using the File – Save Defaults commandto save the filter 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 fields, you can:

❑ Specify whole words or character strings

❑ Specify multiple patterns; separate the patterns with spaces

❑ Use the following wildcards:

? Matches any single character

[list] Matches any single character in list

September 2002 29 Product Version 5.0

Page 30: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Note: Pattern matching is case sensitive.

Show leaf instances and cellviews lets you specify whether you want to display instancesand cellviews that are at the leaf level.

Show instances and cellviews that are not bound lets you specify whether you want todisplay unbound instances and cellviews.

Only show entries that have an explicit rule lets you specify whether you want to displayall 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 filter off. The hierarchy editordisplays all cellviews and instances. The status bar displays Filters OFF.

Help opens this manual.

[lower-upper] Matches any character in the range between lower andupper

* Matches any pattern

September 2002 30 Product Version 5.0

Page 31: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Viewing the Legend

The Legend dialog box provides information about the icons and colors that are used in thehierarchy 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 ColorDefinitions” on page 105.

September 2002 31 Product Version 5.0

Page 32: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

Changing the Hierarchy Editor Fonts

The hierarchy editor’s fonts are determined by the settings in thecdsresource.properties file. The default fonts are defined in thecdsresource.properties file in the your_install_dir/share/cdssetup/symphony/resources directory.

You can have multiple cdsresource.properties files. The hierarchy editor determineswhich file to use based on the search order defined in the setup.loc file.

To change the hierarchy editor fonts,

1. Copy the following file to a directory that is in your setup.loc file (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 file.

The font settings are defined by the CDS.textFont property, which has the followingformat:

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 whichcdsresource.properties file 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 saveyour settings with the Save Defaults form.

You can save and restore the following settings:

■ The height and width of the hierarchy editor window

■ The location of the hierarchy editor window on the screen

■ The filter settings

September 2002 32 Product Version 5.0

Page 33: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

■ The view options to show or hide the toolbar, status bar, message area, or the GlobalBindings, 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

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 file in the directory you specified.

The next time you start the hierarchy editor, it loads the hierEditor.env file. If thehierEditor.env file is not in a directory that is found by the Cadence searchmechanism, you can load the file by starting the hierarchy editor with the -restoredirname command. For more information about the hierEditor.env file, seeAppendix 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.

September 2002 33 Product Version 5.0

Page 34: Hier Editor

Cadence Hierarchy Editor User GuideCadence Hierarchy Editor Overview

If you have not saved the configuration changes you have made, a Warning form asksyou 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 applicationswith which the hierarchy editor might have been communicating.

September 2002 34 Product Version 5.0

Page 35: Hier Editor

Cadence Hierarchy Editor User Guide

2Creating Configurations

This chapter covers the following topics:

■ About the Configuration View of a Design Hierarchy on page 37

❑ Opening Configurations on page 37

❑ Opening Configurations in Read-Only Mode on page 39

❑ About the Open Form on page 39

❑ Filtering the Configurations in the Open Form on page 40

❑ About the Browser Filters Form on page 41

■ Creating a New Configuration on page 43

❑ About the New Configuration Form on page 45

❑ About the Choose the Top Cell Form on page 46

■ Editing Configurations on page 46

❑ Editing the Cell Bindings and Instance Bindings Tables on page 47

■ Verifying Configuration 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 35 Product Version 5.0

Page 36: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

❑ Using Templates on page 56

❑ Creating Templates on page 57

❑ Copying Your Created Template to Another Location on page 58

■ Saving Configurations on page 59

❑ Saving a Configuration on page 59

❑ Saving VHDL Configurations on page 61

❑ Saving Verilog Configurations on page 62

❑ Updating a Virtuoso Schematic Composer Configuration Using the Hierarchy EditorInterface on page 64

September 2002 36 Product Version 5.0

Page 37: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

About the Configuration View of a Design Hierarchy

The configuration view of a design is the definition that the hierarchy editor understands andcan open. It is a cellview that stores a configuration file that contains the libraries, cells, andviews of a design. You can browse

■ The library directory, which contains a collection of cells that correspond to a specificprocess technology

■ The cell directory, which contains the design object that forms an individual building blockof a chip or system

■ The view, which is a defined representation of a cell such as layout or a schematic

The main components of a configuration are the top cellview, which is the root of the designand the configuration rules.

In the above example, the designLib library contains two configuration definitions identifiedby the view names mixedConfig and logicConfig. You can use the hierarchy editor toopen the mixedConfig or the logicConfig configuration.

Opening Configurations

To open an existing configuration 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 specified for the hierarchy editor to open a configurationand load the data.

designLib

logicConfigschematic mixedConfig

pulsegen Top cell name

layout

View name

Library name

September 2002 37 Product Version 5.0

Page 38: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

If you do not specify a cellview (library, cell, and view names) when you run thecdsHierEditor command, the hierarchy editor opens without loading aconfiguration.

Note: A cellview is the library, cell, and view names.

To open a configuration 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 specific 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, ortype the name in the Library field.

The libraries are displayed in outline form. The cds.lib file is at the top of the designhierarchy. The libraries defined in the cds.lib file are at the next level, the cells are alevel below the libraries, and the views are a level below the cells. For more informationabout Cadence® library structures, refer to the Cadence Application InfrastructureUser Guide.

The selected library name appears in the Library field.

September 2002 38 Product Version 5.0

Page 39: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

4. Click the expansion icon for the library, then select the cell you want.

The selected cell name appears in the Cell field.

5. Click the expansion icon of the cell, then select the view you want.

Note: The browser displays only configuration views and expands only those cells thatcontain configuration views.

The selected view name appears in the View field.

6. When all the fields in the form are filled, click OK.

The hierarchy editor displays your data in the Top Cell, Global, and Cell Bindingssections.

Note: Cadence Design Framework II (DFII) users can use the libSelect application toopen configurations in the hierarchy editor. You must enable libSelect by setting thecompatibility mode in the hierEditor.env file. For more information on thehierEditor.env file, refer to Appendix A, “The hierEditor.env File.”

Opening Configurations in Read-Only Mode

To open a configuration 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 Configurations” on page 37.

The configuration is opened but cannot be edited. If the hierarchy editor cannot open aconfiguration, an Open Error dialog box appears.

About the Open Form

Configuration

Library lets you type the name of a library specified in your cds.lib file. You can alsofill in this field by selecting a library in the Browse section.

Cell lets you type the name of the cell you want to open. You can also fill in this field byselecting a cell in the Browse section.

View lets you type the name of the configuration view you want to open. You can also fillin this field by selecting a view in the Browse section.

September 2002 39 Product Version 5.0

Page 40: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

Browse lets you select the library, cell, and view. The library, cell, and view that you selectare displayed in the Library, Cell, and View text fields in the Configuration section. Notethat the browser displays only configuration views and expands only those cells that containconfiguration views.

You can set filters to display only a specific set of libraries, cells, and views in the Browsesection. See “Filtering the Configurations in the Open Form” on page 40 for more information.

OK opens the configuration 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 onlyparts of the library structure that match your filter criteria.

Help opens this manual.

Filtering the Configurations in the Open Form

You can set filters to display only a specific set of libraries, cells, and views in the Browsesection of the Open form.

1. In the Open form, click Filters.

The Browser Filters form appears.

2. In the Library, Cell, and View fields, specify whole words or character strings to narrowyour search.

September 2002 40 Product Version 5.0

Page 41: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

You can use the following wildcard characters:

For example, to find all the libraries that begin with p, in the Library field, type p*.

Pattern matching is case sensitive. You can also specify multiple patterns by separatingthe 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, basedon the filters you set.

Note: To return to the default filter 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 fields, you can:

❑ Specify whole words or character strings

❑ Specify multiple patterns; separate the patterns with spaces

❑ Use the following wildcards:

Character Match Criteria

? Matches any single character

[list] Matches any single character in list

[lower-upper] Matches any character in the range between lower andupper

* Matches any pattern

? Matches any single character

September 2002 41 Product Version 5.0

Page 42: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

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 theform.

Defaults restores the default settings.

Help opens this manual.

[list] Matches any single character in list

[lower-upper] Matches any character in the range between lower andupper

* Matches any pattern

September 2002 42 Product Version 5.0

Page 43: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

Creating a New Configuration

Use these steps to create and use a configuration with the hierarchy editor:

To create a new configuration,

1. Open the hierarchy editor.

The hierarchy editor window appears.

2. Choose File – New or press Control-n.

Define a global stop list

Define a global view list

Specify cell bindings

Specify instance bindings

Save the configuration cellview file

Update the configuration cellview

Run your application

Quit thehierarchyeditor

YesNo

Check results

Verify theconfigurationcellview

optional

required

Define a global library list

Open a new configuration file

Open or reopen the application where the design was generated

OK?

September 2002 43 Product Version 5.0

Page 44: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

The New Configuration form appears.

3. In the Top Cell section, do one of the following:

❑ In the Library, Cell, and View fields, type the name of the library, cell, and view thatyou 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 fields, type a library list, view list, andstop list to specify the default bindings for the entire design.

The global library list is a list of libraries that determines the libraries from whicheach cell is obtained. The global view list is a list of views that determines which viewis selected for each object in the design. The global stop list specifies a list of viewsthat 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

Page 45: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

You can use constants in the view list and stop list. A constant is a symbolic nameused to represent a set of views. For more information on creating and usingconstants, refer to “Using Constants” on page 106.

The Stop List field can be empty.

❑ Click Use Template to select a template that is compatible with the simulator youare running. Templates for simulators provide lists of views that are most often usedfor those simulators.

Refer to “Working with Templates” on page 56 to use prepared templates or tocreate your own templates.

Note: If the template you selected has filled in the Top Cell section of the NewConfiguration form, replace the names in the Library, Cell, and View fields with thetop cellview you want to use.

5. (Optional) In the Description field, type a brief statement describing the newconfiguration.

6. Click OK.

The New Configuration form closes. The hierarchy editor displays the new configuration.

See “Saving Configurations” on page 59 for information about saving your new configuration.

About the New Configuration Form

Top Cell specifies the cell at the highest level of the configuration, the top cellview.

Library specifies the name of the library that contains the top cellview.

Cell specifies the cell name of the top cellview.

View specifies the view name of the top cellview.

Browse opens the Choose the Top Cell form for selecting the top cellview of theconfiguration.

Global Bindings specify default bindings for the entire design.

Library List lets you specify libraries for cells that do not have library bindings. List thelibraries in the order you want them searched.

View List lets you specify the views you want in your configuration in order ofpreference. The view list applies to every level of the configuration and determines which

September 2002 45 Product Version 5.0

Page 46: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

view is selected for every object in the design, unless overridden by a cell or instancebinding.

Stop List lets you specify cellviews that are to be treated as leaf nodes, that is, they arenot to be expanded. This field can be empty.

Description lets you enter a brief statement describing the configuration.

OK sets the values you entered and closes the form.

Cancel closes the New Configuration form without applying your values.

Use Template lets you select a template from a list of predefined 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 levelof the configuration, the top cellview.

Cell lets you specify the cell name of the top cellview of the configuration.

View lets you specify the view name of the top cellview of the configuration.

Browse lets you select the top cellview of the configuration. The library, cell, and view youselect are displayed in the Library, Cell, and View text fields 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 onlyparts of the library structure.

Help opens this manual.

Editing Configurations

This section provides an overview of how to edit a configuration. For a more detaileddescription on how to make changes and specify rules for configurations, see Chapter 3,“Changing Design Components.”.

September 2002 46 Product Version 5.0

Page 47: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

Note: You cannot edit sub-configurations—a sub-configuration is a configuration that iscontained within a configuration. To edit a sub-configuration, you must open it separately asa configuration in the hierarchy editor.

To edit a configuration using the hierarchy editor,

1. Open the configuration you want to edit.

2. Edit the configuration.

❑ In the Top Cell section, edit the library name, cell name, or view name of the topcellview of the configuration.

❑ In the Global Bindings section, edit the library list, view list, and stop list. Separatethe entries in the lists with spaces.

Note: Library bindings in CDBA are fixed and cannot be overridden. If your data isCDBA (DFII only), the hierarchy editor ignores any library list you enter in the GlobalBindings 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 identified with a green triangle in theInfo 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 orInstance Bindings sections.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration is automatically updated.

Note: Updating the display is optional, but you must save the information to be able touse the edited configuration.

4. Click File – Save or press Control-s.

Note: Other Cadence software tools cannot access new or changed configuration filesuntil 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 wantto change.

September 2002 47 Product Version 5.0

Page 48: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

2. Do one of the following:

❑ Click in the View to Use column of the cell or instance, type the new view, thenpress Return.

❑ Right-click anywhere in the row of the cell or instance you want to change and selecta 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 userbindings.

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 notrequired because your configuration 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 Listcolumn 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 modified view list appears in the Inherited View List column in the color used todisplay user bindings.

4. To view your changes, choose View – Update.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration 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

Page 49: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

1. In the Cell Bindings or Instance Bindings section, select the cell or instance you wantto 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 notrequired because your configuration 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 thatshare the same rules,

1. Choose View – Options.

The Options form appears.

September 2002 49 Product Version 5.0

Page 50: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

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 ofinstances.

8. Press Return.

The view you selected is applied to all the instances and appears in the color used todisplay 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 notrequired because your configuration is automatically updated.

10. To save the changes, choose File – Save or press Control-s.

Verifying Configuration Data

You can check the configuration data of your design in the following ways:

■ Viewing the Description File

■ Seeing what binding rules were used to select any view in the hierarchy. You can do thisby

❑ 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 file,

➤ Choose Edit – Description.

September 2002 50 Product Version 5.0

Page 51: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

The Edit Description form appears.

Description displays a description of the configuration, 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 configuration,

1. In the Edit Description form, edit the description in the Description field.

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:

■ In the Cell Bindings table, right-click on a cellview and, from the pop-up menu, selectExplain.

■ In the Cell Bindings table, select a cellview and, from the toolbar, click the Explain icon.

September 2002 51 Product Version 5.0

Page 52: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

The Explain form appears.

About the Explain Form for a Selected Cell

Selection displays the master cellview for the selected cell

Library specifies the master library of the cell.

Cell specifies the master cell of the cell.

View specifies the master view of the cell.

Note: If the Library, Cell, or View fields display **UNBOUND**, the cell has a bind-to-open 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

Page 53: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

Help opens this manual.

Verifying Instance Binding Rules

To see which binding rules were used for an instance, do one of the following:

■ In the Instance Bindings table, right-click on the instance whose rules you want tocheck and, from the pop-up menu, select Explain.

■ In the Instance Bindings table, select the instance and, from the toolbar, click theExplain icon.

The Explain form appears.

About the Explain Form for a Selected Instance

Selection displays the cellview that contains the selected instance

Library specifies the library of the cellview that contains the selected instance.

Cell specifies the cell that contains the selected instance.

September 2002 53 Product Version 5.0

Page 54: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

View specifies the view of the cellview that contains the selected instance.

Instance specifies 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 specifies the master library of the selected instance.

Cell specifies the master cell of the selected instance.

View specifies the master view of the selected instance.

Note: If the Library, Cell, or View fields display **UNBOUND**, the instance has a bind-to-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 theoccurrence.

2. From the pop-up menu, select Explain.

September 2002 54 Product Version 5.0

Page 55: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

The Explain form appears.

About the Explain Form for a Selected Occurrence

Selection specifies 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 specifies the library of the selected occurrence.

Cell specifies the cell of the selected occurrence.

View specifies the view of the selected occurrence.

Note: If the Library, Cell, or View fields display **UNBOUND**, the occurrence has abind-to-open attribute.

Explanation describes the bindings for the selected occurrence.

Close closes the form.

September 2002 55 Product Version 5.0

Page 56: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

Help opens this manual.

Working with Templates

Templates let you build configurations using pre-defined view lists and stop lists. Thehierarchy editor includes templates for some simulators that are compatible with Cadencesoftware. You can also create your own templates.

Using Templates

To use a template,

1. Choose File – New or press Control-n.

The New Configuration form appears.

2. In the New Configuration form, click Use Template.

The Use Template form appears.

3. Do one of the following:

❑ If you want to use a pre-defined template, or a template that you have created andplaced 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 field, type the path to the template.

September 2002 56 Product Version 5.0

Page 57: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

4. Click OK.

The Use Template form closes. The New Configuration form is filled in with the view listand stop list data from the template.

Note: If there is already information in the Top Cell section, selecting a template doesnot overwrite that information. If the Top Cell fields are empty when you select atemplate, the hierarchy editor fills them in with the default values.

5. In the New Configuration 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-defined templates for simulators thatare compatible with Cadence software. The listbox also lists any other templates that youplaced 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> andspecify the path in the From File field.

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 simulatoror other design-specific 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 promptsyou to save your changes.

The New Configuration form appears.

September 2002 57 Product Version 5.0

Page 58: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

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” onpage 106.

4. (Optional) In the Description field, type a brief statement about the new template.

5. Click OK.

The New Configuration form closes.

The hierarchy editor displays the new configuration.

6. Choose File – Save As to save your new configuration.

The Save As form appears.

7. In the Browse section, select the library in which you want to save the new configuration.

The library is displayed in the Library field in the Configuration section.

8. In the Cell field, type the name of the cell.

9. In the View field, type the name of the view.

Note: The name you give to the cell and view of the configuration do not have to matchthe 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 UseTemplate button on the New Configuration form.

By default, configurations are saved in the expand.cfg file, which is located in yourlibrary/cell/configuration_view directory.

To copy your template to another location,

1. Change directories to the /library/cell/view directory in which you saved thetemplate.

2. Use a text editor such as vi to verify that the configuration file is correct.

September 2002 58 Product Version 5.0

Page 59: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

3. Copy the configuration file 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 NewConfiguration form.

Saving Configurations

When you save a configuration in the hierarchy editor, it is saved in the expand.cfg file inthe configuration view. The configuration view directory also contains an expand.cfg% file,which is the previously-saved version of the expand.cfg file.

You can also save VHDL and Verilog® configurations. See the following topics for moreinformation:

■ “Saving VHDL Configurations” on page 61

■ “Saving Verilog Configurations” on page 62

If you are a Virtuoso® Schematic Composer user, see “Updating a Virtuoso SchematicComposer Configuration Using the Hierarchy Editor Interface” on page 64.

Note: Other applications cannot access changed configuration files until they have beensaved in the hierarchy editor.

Saving a Configuration

To save a configuration,

➤ Choose File – Save or press Control-s.

The hierarchy editor saves the configuration.

To save a configuration using the File – Save As command,

1. Choose File – Save As.

September 2002 59 Product Version 5.0

Page 60: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

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 configuration by typing the name in theLibrary field or selecting the library from the Browse section.

3. Specify the cell in which you want to save the configuration by typing the name in theCell field or selecting the cell from the Browse section.

4. In the View field, type the name of the new configuration view.

Note: The name you give to the cell and view of the configuration do not have to matchthe name of the cell and view of the top-level cellview.

5. Click OK.

The next time you want to use this configuration, you can access it from the Open Browsesection 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 theconfiguration.

Cell lets you specify the name of the cell in which you want to save the configuration.

September 2002 60 Product Version 5.0

Page 61: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

View lets you specify the name of the new configuration view.

OK saves the file you selected.

Cancel cancels your selections and closes the form.

Browse lets you select the library, cell, and view for the new configuration. The library, cell,and view you select are displayed in the Library, Cell, and View text fields in theConfiguration section. Note that the browser displays only configuration views and expandsonly those cells that contain configuration views.

Filters lets you narrow your search by displaying a subset of libraries and cells that matchyour search criteria.

Help opens this manual.

Saving VHDL Configurations

The hierarchy editor provides the File – Save As VHDL command to save a configurationin VHDL syntax that can be read by VHDL tools. A VHDL configuration is always saved in aview called configuration.

To save a configuration for VHDL applications,

1. Choose File – Save As VHDL.

The Save As VHDL form appears.

September 2002 61 Product Version 5.0

Page 62: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

2. Specify the name of the library and cell in which you want to save the VHDL configurationby doing one of the following:

❑ Type the names in the Library and Cell fields.

❑ Select the library and cell from the Browse section.

The View field is automatically set to configuration.

3. Click OK.

Note: Saving a VHDL configuration does not save it in a format that can be read andedited by the hierarchy editor. You must also save the configuration with the File – Saveor File – Save As command in order for it to be read by the hierarchy editor.

About the Save As VHDL Form

Configuration

Library specifies the name of the library in which you want to save the configuration.

Cell specifies the name of the cell in which you want to save the configuration.

View specifies the name of the configuration view. For VHDL configurations, the viewname is always configuration.

OK saves the configuration.

Cancel discards your selections and closes the form.

Filters lets you narrow your search by displaying a subset of libraries and cells that matchyour search criteria.

Help opens this manual.

Saving Verilog Configurations

The hierarchy editor provides the File – Save As Verilog command to save a configurationin Verilog syntax that can be read by Verilog tools.

To save a configuration for Verilog applications,

1. Choose File – Save As Verilog.

September 2002 62 Product Version 5.0

Page 63: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

The Save As Verilog form appears.

2. Specify the file in which you want to save the Verilog configuration by doing one of thefollowing:

a. In the Look in field, type the path to the directory in which you want to save theconfiguration.

b. In the File field, type the name of the file.

The default value of this field is verilog.f.

or

a. Select the file in which you want to save the Verilog configuration from the filebrowser.

Note: You can also type a filter expression in the Filters field to narrow your search forthe directory to which you want to save your Verilog file.

3. Click OK.

September 2002 63 Product Version 5.0

Page 64: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

About the Save As Verilog Form

Look in lets you type the path to a directory or use the arrow button to display a drop-down menu of all the directories in the path to the root directory.

The file browser displays all the directories and subdirectories of the current directorydisplayed in the Look in field.

File lets you type a name for the Verilog file.

Filters let you type a filter expression to display the directories you want to see. Forexample, to display all the directories that begin with c, type *.c

The files that match the filter 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 Configuration Using theHierarchy Editor Interface

The Virtuoso schematic composer provides an interface to the hierarchy editor. Using theinterface, you can update the configuration of a cellview.

To update a configuration which was generated from the schematic composer, do thefollowing:

1. Open the configuration view of the design you want to reconfigure.

The hierarchy editor and the configured schematic view appears.

2. Edit the configuration using the hierarchy editor and save the file.

3. From the schematic composer window, open the Hierarchy Editor interface bychoosing Tools – Hierarchy Editor.

The hierarchy editor menu appears on the schematic composer menu banner. TheUpdate menu is grayed-out until you update the configuration.

4. Choose Hierarchy Editor – Update.

The hierarchy editor displays the updated configuration.

September 2002 64 Product Version 5.0

Page 65: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

Note: The configuration cellview on the save form in the schematic composer must bechecked 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 configurationcellview on the save form in the schematic composer.

➤ To dismiss this form, click OK, return to the save form and check the configurationcellview.

Your configuration is automatically updated and the hierarchy editor and the schematiccomposer are synchronized.

September 2002 65 Product Version 5.0

Page 66: Hier Editor

Cadence Hierarchy Editor User GuideCreating Configurations

September 2002 66 Product Version 5.0

Page 67: Hier Editor

Cadence Hierarchy Editor User Guide

3Changing Design Components

This chapter covers the following topics:

■ 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

■ Defining Rules at the Global Level on page 72

❑ Defining a View List at the Global Level on page 73

❑ Defining a Library List at the Global Level on page 74

❑ Defining a Stop List at the Global Level on page 75

■ Defining 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

❑ Defining Stop Points on a Per-Cell Basis on page 79

❑ Defining Bind-to-Open on a Per-Cell Basis on page 80

■ Defining 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

❑ Defining Stop Points on a Per-Instance Basis on page 85

September 2002 67 Product Version 5.0

Page 68: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

❑ Defining 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

■ Defining Rules at the Occurrence Level on page 92

❑ About Occurrences on page 92

❑ How Occurrences Are Different from Instances on page 93

❑ Defining Occurrence Bindings on page 95

❑ Defining Occurrence Stop Points on page 102

❑ Defining Occurrence-Level Bind-to-Open on page 103

■ Changing Binding Data Color Definitions 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

Page 69: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Overview

With the hierarchy editor, you can control the expansion of your design for any given purposesuch as simulation or netlisting. You do this by creating and editing rules that define a designconfiguration. You can specify the following configuration rules in the hierarchy editor:

■ 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 theconfiguration. For example, a cell might have different representations such asschematic, Verilog, and VHDL; the view binding determines which of theserepresentations is used in the configuration.

■ Stop Lists and Stop Points: Stop lists and stop points prevent further expansion ofany part of a design.

■ Bind-to-Open: The bind-to-open attribute is a way of specifying that an object in thedesign is unbound, that is, it is not bound to a particular library, cell, and view. Thebindings 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 rulesthat apply to every level of the design. You can also specify rules at the cell, instance, andoccurrence levels.

Global Bindings

Global bindings are configuration rules that are defined at the global level.

At the global level, you can define a library list, view list, and stop list. These global bindingsbecome the default rules for the configuration and apply to every level of the hierarchy, unlessthey are overridden at lower levels of the hierarchy.

For more information about global bindings, see “Defining Rules at the Global Level” onpage 72.

Cell Bindings

Cell bindings are configuration rules that are defined at the cell level. Cell bindings overrideglobal bindings for a cell.

Cell bindings apply to all instantiations of a cell.

You can define the following rules at the cell level:

September 2002 69 Product Version 5.0

Page 70: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

■ View binding that determines which view of the cell is used in the configuration

You can define view bindings for a cell in the following ways:

❑ Binding rules for a specific cell that apply to that cell and to components below it inthe hierarchy, until they are overridden by another binding

❑ Binding for a specific cell that applies only to that cell and is not inherited bycomponents below the cell

■ Library binding that determines the library from which the cell is obtained. This is doneby specifying a library list for the cell. Cell-level library lists are inherited by componentsbelow the cell in the hierarchy.

■ Stop point on the cell that prevents the cell from being expanded.

■ Bind-to-open attribute that specifies that the cell is unbound. You can put a bind-to-openattribute on a cell in a specific library or on just a cell.

For more information about cell bindings, see “Defining Rules at the Cell Level” on page 77.

Instance Bindings

Instance bindings are configuration rules that are defined at the instance level. Instancebindings 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 thatcontains the instance is used in multiple places in the design, the binding applies to theinstance in all those places. If you want to specify a binding for only one instance at a specificpath, you need to specify occurrence bindings instead of instance bindings.

You can define the following rules at the instance level:

■ View binding that determines which view of the cell is used in the configuration

You can define view binding for an instance in the following ways:

❑ Binding rules for a specific instance that apply to that instance and to componentsbelow it in the hierarchy, until they are overridden by another binding

❑ Binding for a specific instance that applies only to that instance and is not inheritedby components below it in the hierarchy

■ Library binding that determines the library from which the instance is obtained. This isdone by specifying a library list for the instance. Instance-level library lists are inheritedby components below the instance in the hierarchy.

September 2002 70 Product Version 5.0

Page 71: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

■ Stop point on the instance that prevents the instance from being expanded.

■ Bind-to-open attribute that specifies that the instance is unbound, that is, it is not boundto a particular library, cell, or view.

For more information about instance bindings, see “Defining Rules at the Instance Level” onpage 82.

Occurrence Bindings

Occurrence bindings are configuration rules that are defined at the occurrence level. Anoccurrence is an instance that is defined by the full path from the top-level design to theinstance. Therefore, occurrence bindings apply to a single object at a specific path in thedesign.

You can specify the following rules at the occurrence level:

■ Library, cell, and view binding for a single object at a specific path in the design

■ Stop point that prevents the occurrence from being expanded

■ Bind-to-open attribute that specifies that the occurrence is unbound, that is, it is notbound to a specific library, cell, or view.

For more information about occurrence bindings, see “Defining Rules at the OccurrenceLevel” on page 92.

Note: Not all Cadence tools support occurrences. Please refer to the documentation for theapplications you are using to check if those applications support occurrences.

How a Library Is Selected for an Object

You can define library binding rules at different levels of a design. The hierarchy editor usesthe following order of precedence (listed from highest precedence to lowest precedence) toselect 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

Page 72: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

You can see which binding rules were used to select the library for an object by reading thedescription in the Explain form in the hierarchy editor. See “Verifying Configuration Data” onpage 50 for more information.

How a View Is Selected for an Object

You can define view binding rules in different ways and at different levels of a design. Thehierarchy editor uses the following order of precedence (listed from highest precedence tolowest 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 thedescription in the Explain form in the hierarchy editor. See “Verifying Configuration Data” onpage 50 for more information.

Defining Rules at the Global Level

You can define rules at the global level that become the default rules for the entireconfiguration. These rules are inherited by every level of the hierarchy until they areoverridden by rules lower in the hierarchy.

You specify global rules, referred to as global bindings, in the Global Bindings section of thehierarchy editor. You can specify these rules in either the table view or the tree view of thehierarchy editor.

You can specify the following rules at the global level:

■ Library List

■ View List

■ Stop List

September 2002 72 Product Version 5.0

Page 73: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Defining a View List at the Global Level

When you define views at the global level, the views apply to every level of the configurationand 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 figure.

The figure shows how the hierarchy editor searches for the first view listed in the View List.For example, in the cell inv1, the symbol, schematic, and verilog views are in thetable. If the hierarchy editor finds a match, it selects that view for the design. If it does not finda match, it continues to look until a match is found. In the example, the second view in theview list, schematic, is the first view that is found.

The View List determines which view is selected for every object in the design, unlessoverridden by a cell binding, instance binding, or occurrence binding.

If the hierarchy editor does not find a view for a cell or instance, it displays **NONE** for thatcell or instance in the View Found column of the Cell or Instance Bindings table.

symbol verilog

symbol

pmos

symbol spectreS

symbol verilog

inv1 inv2

nmos

Inherited View List: spectreS schematic cmos.sch verilog

Top cell

symbol spectreS

pmos

symbol

nmos

Cell contained bytop cell

First view found inView List

Views of inv2

Instances within inv2

First view found in View ListFirst view found in View List

Instances within inv1

spectreSspectreS

schematic schematic

September 2002 73 Product Version 5.0

Page 74: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

**NONE** indicates a binding error that prevents you from netlisting until you correct theerror.

The global view list that you define becomes the default Inherited View List for each cell andinstance. You can override the default at the cell, instance, or occurrence levels. You can alsocheck which binding rules were used to select the view for an object; see “VerifyingConfiguration 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 field.

2. Type the views you want in the order of preference.

Note: You can also define a constant, such as $default, $digital, or $analog, torepresent a view list, and use this constant in inherited view lists. Constants are easierto read than a long view list, and they can be re-used in any view list. See “UsingConstants” 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 configuration resulting from thechange in the View List.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration 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 field.

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.

Defining 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 inthe order in which they are listed and uses the component from the first library in which it isfound.

September 2002 74 Product Version 5.0

Page 75: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Global library lists apply to every level of the configuration. Global library lists can beoverridden by library lists at the cell and instance levels and by specific library.cell:viewbinding on an occurrence. You can see which binding rules were used to select a library fora component; see “Verifying Configuration 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 field.

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 appropriateplace. 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 configuration, from the toolbar, click the Update icon.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration is automatically updated.

5. To save the changes, choose File – Save or press Control-s.

Defining 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 areto be treated as if they do not have any levels of hierarchy below them and cannot beexpanded further. The stop list is optional—the hierarchy editor does not require you to havea stop list in your configuration.

You can use the stop list to designate cellviews that contain no instances. In addition, you canuse the stop list to indicate cases where you do not want the configuration to descend furtherinto the hierarchy.

For example, in flattening for placement, you can use the stop list to indicate a cellview thatis 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 configuration. Views must be listedin the order of preference. For example, if your stop list is

spectreS verilog

September 2002 75 Product Version 5.0

Page 76: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

the hierarchy editor expands the design as shown in the figure below.

To create or change the Stop List,

1. In the Global Bindings section, click in the Stop List field.

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 notrequired because your configuration is automatically updated.

The Cell Bindings section of the hierarchy editor changes to show the new configurationresulting from the change in the Stop List.

5. To save the changes, choose File – Save or press Control-s.

schematicsymbol verilog

symbol spectreS

pmos

symbol spectreS

schematicsymbol verilog

inv1 inv2

nmos

Stop List: spectreS verilog

Top cell

symbol spectreS

pmos

symbol spectreS

nmos

September 2002 76 Product Version 5.0

Page 77: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Defining Rules at the Cell Level

You can define rules at the cell level that override the global rules for an individual cell. Notethat these rules apply to all instantiations of the cell. In addition, some of these rules can alsoapply to the hierarchy below the cell.

You specify cell-level rules, also referred to as cell bindings, in the Cell Bindings section ofthe hierarchy editor. You must specify cell binding rules in the table view of the hierarchyeditor; you cannot specify them in the tree view.

You can specify the following rules at the cell level:

■ Library Binding

■ View Binding

■ Stop Point

■ Bind-to-Open

Changing Library Bindings on a Per-Cell Basis

You can define a cell-level library list that overrides the global library list for an individual cell.The library list determines the library from which the specific cell is obtained. Libraries arelisted in the order of preference. The hierarchy editor searches the libraries in the order inwhich they are listed and uses the cell from the first library in which it is found.

Note that the cell-level library list

■ 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 whosebinding you want to change.

The field becomes editable. If the field does not become editable, the library is fixed foryour design and cannot be changed. CDBA data typically does not allow you to changethe library.

September 2002 77 Product Version 5.0

Page 78: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

3. Edit the inherited library list. The library list that is currently displayed is the global librarylist. Type the libraries you want to use in the order of preference.

4. Press Return.

5. To view the changes in the configuration, click the Update icon.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration 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 cellcontains. If an instance has an instance-level library list, the cell-level list does not apply tothat instance.

Changing View Bindings on a Per-Cell Basis

You can define 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 waythat it is also inherited by the components below the cell in the hierarchy. To make the cellbinding apply only to the cell, you specify the view in the View to Use column. To make thecell binding applicable to components below the cell, you specify a view or view list in theInherited 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 field, type the new view or list of views for the cell and pressReturn.

2. To see the results of your changes, from the toolbar, click the Update icon or from themenu bar, choose View – Update.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration is automatically updated.

The view list you entered is now the view list used for that cell and for any other cellsbelow that cell in the hierarchy (unless they are overridden by other cell or instancebindings 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

Page 79: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

1. From the Cell Bindings table, right-click anywhere in the row of the cell whose bindingsyou 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 forthe cell and press Return.

The new view name(s) appears in the View to Use column in the color used to displayuser bindings.

If you previously selected a binding you no longer want to use, from the Set Cell Viewmenu item, you can select <none> from the cascaded menu list of views to remove theview binding.

4. To see the results of your changes, from the toolbar, click the Update icon. You can alsofrom the menu bar, choose View – Update.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration is automatically updated.

5. To save the changes, from the menu bar, click File – Save or pressControl-s.

Note: This new cell binding is not inheritable.

Defining Stop Points on a Per-Cell Basis

In addition to a global stop list that applies to the entire configuration, you can specify stoppoints on individual cells. A stop point on a cell prevents the cell from being expanded whenthe hierarchy is expanded. Note that a stop point on a cell applies to all the instantiations ofthe 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

Page 80: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

The icon (stop icon) appears in the Info column of the cell row. All the instantiations of thecell will now be considered leaf nodes in the hierarchy; none of them will be expanded whenthe 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 thecell. The stop point applies to all these instantiations.

Defining Bind-to-Open on a Per-Cell Basis

You can specify that a cell is unbound, that is, it is not bound to a specific library or view, bysetting a bind-to-open attribute on it. The bindings for the cell can be set later by other toolsthat use the configuration.

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:

■ Bind-to-open on a cell

■ Bind-to-open on a cell in a specific library

The hierarchy editor displays the string **UNBOUND** to indicate that a cell has a bind-to-open attribute. **UNBOUND** is not an error, unlike **NONE* . **UNBOUND** indicates thatthe cell is deliberately unbound while **NONE** indicates that the binding for the cell couldnot 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-to-open attribute.

3. From the pop-up menu, select Add Bind To Open.

September 2002 80 Product Version 5.0

Page 81: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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, selectAdd Bind To Open on Cell "cellname".

❑ If you want the cell to be unbound when it is obtained from a specific library, selectAdd 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 theCell Bindings section display **UNBOUND**. If you selected Add Bind to Open onLibrary "libraryname", Cell "cellname", only the View Found and View to Usecolumns display **UNBOUND**. For example:

Also, the instances contained in the cell are no longer displayed in the Instance Bindingssection 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 thecell. The bind-to-open attribute applies to all these instantiations.

September 2002 81 Product Version 5.0

Page 82: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Defining Rules at the Instance Level

You can define rules at the instance level that override global rules and cell rules. Instancerules apply to only one instantiation of a cell, unlike cell-level rules that apply to all theinstantiations of a cell. Note, however, that if the cell that contains the instance is used inmultiple 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 InstanceBindings section of the hierarchy editor. You can specify instance binding rules in the tableview or the tree view of the hierarchy editor.

You can specify the following rules at the instance level:

■ 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 viewbinding apply to only the instance you specify (effective no lower in the hierarchy) or you canchange it in a way that it is also inherited by the components below the instance in thehierarchy.

To make the binding apply only to the instance, you specify the view in the View to Usecolumn. To make the binding applicable to components below the instance, you specify a viewor 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

Page 83: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 userbindings.

If you previously selected a binding you no longer want to use, from the Set InstanceView menu item, you can select <none> from the cascaded menu list of views to removethe view binding.

5. To see the results of your changes, from the toolbar, click the Update icon.

September 2002 83 Product Version 5.0

Page 84: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration is automatically updated.

6. To save the changes, from the menu bar, click File – Save or pressControl-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 thehierarchy,

1. Click in the Inherited View List field and type a new view or list of views for the instanceand 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 notrequired because your configuration is automatically updated.

3. To save the changes, from the menu bar, click File – Save or pressControl-s.

You may also create a symbolic name, to represent a view list. Refer to “Using Constants” onpage 110 if you want to represent multiple views by one name.

Changing Library Bindings on a Per-Instance Basis

You can define an instance-level library list that overrides the global and cell library lists for asingle instantiation of a cell. The library list determines the library from which the instance isobtained. Libraries are listed in the order of preference—if the instance is found in the firstlibrary 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

■ Applies to only one instantiation of a cell

■ Can apply to multiple objects—if the cell that contains the instance is used in multipleplaces 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

Page 85: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 instancewhose binding you want to change.

The field becomes editable. If the field does not become editable, the library is fixed foryour design and cannot be changed. CDBA data typically does not allow you to changethe library.

4. Edit the inherited library list. The library list that is currently displayed is the library listinherited from higher levels of the hierarchy. Type the libraries in the order of preference.

5. Press Return.

6. To view the changes in the configuration, click the Update icon.

If you selected the Automatic Update option in the Options form, this step is notrequired because your configuration is automatically updated.

7. To save the changes, choose File – Save or press Control-s.

Defining Stop Points on a Per-Instance Basis

You can specify a stop point on a single instantiation of a cell that prevents the instance frombeing expanded when the hierarchy is expanded. Note that a stop point on an instance canapply to multiple objects—if the cell that contains the instance is used in multiple places in thedesign, the stop point applies to the instance in all those places. For example, if you put a stoppoint on instance I2 of cell OpAmp and cell OpAmp is used in three places in the design, thestop 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 thehierarchy editor.

To add a stop point to an instance from the tree view,

1. Choose View – Tree to display the tree view of the configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the instance on which you want to add a stoppoint.

3. From the pop-up menu, select Add Stop Point.

September 2002 85 Product Version 5.0

Page 86: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

The Set Stop Point dialog box appears.

Note: If the instance has already been identified as an occurrence and has the icon(occurrence icon), when you select Add Stop Point, the Set Stop Point dialog box doesnot appear. Instead, the stop point is added to the occurrence. For more informationabout occurrence stop points, see “Defining Occurrence Stop Points” on page 102.

4. In the Set Stop Point dialog box, select Add Stop Point on Instance "instance", whereinstance is the instance you selected.

5. Click OK.

The stop icon appears in the Info column of the instance row. The instance cannot beexpanded.

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 thehierarchy editor, if it is not already displayed.

2. In the Cell Bindings section, select the cell that contains the instance to which you wantto 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 astop 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 instancecan no longer be expanded.

If the cellview that contains the instance is used in multiple places in the design, the stop pointwill apply to the instance in all those places.

September 2002 86 Product Version 5.0

Page 87: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 youadded the stop point.

2. From the pop-up menu, select Explain.

The Explain dialog box appears. The Instantiations section lists the instantiations of thecell. 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 defined asan occurrence (identified by a icon). When you add a stop point to such an object, it isadded to the occurrence, not the instance, and applies only to one object at a specific path.For information about occurrence stop points, see “Defining Occurrence Stop Points” onpage 102.

Defining Bind-to-Open on a Per-Instance Basis

You can specify that a single instantiation of a cell is unbound—that is, it is not bound to aspecific library, cell, and view—by setting a bind-to-open attribute on it. The bindings for theinstance can be set later by other tools that use the configuration.

Note that a bind-to-open attribute on an instance can apply to multiple objects—if the cell thatcontains the instance is used in multiple places in the design, the bind-to-open applies to theinstance in all those places. For example, if you specify that instance I2 in cell OpAmp isunbound and cell OpAmp is used in three places in the design, I2 will be unbound in all threeinstantiations of OpAmp.

The hierarchy editor displays the string **UNBOUND** to indicate that an instance has a bind-to-open attribute. **UNBOUND** is not an error, unlike **NONE**. **UNBOUND** indicatesthat the instance is deliberately unbound while **NONE** indicates that the binding for theinstance 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 viewof 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 configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the instance on which you want to add a bind-to-open.

3. From the pop-up menu, select Add Bind To Open.

September 2002 87 Product Version 5.0

Page 88: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 identified as an occurrence and has the icon(occurrence icon), the Add Bind To Open on Instance “instance” option will begreyed 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 “Defining Occurrence-Level Bind-to-Open” on page 103.

5. Click OK.

The instance is now unbound. The library, cell, and view name of the instance arereplaced 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 theconfiguration, if it is not already displayed.

2. In the Cell Bindings section, select the cell that contains the instance to which you wantto 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 abind-to-open.

4. From the pop-up menu, select Add Bind To Open.

September 2002 88 Product Version 5.0

Page 89: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

The instance is now unbound. The Library, Cell, View Found, and View to Usecolumns display **UNBOUND**. For example:

If the cellview that contains the instance is used in multiple places in the design, the bind-to-open 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 whichyou 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 thecell. The bind-to-open will apply to the instance in all these instantiations of the cell. Ifany of the instances has an occurrence binding on it already, the bind-to-open will notapply to it.

Changing Instance Bindings Inside a Block

A block is a group of instances used in simulators like VHDL. Blocks can contain other blocksand other instances. You can bind instances inside a block the same way you can bindinstances 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

Page 90: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

3. Click the expand button to display the instances within the selected block.

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 pressReturn.

The new view name(s) appears in the View to Use column in the color used to displayuser bindings.

If you select a binding you no longer want to use, from the Set Instance View menuitem, you can select <none> from the cascaded menu list of views to remove the viewbinding.

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 notrequired because your configuration is automatically updated.

8. To save the changes, from the menu bar, click File – Save or press Control-s.

Block name

Generate statement

Instance

Expanded block

September 2002 90 Product Version 5.0

Page 91: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Changing Instance Bindings Created by a Generate Statement

VHDL users can bind instances created by generate statements. You can collectively bind allthe 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.

■ 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 youcan 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 generatestatement.

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 pressReturn.

The new view name(s) appears in the View to Use column in the color used to displayuser bindings.

If you select a binding you no longer want to use, from the Set Instance View menuitem, you can select <none> from the cascaded menu list of views to remove the viewbinding.

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 notrequired because your configuration is automatically updated.

September 2002 91 Product Version 5.0

Page 92: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

6. To save the changes, from the menu bar, click File – Save or pressControl-s.

Defining Rules at the Occurrence Level

About Occurrences

An occurrence is an instance that is uniquely identified by its full path from the top-level designto the instance. Occurrences provide the ability to uniquely identify an object in the designand 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:

■ Occurrence binding, that is, library, cell, and view binding

■ Occurrence stop point

■ Occurrence-level bind-to-open

Setting any of the above attributes identifies the object as an occurrence.

Note: Not all Cadence tools support occurrences. Before you use the occurrence feature ofthe hierarchy editor, please refer to the documentation for the applications you are using tocheck if those applications support occurrences.

In the hierarchy editor, occurrences are represented by the following icons:

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 colorconventions.

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

September 2002 92 Product Version 5.0

Page 93: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

How Occurrences Are Different from Instances

Occurrences are unique, while instances are not. When you put an attribute (such as a stoppoint) on an instance, it can apply to more than one object because instances cannot beidentified uniquely. An instance is identified by the cell it is contained in. If the cell is used inmultiple places in the design, the instance is in multiple places in the design.

An occurrence, on the other hand, is identified uniquely by its full path from the top-leveldesign. When you put an attribute (such as a stop point) on an occurrence, it only applies tothat single object.

The following example illustrates the difference between instances and occurrences. BothFigure 1 and Figure 2 display the design mixSigLib.tutorial:schematic. In thisdesign, the cell OpAmp is used twice—its instantiations aremixSigLib.tutorial:schematic.I0.I0.I144 andmixSigLib.tutorial:schematic.I0.I0.I145. The cell OpAmp contains severalinstances, including Q60.

In Figure 1, an instance stop point is specified on Q60 in I144. Notice that Q60 in I145 (theother instantiation of cell OpAmp) automatically gets the stop point, too.

September 2002 93 Product Version 5.0

Page 94: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Figure 1: Example of an Instance-Level Stop Point

In Figure 2, an occurrence stop point is specified 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 thestop point was put on the occurrence and not on the instance.

Stop Pointplaced oninstance Q60

September 2002 94 Product Version 5.0

Page 95: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Figure 2: Example of an Occurrence Stop Point

Defining Occurrence Bindings

You create an occurrence binding by specifying a library, cell, and view for a single object ata specific path in the design. Unlike cell or instance binding, occurrence binding applies onlyto one object.

When you do an occurrence binding, none of the other binding rules—such as inheritedlibrary lists or view lists—apply to that occurrence.

You can create an occurrence binding only in the tree view of the hierarchy editor; you cannotcreate it in the table view.

Note: If the library or cell is fixed by some other rules in the design data, you will not be ableto change that binding. For example, design data in DFII typically does not allow you tochange the library.

Stop pointplaced onoccurrence Q60

September 2002 95 Product Version 5.0

Page 96: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Creating an Occurrence Binding

To specify a binding for an occurrence,

1. Choose View – Tree to display the tree view of the configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the instance to which you want to add anoccurrence 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 oneof 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 filters to limit the data displayed in the Browse section. Click Filters todisplay the Browser Filters form.

❑ If you want the occurrence to be unbound so that its binding can be set later byanother tool, select Enable Bind To Open.

The Library, Cell, and View fields display **UNBOUND**. These fields are greyed-out and are not editable when Enable Bind To Open is selected.

September 2002 96 Product Version 5.0

Page 97: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

(For more information about the Bind To Open option, see “Defining Occurrence-Level Bind-to-Open” on page 103)

Note: If the library or cell is fixed by some other rules in the design data, you will not beable to edit the corresponding fields 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 identified as an occurrence and a library.cell:view binding is set on it. Theleaf 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 replacedby 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 configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the occurrence whose binding you want tochange.

3. If you want to change only the view, from the pop-up menu, select Set OccurrenceView and then select the new view from the list of views. Skip the remaining steps in thissection.

4. If you want to change the library or cell, from the pop-up menu, select Edit OccurrenceBinding.

September 2002 97 Product Version 5.0

Page 98: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 thefollowing:

❑ Edit the Library, Cell, and View fields in the Occurrence Binding section or selectthe library, cell, and view from the Browse section.

You can use filters to limit the data displayed in the Browse section. Click Filters todisplay the Browser Filters form.

❑ If you want the occurrence to be unbound so that its binding can be set later byanother tool, select Enable Bind To Open.

The Library, Cell, and View fields display **UNBOUND**. These fields are greyed-out and are not editable when Enable Bind To Open is selected.

(For more information about the Bind To Open option, see “Defining Occurrence-Level Bind-to-Open” on page 103)

Note: If the library or cell is fixed by some other rules in the design data, you will not beable to edit the corresponding fields 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

Page 99: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Removing an Occurrence Binding

To remove an occurrence binding,

1. Choose View – Tree to display the tree view of the configuration, if it is not alreadydisplayed.

The hierarchy editor displays the tree view of the configuration.

2. In the Tree View section, right-click on the occurrence whose binding you want toremove.

3. From the pop-up menu, select Remove Occurrence Binding.

The occurrence binding is removed from the object. The icon (occurrence icon) isreplaced by the leaf or folder icon. The object is no longer uniquely identified, unless it alsohas 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.

September 2002 99 Product Version 5.0

Page 100: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 fields if

❑ The library or cell is fixed 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 specifies that the library, cell, and view areunbound.

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 textfields in the Occurrence Binding section.

Enable Bind To Open lets you specify that the occurrence is unbound, that is, it is not boundto a particular library, cell, or view. The binding for the occurrence can be set later by anothertool that uses the configuration. If Enable Bind To Open is selected, the Library, Cell, andView fields 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 onlypart of the library structure in the Browse section.

Help opens this manual.

September 2002 100 Product Version 5.0

Page 101: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 fields if

❑ The library or cell is fixed 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 specifies that the library, cell, and view areunbound.

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 textfields in the Occurrence Binding section.

Enable Bind To Open lets you specify that the occurrence is unbound, that is, it is not boundto a particular library, cell, or view. The binding for the occurrence can be set later by anothertool that uses the configuration. If Enable Bind To Open is selected, the Library, Cell, andView fields cannot be edited.

September 2002 101 Product Version 5.0

Page 102: Hier Editor

Cadence Hierarchy Editor User GuideChanging 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 onlypart of the library structure in the Browse section.

Help opens this manual.

Defining Occurrence Stop Points

An occurrence stop point is a stop point on a specific path and applies only to one object inthe design.

If an object has already been defined as an occurrence (an object is defined as an occurrenceif 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 tothe occurrence, not to the instance.

You can only add an occurrence stop point in the tree view of the hierarchy editor; you cannotadd 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 configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the instance on which you want to add a stoppoint.

3. From the pop-up menu, select Add Stop Point.

September 2002 102 Product Version 5.0

Page 103: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

The Set Stop Point dialog box appears.

Note: If the instance has already been identified as an occurrence and has the icon,when you select Add Stop Point, the Set Stop Point dialog box does not appear. Thestop point is added to the occurrence and the icon (occurrence binding and stoppoint icon) appears next to the occurrence.

4. In the Set Stop Point dialog box, select Add Stop Point on Path "path", where path isthe 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 occurrencecannot 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 configuration, if it is not alreadydisplayed.

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 identified, unless it also has an occurrence binding.

Defining Occurrence-Level Bind-to-Open

You can specify that an occurrence is unbound—that is, it is not bound to a specific library,cell, and view—by setting a bind-to-open attribute on it. The bindings for the occurrence canbe set later by other tools that use the configuration.

September 2002 103 Product Version 5.0

Page 104: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

The hierarchy editor displays the string **UNBOUND** to indicate that an occurrence has abind-to-open attribute. **UNBOUND** is not an error, unlike **NONE**. **UNBOUND**indicates that the occurrence is deliberately unbound while **NONE** indicates that thebinding 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 hierarchyeditor; 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 configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the instance on which you want to add anoccurrence-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", wherepath 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) appearsnext to the occurrence and the library, cell, and view names are replaced by **UNBOUND**.For example:

September 2002 104 Product Version 5.0

Page 105: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Note: You can also specify a bind-to-open attribute from the Add Occurrence Binding andEdit 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 configuration, if it is not alreadydisplayed.

2. In the Tree View section, right-click on the occurrence from which you want to removethe 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 basedon the other binding rules and displayed.

Changing Binding Data Color Definitions

The hierarchy editor displays color-coded cell and instance binding data. The following tablelists the default colors:

Note: As you type new binding information into the Cell Bindings or Instance Bindings table,the user-defined binding color is used.

You can change the default colors by adding variables to a local hierEditor.env file.

To change the default colors,

1. If you do not have a hierEditor.env file, create a file named hierEditor.env in adirectory that is in your setup.loc file (for example, your $HOME directory or current

Color Definition

Black Default binding

Blue User-defined binding

Red Error

Orange Not in Use

September 2002 105 Product Version 5.0

Page 106: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

working directory). You can create the file with a text editor or with the File – SaveDefaults command.

Note: If you have multiple hierEditor.env files, the hierarchy editor determineswhich value to use based on the search order defined in the setup.loc file.

2. Add the following variables to the hierEditor.env file:

hierEditor.display.colorChooser bindingError string “newColor” nilhierEditor.display.colorChooser userBinding string “newColor” nilhierEditor.display.colorChooser defaultBinding string “newColor” nilhierEditor.display.colorChooser notInUse string “newColor” nil

For example, if you want to change the default binding color to green, add the followingvariable:

hierEditor.display.colorChooser defaultBinding string “green” nil

Note: Add only those variables that you want to change from the default. You do notneed to add variables that you are not changing.

3. Save the hierEditor.env file.

Your changes are displayed the next time you start the hierarchy editor.

For more information about the hierEditor.env file, see Appendix A, “The hierEditor.envFile.”

Using Constants

A constant is a symbolic name that represents a view list. Constants provide a way to storeand retrieve long view lists. You can create a constant and use it anywhere you use a ViewList and a Stop List.

Creating Constants

To create a constant,

1. Choose Edit – Constants.

September 2002 106 Product Version 5.0

Page 107: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

The Edit Constants form appears.

2. Add views to the Value field by doing one of the following:

❑ In the View Choices list box, select the view that you want to include in the newconstant, then click Insert.

❑ In the View Choices list box, double-click the view that you want to include in thenew constant.

Note: If a view that you want to include in the constant is not available in the ViewChoices list, you can type the name of the view in the Value field. You can also changethe default list of views in the View Choices list box. See “Changing the Views in theView Choices List Box” on page 110 for more information.

3. In the Constant field, type the name you want to use to represent the list of views youadded to the Value field.

4. Click Set.

Note: The Set button is greyed-out if you have not assigned a constant name to theselected views.

The hierarchy editor creates the constant.The constant and its value appear in the tableat the top of the form.

September 2002 107 Product Version 5.0

Page 108: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Note: The view names must appear in the Value field in the order in which you want thehierarchy editor to use them. Either insert or type them into the Value field in that order orhighlight a view in the View Choices list box and use the Remove and Insert buttons torearrange 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 field and its views are displayed in theValue field.

3. To add a view,

a. In the Value field, place the cursor where you want to add the new view.

Note that the order of views is important—the hierarchy editor uses the views in theorder 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 field, double-click the view.

b. Press the Delete key.

5. When you have finished editing the Value field, click Set.

Note: The Set button is greyed-out if the Constant field is empty.

September 2002 108 Product Version 5.0

Page 109: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

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 themfrom the View Choices list box.

View Choices contains the list of views from which you select views for the constant. Youcan 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

Page 110: Hier Editor

Cadence Hierarchy Editor User GuideChanging Design Components

Changing the Views in the View Choices List Box

The default list of views in the View Choices list box is defined by thehierEditor.constants variable in the your_install_dir/share/cdssetup/hierEditor/env/hierEditorReg.env file. You cannot edit this registration file but youcan change the list of views by adding the variable to a local hierEditor.env file.

To change the views in the View Choices list box,

1. If you do not have a hierEditor.env file, create a file named hierEditor.env in adirectory that is in your setup.loc file (for example, your $HOME directory or currentworking directory).

Note: If you have multiple hierEditor.env files, the hierarchy editor determineswhich value to use based on the search order defined in the setup.loc file.

2. Add the following variable to the hierEditor.env file:

hierEditor.constants viewChoices string "view1 view2 view3 view4 ..."

where view1, view2, view3, and view4 are the views that you want the ViewChoices list box to display. For example:

hierEditor.constants viewChoices string "abstract ahdl behavioral cdsSpicecmos_sch functional schematic spectre spectreS symbol"

For more information about the hierEditor.env file, see Appendix A, “The hierEditor.envFile.”

Using Constants

To use a constant,

➤ Type the name of the constant, preceded by a dollar sign ($), in any view list or stop listfield.

By default, the hierarchy editor displays the constant in the view lists or stop lists in which itis used. However, you can choose to display the expanded form of the constant (the list ofviews 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 file:

hierEditor.display showConstInViewList boolean nil

For more information about the hierEditor.env file, see Appendix A, “The hierEditor.envFile.”

September 2002 110 Product Version 5.0

Page 111: Hier Editor

Cadence Hierarchy Editor User Guide

4Using Plug-Ins

This chapter covers the following topics:

■ 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

Page 112: Hier Editor

Cadence Hierarchy Editor User GuideUsing Plug-Ins

About Plug-Ins

Plug-ins are applications that are added to the hierarchy editor and that are used from thehierarchy editor user interface. Some Cadence products are added to the hierarchy editor asplug-ins.

The Plug-Ins Menu

If at least one plug-in is added to the hierarchy editor, the hierarchy editor menu bar displaysthe Plug-Ins menu. If the Plug-Ins menu is not present, no plug-ins have been added to thehierarchy editor.

Plug-Ins Menu

September 2002 112 Product Version 5.0

Page 113: Hier Editor

Cadence Hierarchy Editor User GuideUsing Plug-Ins

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 first load it. The hierarchy editor does notload the plug-ins by default.

When you load a plug-in application, it appears in the hierarchy editor, typically as a menu onthe menu bar or an icon on the tool bar. You can load a plug-in either from the command linewhen 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 youcan 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 tothe 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 specified by the plug-in. For instance,a plug-in could appear as an additional menu in the hierarchy editor menu bar or an iconin the hierarchy editor tool bar.

Also, in the Plug-Ins menu, the plug-in check box is now selected, which indicates thatthe plug-in is loaded.

September 2002 113 Product Version 5.0

Page 114: Hier Editor

Cadence Hierarchy Editor User GuideUsing Plug-Ins

For example, if you choose Plug-Ins – AMS, the AMS menu appears in the menu bar.

3. (Optional) If you want the hierarchy editor to automatically load the plug-in applicationevery time it starts, save the hierarchy editor defaults with the File – Save Defaultscommand.

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 specified with the cdsHierEditorcommand. It can be followed only by other -plugin arguments.

When the hierarchy editor starts, the plug-in application appears in the hierarchy editorgraphical 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 applicationevery time it starts, save the hierarchy editor defaults with the File – Save Defaultscommand.

AMS Menu

September 2002 114 Product Version 5.0

Page 115: Hier Editor

Cadence Hierarchy Editor User GuideUsing Plug-Ins

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 thePlug-Ins menu, the plug-in check box is no longer selected, which indicates that theplug-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

Page 116: Hier Editor

Cadence Hierarchy Editor User GuideUsing Plug-Ins

September 2002 116 Product Version 5.0

Page 117: Hier Editor

Cadence Hierarchy Editor User Guide

AThe hierEditor.env File

The default display and form settings of the hierarchy editor are defined by variables that areregistered in the your_install_dir/share/cdssetup/hierEditor/env/hierEditorReg.env file. You cannot edit the hierEditorReg.env file but you canchange the settings by creating a local environment file named hierEditor.env.

The local hierEditor.env file is typically created with the File – Save Defaults commandand must be in a directory that is listed in your setup.loc file (for example, your homedirectory or current working directory). The hierEditor.env file contains only thosesettings that are different from the hierEditorReg.env file.

The hierEditor.env file is read by the hierarchy editor when it is started. If you havemultiple hierEditor.env files, the hierarchy editor determines which value to use for eachvariable based on the search order defined in the setup.loc file. For more informationabout the setup.loc file, see Chapter 3, “Cadence Setup Search File: setup.loc,” of theCadence Application Infrastructure User Guide.

Some of the form and display settings, typically the general user interface settings, are savedwhen you use the File – Save Defaults command. For example, the options that you selectin the Options form or in the View Filters form are saved to the hierEditor.env file whenyou use the File – Save Defaults command. Other settings, such as the list of views in theEdit Constants form, can only be changed by editing the hierEditor.env file manually.

If you want to set any of the following variables, you must add them to your localhierEditor.env file manually:

■ hierEditor.compatibility uselibSelect boolean nil

useLibSelect specifies that the libSelect application is used to browse a library toopen a configuration. It is used for compatibility with DFII applications.

■ hierEditor.constants viewChoices string "view1 view2 view3 ..."

viewChoices defines the list of views in the View Choices list box in the EditConstants form.

■ hierEditor.display.colorChooser bindingError string "red"

September 2002 117 Product Version 5.0

Page 118: Hier Editor

Cadence Hierarchy Editor User GuideThe hierEditor.env File

bindingError defines the color used to display text when there is a binding error.

■ hierEditor.display.colorChooser userBinding string "blue"

userBinding defines the color used to indicate the bindings that users have changed.

■ hierEditor.display.colorChooser defaultBinding string "black"

defaultBinding defines the color used to indicate that this is the default binding.

■ hierEditor.display.colorChooser notInUse string "darkOrange2"

notInUse defines the color used to indicate objects that are not in use.

■ hierEditor.display.colorChooser highlight string "khaki1"

highlight defines the color used to indicate an object that an external applicationwants to find. For example, Virtuoso schematic composer users can add an instanceprobe and see it in the hierarchy editor.

■ hierEditor.display.colorChooser rowSelection string "#ccccff"

rowSelection defines the color used to indicate a row selection in the table and thetree.

Specify colors as hex rgb values in the format "#rrggbb" where rr is a two digit hexnumber for red, gg is a two digit hex number for green, and bb is a two digit hex numberfor blue.

■ hierEditor.display showConstInViewList boolean nil

showConstInViewList, when set to nil, specifies that instead of displaying aconstant, the hierarchy editor should display the expanded view list that the constantrepresents. The default value of this variable is t.

■ hierEditor.options.update autoGenPcdbFiles boolean t

autoGenPcdbFiles, when set to t, specifies that the hierarchy editor shouldautomatically generate a pc.db file from Verilog or VHDL.

■ hierEditor.options.update useNCCompilers boolean t

useNCCompilers is used in conjunction with the autoGenPcdbFiles variable. Whenset to t, useNCCompilers specifies that the NC compilers (NC-Verilog and NC-VHDL)be used when generating a pc.db file from Verilog or VHDL.

September 2002 118 Product Version 5.0