If a cellview contains an object for example, a net or a pin with an illegal name, the translator translates the cellview but not the illegally-named object. March 25 Product Version 6. The translator does not convert directories contained in cellviews. If your library has directories in cellviews and if those directories contain data that needs to be translated, move the directory and its contents up to the cell level in the hierarchy before running the translator.
Identifying the Master Cellview For certain operations, such as launching an editor on cellview data, Cadence software needs to be able to identify the master file in any cellview. The master. The Parent-Child Database File: pc. Otherwise it is skipped. The oa2cdb translator behaves similarly: It copies a pc. Otherwise the file is skipped with a message. If the pc. They are set to unknown by oa2cdb. March 26 Product Version 6.
March 27 Product Version 6. If the values are different, then the connectivity data is out of date and needs to be re-extracted. If lastSchematicExtraction is later than instancesLastChanged, the connectivity data is current; otherwise, it is not current.
The translator checks whether the connectivity data is current in OpenAccess. CDB applications comparing the values of the two properties find that the connectivity is current. CDB applications are able to determine that connectivity needs to be re-extracted for the cellview.
The translator uses a similar policy to establish the status of cellview geometry. In this case, the schGeometryLastUpdated property is compared with the cellview counter value to determine if the geometry of the cellview is up to date in OpenAccess. March 28 Product Version 6. CDB applications comparing the values of the two properties find that the geometry was updated after the instance was last modified, therefore the geometry is current.
CDB applications are able to determine that geometry needs to be updated for the cellview. In CDB, whenever a cellview is opened, the application retrieves the value of instancesLastChanged from the master cellview during instance binding and compares it with the value of the instancesLastChanged property of the cellview. If the value from the master is later than the value from the cellview, it means that the master has been edited since the cellview was last saved.
In OpenAccess, when saving the cellview, the cellview counter from the master is stored as an integer property under the name masterChangeCount in the instance header of the parent cellview that contains the instance. When the cellview is reopened, the cellview counter from the master is compared with the masterChangeCount counter from the instance header. If the values are different, then the instance and its master are out of synch.
If it is not, the translator sets it to that value. The next time an application compares the values, it detects that the instances were changed after their master and therefore that the instances and masters are in synch.
CDB applications will determine that all instances are out of synch with their master. March 29 Product Version 6. When translating paths with extensions, if the path style is not variable, the translator sets beginExt and endExt to 0. Labels There are three types of label objects in CDB. A normal label is equivalent to an oaText object in OpenAccess. An IL or NLP label is equivalent to an oaEvalText object, each one associated to a specific text callback object that contains the code to evaluate the text string before displaying it.
When converting an oaText object, there is a direct mapping for all OpenAccess attributes except alignment, which is mapped to the justify attribute in CDB. Visibility Settings for Text Display Objects Text display objects are used to display the value of a property or attribute for an object. Like all other design components, they can be assigned visibility attributes that specify whether or not they are displayed when the cellview is viewed in a display device.
March 30 Product Version 6. The translator maps the OpenAccess settings as indicated in the table below. The difference is caused not by the translator but because of a difference in how OpenAccess and CDB calculate bounding boxes: OpenAccess rounds the values to the nearest database unit, whereas CDB truncates the values.
Consequently, the width and height of a particular label could differ by up to 1 OpenAccess database unit between OpenAccess and CDB versions. If the label or text display is at the edge of a cellview, the difference described above can cause the bounding box of the cellview and any instances of that cellview to be different in OpenAccess and CDB.
Parameterized Cellviews A parameterized cell, or pcell, is a graphic, programmable cell that lets you create a customized instance each time you place it. Pcells are created in the same way as any other cell and combine the graphic layout of the cell and the parameters assigned to it. March 31 Product Version 6. The translator converts the pcell master cellview as a regular cellview. It then retrieves the parameter values from the OpenAccess master parameters and the SKILL code attached to the master, and uses this information to transform the CDB regular cellview into a parameterized master cellview.
If your pcells deviate from the recommendations and, for example, include SKILL functions that are not intended for use in pcells, the translator fails. To reproduce magnified instances in OpenAccess, the cdb2oa translator creates special parameterized cellviews containing flattened instances of the original cellview master with an additional mag parameter, used to magnify instances of that master when required.
When the oa2cdb translator encounters a pcell master with the mag and rotation parameters, it converts it to a regular CDB cellview. Instances of such masters are translated as regular magnified instances. Design Database Files The properties, groups, or extensions associated with a library, cell, or view are stored in OpenAccess design database dd. The translator converts dd.
Note: OpenAccess dd. OpenAccess groups and extensions defined in dd. March 32 Product Version 6. The cdb2oa translator converts this property to a string property in OpenAccess and oa2cdb converts it back into a string property in CDB.
Nets and Signals When converting nets, the translator sets the sigType and global attributes on all signals associated with a CDB net. They are mapped to unknown in CDB. The following attributes are skipped because they have no equivalent in CDB: original, routePattern, routeSpec, shieldNet1, shieldNet2, source, and voltage. Terminals When converting terminals, the translator converts all the OpenAccess termType values to their CDB equivalents except tristate, which is set to unknown and a warning issued to the log file.
Additionally, in CDB a net can be associated with at most one terminal, while OpenAccess supports multiple terminals on each net. If the translator finds a terminal with the same net in CDB, the terminal currently being translated is skipped with an error.
Pins oa2cdb is able to convert only pins that are represented either by a shape or an instance object. OpenAccess pins that are represented by routes are skipped with an error. March 33 Product Version 6. The translator sets these to unknown. Mosaics A mosaic is a database object in CDB that represents an array of instances of one or more masters. There are two kinds of mosaics: simple and complex.
A simple mosaic is a special kind of regular array that has only one master, and every cell in the array has the same orientation. Any mosaic other than the simple mosaic is called a complex mosaic. Complex mosaics are not supported in OpenAccess so cdb2oa breaks up complex mosaics into the individual instances that make up the mosaic before conversion. If the OpenAccess regular arrayed instance has instance terminals, it is converted into several CDB scalar instances.
Instance Pins An instance pin instPin is a database object that represents a pin of a terminal in the master of an instance. Because they are not used in DFII applications, cdb2oa does not create any instance pins in the OpenAccess version of the cellview.
Similarly, oa2cdb does not support the conversion of instance pins to CDB. March 34 Product Version 6. This section lists the arguments and switches you can use with the oa2cdb UNIX command and describes how to use these to accomplish the most common translation tasks. The oa2cdb executable is available at the following location. Getting Help To get help on the translator syntax and usage, type the following command in a shell window.
The software displays the same information if you enter oa2cdb without specifying any arguments. March 35 Product Version 6. Specify the name in the CDBA name space. This will also be the name of the CDB version of the library. You cannot use the translator to rename a library. If you need your library to have a different name in CDB, rename the OpenAccess version before translating it. The translator accepts any file that uses standard Cadence cds.
You can enter either a relative path or an absolute path. The parent directory of the directory you specify must exist on your system; the translator cannot create it automatically. The last element of the path is the library directory into which the library cells and other files are to be translated. The translator creates this directory automatically.
If the library is already defined in the CDB cds. Note: The translator always creates or updates the CDB cds. March 36 Product Version 6. Specifies the names of the cells to be translated. Specify the names in the CDBA name space. The translator converts only cells with one of the specified names. To convert an individual cellview, specify both -cell and -view. Specifies the view names to be translated.
The translator converts only views with one of the specified names. Specifies the view types to be converted. Only cellviews that map to one of the specified view types are translated. Note: The view type is distinct from the view name used to describe the view directory in the library file system.
The technology library you specify must be defined in the CDB cds. Instead, it writes only data that does not already exist in the CDB version of the library. By default the translator overwrites existing data in the CDB library. March 37 Product Version 6. Incrementally translates only the routing data from OpenAccess to CDB and adds the route information on top of the cellview.
Note: The translated cellview should already exist on CDB before this argument can be used. Important The examples in this chapter use simple library structures to illustrate the use model of the translator.
The pictures do not show all the files typically found in an OpenAccess library, only those required to illustrate the point being described.
This example uses an OpenAccess library called design containing a number of different cells. This library was previously converted from CDB using the cdb2oa translator. March 38 Product Version 6. This means that all required technology information, simulation data, rule decks, SKILL files, scripts, and design management metadata exists already in CDB. Run the translator in the cdb directory using the following command line.
March 39 Product Version 6. The CDB cds. Converting into a Specified Directory When converting large databases containing many interdependent libraries, the default behavior of translating the library into the current directory might be restrictive. Use the -cdblibpath argument to direct the CDB version of the library to a specific directory.
The -cdblibpath argument accepts either a relative or an absolute path. March 40 Product Version 6. You can use this option only when the CDB version of the library does not exist. Important Regardless of any -cdblibpath specification, the translator always creates or updates the cds. To ensure that the correct cds.
To translate the design library into a specified directory, 1. Create a new directory for the new CDB version of the library. Run the translator in the cdb directory. March 41 Product Version 6. The OpenAccess cds. March 42 Product Version 6. Converting Multiple Libraries When using the translator from the command line, you can translate only one library at a time. To translate multiple libraries, you must run the translator separately on each library in turn.
For example, if your design library references information in libraries, deviceLib1, deviceLib2, refLib1, and refLib2, the directory structure might look like this.
To translate this database, you need to 1. Set up the file system structure for the CDB version of the library if it does not exist already 2. Determine the correct sequence of translation 3. Run oa2cdb once for each of the libraries in the database. When converting the libraries, oa2cdb will automatically translate them into the correct locations. The -cdblibpath argument is not required. March 43 Product Version 6. If you are translating multiple libraries from OpenAccess to CDB for the first time, Cadence recommends that you set up the directory structure for the CDB version of the database before you start.
Then use the -cdblibpath argument to direct the translated libraries to the correct location. This approach is recommended for two reasons. The process of methodically determining where each library will go is important in tracking the progress and success of the migration effort. Setting up the directory structure involves not only setting up library directories, but also other files and directories for storing simulation data, rule decks, SKILL files, scripts, and design management metadata.
Important Regardless of any path specified using -cdblibpath, the translator always creates or updates the cds. Determining the Sequence of Translation You must translate the individual libraries in the correct sequence so that definitions from the reference libraries are available in CDB at the time they are referenced.
The translator cannot determine this sequence automatically. You must do it manually and run the translator separately on each of the libraries in turn. March 44 Product Version 6. Identify the top cellview in your design and open it in your Virtuoso design environment.
Type Shift-f to display all the levels in the design. The layout editor opens the Tree window showing the entire hierarchy of instances inside the current cellview. The indentation shows the hierarchical relationships between the cellviews listed. The numbers in parentheses tell you how many instances of each cellview are present.
Translate the libraries one at a time, working from the lowest level library up to the top cellview. Resolving Circular Dependencies A circular dependency occurs when a cellview contains an instance of a cellview from another library which itself contains an instance of a cellview from the first library. March 45 Product Version 6. To resolve this situation, work from the lowest level in the hierarchy back up to the top cellview, translating individual cellviews as required so that the dependencies are satisfied.
To resolve the dependency shown, 1. Translate library refLib2. March 46 Product Version 6. Translate the rest of library refLib1, using the -nooverwrite option to prevent the cellview translated previously from being translated again. Note: Because refLib1 exists already, you do not need to use -cdblibpath.
The library is updated automatically in the correct location. March 47 Product Version 6. March 48 Product Version 6. Index A D application infrastructure files display resource file, display.
March 49 Product Version 6. O verifying geometry 28 verifying the currency of a placed oa2cdb instance and its master 29 getting help 35 translating location of executable 35 from the command line 35 overview of the translator multiple libraries 43 engine 14 to 16 determining the sequence of syntax 35 translation 44 OpenAccess resolving circular dependencies 45 DFII on OpenAccess 11 single libraries illegal names in 20 into a target directory 43 introduced 11 troubleshooting standard OpenAccess 11 log file 16 versions supported 12 U P usage parameterized cells oa2cdb 35 introduced 31 SKILL functions in 32 parent-child database file, pc.
S syntax command line validation 14 conventions 8 getting help with 35 oa2cdb T technology information display. March 50 Product Version 6. Pular no carrossel. Anterior no carrossel. Explorar E-books. Os mais vendidos Escolhas dos editores Todos os e-books. Explorar Audiolivros. Os mais vendidos Escolhas dos editores Todos os audiolivros.
Explorar Revistas. Escolhas dos editores Todas as revistas. Explorar Podcasts Todos os podcasts. Explorar Documentos. Enviado por RohininandanaDas. Denunciar este documento. Analisis Kasus CSR traidos bank and roche drugstore.
Pesquisar no documento. Separates a choice of options. Run the translator from the command line. Summary Section The Summary section provides information on the numbers of cells and views that were translated. Generated times. For example, If you specify the following command line March 19 Product Version 6. Using Environment Variables in cds. If the values are different, the translator issues an error March 24 Product Version 6.
The Display Resource File The display resource file specifies how your layers appear on display devices. Please let me know if you have any questions. The following conditions must be met in order to receive a sourcelink lite account.
To obtain a reference key please email help ece. Release check installation directory for specific Release Level adw ambit assura cd confrml dsm-dp dsm-se dsm-se edi et et ets ext finale GoldenGate ic icc ifv incisiv ius ldv mmsim mvs neocircuit oa psd soc spb spr spw tda testbench tsi usim vcc.
This entry was posted in Services , Software and tagged Cadence , software. Bookmark the permalink.
0コメント