cdb to oa conversion

Yes, in the destination directory you should have a cds.lib with all the reference libraries (e.g. technology libraries) that you need. Otherwise it can't find information about the technology.

If you were converting everything, you'd convert the leaf level technology libraries first, then build upwards. However, if you already have an OA version of the PDK you should just be able to reference that in the destination cds.lib file.

Regards,

Andrew.

Thanks Andrew for your quick reply. I used the GUI conversion tool to do the conversion. I get the following warnings.

Message Summary:

WARNING (CDBOA-406): Directory <path>/<name> is in a cellview. The directory  

                    and its contents will be copied to the destination database

                    but will not be translated.

                     Generated once. Neither CDBA nor OpenAccess supports      

                    directories in cellviews. The directory and its contents  

                    are copied to the destination library but are not          

                    translated. This could mean that you end up with CDBA data

                    in the OpenAccess version of your library. Check the      

                    directory in question. If it contains data that needs to be

                    translated, correct the source data so that it conforms to

                    legal directory structure conventions and then run the    

                    translator again.

WARNING (CDBOA-605): For cellview <path>/<name> the view type implied by the  

                    file name (<viewtype>) differs from the view type held in  

                    the database (<viewtype>). Creating a view of type        

                    <viewtype> in OpenAccess.

                     Generated 8 times. The translator has encountered a CDBA  

                    cellview for which the view type stored in the cellview    

                    data file differs from the view type implied by the        

                    cellview file name. OpenAccess expects a cellview filename

                    to reflect the stored view type. The translator identifies

                    conflicting view type information and fixes it by changing

                    the cellview filename to agree with its stored view type.

                     For example, a CDBA cellview with the stored view type    

                    maskLayout to be called symbol.cdb. This would be          

                    translated into an OpenAccess cellview of type maskLayout  

                    called layout.oa.

                     To prevent these warnings from being generated, modify    

                    your CDBA data to ensure that the view type implied by the

                    filename matches the view type stored for the cellview. For

                    example, if the filename is sch.cdb, then the view type    

                    should be schematic.

WARNING (CDBOA-649): There is a mismatch between the default values of CDF    

                    param and pcell superMaster param. The CDB2OA translator  

                    will continue. However, for improving data translation    

                    match the default value of the CDF param with the pcell    

                    superMaster param in CDB data.

                     Generated 3 times.

Is there a way in the settings of  'CDB to OpenAccess Translator' to avoid these errors, though their severity are low and I used different directory during translation by rule ??

I also noted this. When I open the top cell of all my designs in the translated library, I can see a windows popping and it tells--Missing Masters: The following masters are used in this cellview, but cannot be found in your search path:

Library       Cell        View

.

.

.

.

(I have five cell listed here)

& when I look into the errors in my top cell-schematic (by pressing g), I can see the comment  'Error: unbound instance--Library_name cell_name symbol (basic opin symbol).

How to avoid these kind of errors during translation ? there should be few settings in the GUI tool-'CDB to OpenAccess Translator' such that a library with 'no error' in cadence 5 is being converter to cadence 6 with same 'no error'.

Thanks in advance.

The final problem simply means that you didn't include all the relevant libraries (e.g. the basic library which is in the IC61X installation) in your destination cds.lib file. You don't need to translate these, but you do need to reference them.

You'd want to put something like:

analogLib $(inst_root_with:tools/dfII/bin/virtuoso)/tools/dfII/etc/cdslib/artist/analogLib
basic $(inst_root_with:tools/dfII/bin/virtuoso)/tools/dfII/etc/cdslib/basic

in your cds.lib file.

I don't think there's a way to suppress warnings. The warnings are reasonable - telling you about differences in what is supported between CDB and OA. In terms of errors - that's just a matter of you ensuring the data setup is correct. There are occasions (here and there) where something that was done in CDB and tolerated can't be supported in OA - but these are explained at the time.

Anything you're unclear about you should talk to customer support.

Regards,

Andrew.

Thanks Andrew once again :-)

The reason behind the errors was the following:-

During CDB to OA translation, a library named 'IOLIB_ANA_4M' got changed to 'IOLIB_ANA_4M_local'. Similarly, another library name 'IOLIB_4M' changed to 'IOLIB_4M_local'. This happened only in the schematic and in cds.lib file, it is correct.

I metaphor these kind of mismatches to cases like- when we do PEX extraction using CALIBRE, the calibre file (or the parasitic extracted file) possess  port names in capital letters, even though we give the names in small letters in the schematic/symbol  and may be with little change in I/O/IO pin configuration from those in schematic/symbol. And later we need to 'Check and safe' to correct errors.

Unless a justification is given to such cases, the conversion (a Cadence tool) and extraction (a Mentor Graphics tool) tools are to be subjected to improvement and bug-fixed.

I have no idea what problem you're describing above. 

CDB to OA Conversion is something that has had many fixes over the years - it was very important to make it pretty robust. It's been used a huge number of times since we first introduced OA versions of the tools about 12 years or so ago. However, it does require valid data and setup to use it properly.

If there are bugs, you need to report them with clear information as to what went wrong. I don't get that from above because you didn't really explain the specifics - so please go to customer support.

Regards,

Andrew.