Difference between revisions of "Tutorials:Cadence:DesignHierarchy"
From EDA Wiki
Jump to navigationJump to search (Created page with "= Design Hierarchy = A hierarchical design is formed by placing copies or instances of cell inside of other cells. The cell at the top includes the whole design (say, a symbol...") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Design Hierarchy = | = Design Hierarchy = | ||
| − | A hierarchical design is formed by placing copies or | + | <!--A hierarchical design is formed by placing copies or instances of cell inside of other cells. The cell at the top includes the whole design (say, a symbol of an inverter) and the cell at the bottom is the layout (the way things are laid out on the silicon). The top cell is given level number zero, while the bottom cell is given the highest level number.--> |
| − | + | ;Library | |
| + | : Libraries let you organize design data and perform version access and control. A library is a collection of logical design objects, organized in levels as shown: | ||
| − | + | ;Cell | |
| + | : A cell is the basic design object. It forms an individual building block of a chip or system. It is a logical, rather than physical, design object. Each cell has one or more cell views as shown above. Cells can be logically grouped into cell categories. A cell can belong to several cell categories. | ||
| − | + | ;Cell view | |
| + | : A cell view is a virtual data file created in association with a cell and a view. It is a logical, rather than physical, design object. | ||
| − | + | <!--Note: This hierarchical list may seem confusing, but if you go back to the Library Browser, you will notice that each one correlates to a different level in the libraries. The organization described above can be seen bellow.--> | |
| − | '' | + | The Cadence software manages these files transparently. However, because of the relationship between cells, you must use the commands ''copy'', ''move'', and ''delete'' within the Cadence software in order to manipulate the different cells. UNIX operating system commands cannot correctly handle these files. |
| + | <noinclude> | ||
| − | + | [[Tutorials:Cadence:UsingLibraryManager|Prev]] : [[Tutorials:Cadence:QuittingCadence|Next]] : [[Tutorials:Cadence:Main|Up]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
---- | ---- | ||
{{CadenceDisclaimer}} | {{CadenceDisclaimer}} | ||
| + | </noinclude> | ||
Latest revision as of 02:05, 12 November 2010
Design Hierarchy
- Library
- Libraries let you organize design data and perform version access and control. A library is a collection of logical design objects, organized in levels as shown:
- Cell
- A cell is the basic design object. It forms an individual building block of a chip or system. It is a logical, rather than physical, design object. Each cell has one or more cell views as shown above. Cells can be logically grouped into cell categories. A cell can belong to several cell categories.
- Cell view
- A cell view is a virtual data file created in association with a cell and a view. It is a logical, rather than physical, design object.
The Cadence software manages these files transparently. However, because of the relationship between cells, you must use the commands copy, move, and delete within the Cadence software in order to manipulate the different cells. UNIX operating system commands cannot correctly handle these files.
Information is provided "as is" without warranty or guarantee of any kind. No statement is made and no attempt has been made to examine the information, either with respect to operability, origin, authorship, or otherwise.
Please use this information at your own risk--and any attempt to use this information is at your own risk--we recommend using it on a copy of your data to be sure you understand what it does and under what conditions. Keep your master intact until you are personally satisfied with the use of this information within your environment."
Cadence® is a trademark of Cadence Design Systems, Inc., 555 River Oaks Parkway, San Jose, CA 95134
For web related questions contact: Viktor Gruev, Michael Hall
