Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 27978
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

cdb to oa conversion

Charanraj Mohan

Hey,

 I have a library in Cadence 5 and I need to convert it to Cadence 6. For this I do the following in the Command window (Orange window environment) in steps. Consider that my library is 'eva' is original in Cadence 5, HITKIT 3.7 AMS35 and I want to convert this library to Cadence 6 HITKIT 4.10 library.

Steps followed-

1. Create a temporary directory

mkdir $HOME/tmp

cd $HOME/tmp

2. Create cdb and oa directories and change the directory to cdb

mkdir cdb

mkdir oa

cd cdb

3. Create cds.lib file with the following content inside

DEFINE eva /directory_of_eva

4. Put/Copy this file into the cdb directory.

5. Change the directory to oa

cd ../oa

6. Execute cdb2oa to convert the library to oa database

cdb2oa -lib eva -cdslibpath ../cdb

(I assume the converted library file to be in the directory oa)

I get the following error:

ERROR   (CDBOA-500): Cannot translate CDB design library <path>/<name> to        
                     OpenAccess because CDB technology library <name> referenced
                     by the CDB design library is not available in the          
                     OpenAccess format. Before translating the CDB design       
                     library, ensure that all the referenced CDB technology     
                     libraries are available in OpenAccess and defined in       
                     'cds.lib'.
                     
                      Generated once. The translator stopped because the CDBA   
                     library references an attached technology library that does
                     not exist in OpenAccess.
                      Check the source library files and correct the library    
                     attachments as required. Ensure that the cds.lib file is   
                     present in the current directory and any technology library
                     that is referenced by the current library is defined in the
                     cds.lib file and is available in OpenAccess at the time it
                     is referenced. If the design library is referencing itself
                     as an attached technology library, ensure that there is an
                     appropriate tech.db technology file present in the         
                     OpenAccess library directory.

I have done the normal procedure for cdb to oa conversion. Does this imply that I have to also have a cds.lib file in the oa folder with all the design libraries ??

Thanks in advance.

Parents

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

Reply

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

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.