• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. oa2cdb translation

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 17269
  • 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

oa2cdb translation

tkhan
tkhan over 15 years ago

Sorry for cross-posting here and on comp.cad.cadence, I wasn't getting a reply there...

Long story short, I need to translate a design back to IC5141 which
I've started in IC613. I tried the oa2cdb utility on an unimportant
library first, but get the following error:

megatron:/home/student1/guest2/cmrf8sf-cdb> /CMC/tools/cadence/
IC-6.1.4/tools/dfII/bin/oa2cdb -lib exampleVCO -cdslibpath ~/cmrf8sf/
lib.defs
*WARNING* envGetVal: Could not find variable 'dbStatCacheOn'
        in tool[.partition] 'cdba'.
*WARNING* envGetVal: Could not find variable 'dbInstNamingGlobalInc'
        in tool[.partition] 'cdba'.
ERROR   (OACDB-113): Failed to find the OpenAccess library
"exampleVCO"
                     because the library is not defined in /home/
student1/guest2/cmrf8sf/lib.defs
                     or is not readable. Ensure that the OpenAccess
library definition file
                     you specify defines the library you want to
translate and
                     that you have permission to read the library.

INFO    (OACDB-820): oa2cdb translation failed.

exampleVCO is defined in lib.defs

megatron:/home/student1/guest2/cmrf8sf-cdb> tail -1 ~/cmrf8sf/lib.defs
DEFINE exampleVCO exampleVCO

The permissions on the folder are

megatron:/home/student1/guest2/cmrf8sf-cdb> ls -ld ~/cmrf8sf/
exampleVCO
drwx------ 3 guest2 student 512 Apr 12 11:12 /home/student1/guest2/
cmrf8sf/exampleVCO/

Please advise.

Thanks,
Tarek

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Tarek,

    Don't have time to experiment and try this myself, but it may be related to the fact that lib.defs is not being supported by the Virtuoso tools from IC614 onwards. Now we have an OA plugin which means that  cds.lib is always used (this is to avoid all the trouble with trying to keep lib.defs and cds.lib in sync, when they don't quite share all the syntax).

    So try referencing a cds.lib instead, and if that doesn't work, I'd suggest contacting Cadence Customer Support.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tkhan
    tkhan over 15 years ago

    Hi,

    Andrew Beckett said:
    but it may be related to the fact that lib.defs is not being supported by the Virtuoso tools from IC614 onwards.

     

    I tried using the oa2cdb from IC6.1.3 and same result, with both cds.lib and lib.defs which were updated via Libray Path Editor before running oa2cdb. I'll get in touch with Cadence Support and hopefully we can resolve this.

    Thanks,

    Tarek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kdewan
    kdewan over 11 years ago

    Hi Tarekh/Andrew

    were you able to solve the rpoblem.. I am getting the same

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    What version of the tools are you using?

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kdewan
    kdewan over 11 years ago
    I am using IC615 and want to convert to IC514
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    OK, I tried this. It does need a lib.defs file still.

    So, first you need to do (in your OA directory, where the OA cds.lib is located):

       cdsLibEditor -batchWriteLibdefs lib.defs

    Then move to the directory that you want to create the CDB equivalent, and do:

       oa2cdb -lib mylib -cdslibpath /path/to/the/lib.defs

    That should work. Bear in mind that oa2cdb is really intended for emergencies only and is not intended to form part of a flow.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kdewan
    kdewan over 11 years ago

    Thanks Andrew..

     My this problem is solved.. but now I am getting error 

    THE CDB technology library <libname> is not valid becuase it does not contain a technology file. Ensure that any CDB technology library involed in the translation contains a techfile.cds file. 

    I am specifying the technology file using -tech <filename>

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kdewan
    kdewan over 11 years ago

     I am able to solve the technology issue. Now it is working

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Snawaz
    Snawaz over 8 years ago

    Hi,

    I need some help in oa2cdb conversion. I want to convert the Nangate open source standard cell library PDKv1_3_v2010_12. The base kit associated with it is NCSU-FreePDK3D45-1.1 . Can anyone kindly guide me on how to successfully convert the library from .oa to .cdb ?

    After using the following script I get these errors :

    SCRIPT:

    cdsLibEditor -batchWriteLibdefs lib.defs

    oa2cdb -cdslibpath ../lib.defs -lib NangateOpenCellLibrary

    ERRORS:

    194 cells and 744 cellviews were translated from library 'NangateOpenCellLibrary' in 65.2s.

    Message Summary:

    WARNING (OACDB-527): Layer-purpose pair '<layerName> <purposeName>' is not     
                         defined in the CDB technology file of library <libName>.
                         
                          Generated 138 times.

    ERROR   (OACDB-650): Cannot translate <shapeType> in cellview '<libName>         
                         <cellName> <viewName>' because layer-purpose pair          
                         '<layerName> <purposeName>' is not defined in the CDB      
                         technology file. To translate this object, define the      
                         specified layer-purpose pair in the CDB technology file.
                         
                          Generated 11362 times.

    ERROR   (OACDB-653): Cannot translate <number> instance terminals for instance   
                         <instanceName> in cellview '<libName> <cellName>           
                         <viewName>' because the CDB master cellview '<libName>     
                         <cellName> <viewName>' is not available. Ensure that the   
                         master is available in OpenAccess, translate it to CDB     
                         first and rerun the translator for the remaining cells in  
                         the library.
                         
                          Generated 2590 times.

    ERROR   (OACDB-670): Cannot translate pin <pinName> for terminal <terminalName>  
                         in cellview '<libName> <cellName> <viewName>' because the  
                         translator failed to find the CDB equivalent for the figure
                         used in the pin. Check the log file for messages indicating
                         why figures were not created.
                         
                          Generated 1602 times.

    ERROR   (OACDB-682): Failed to create <textDisplayType> type text display in     
                         cellview '<libName> <cellName> <viewName>' because of an   
                         unexpected exception. This is an internal program error. If
                         you are unable to isolate the problem, contact your Cadence
                         Customer Support representative for help.
                         
                          Generated 801 times.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Did you convert back the technology library first? 

    I would ask however, why are you converting an OpenAccess library back to CDB? The last CDB release is IC5141, which was released in 2004 and had its final hotfix in 2011 (over 5 and a half years ago). The oa2cdb route was only ever intended as a "disaster-only" conversion route, and is not something that is being actively maintained, especially this long after the end-of-support of IC5141.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information