Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 16334
  • 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 open access translation

stuso

Hi Guys, 

i've just installed IC6 and i'm attempting to port a small test library. From the ciw i'm using tools -> conversion box -> CBD to OpenAccess Translator.

I am reading the manuals as i cannot get it to run but any tips from those who have been through this would be helpful.

Currently i have stripped my old cds.lib such that it references the following:

DEFINE stu_lib

DEFINE cdba_technology

At what point do i point the converter to the new oa_technology, should this also go in the old cds.lib?

Thanks

Stu 

 

 

 

Parents

  •  The lib.defs file is a new definition file which is used by non Virtuoso OA based tools. If you are using Encounter or 3rd party OA based tools, the lib.defs file is currently required. The cds.lib file has additional capabilities which are not supported by lib.defs so Cadence is developing an OA plug-in that other tools can use the cds.lib file in place of the lib.defs file with all the bells and whistles that cds.lib supports.

    It is always good to start with a new .cdsenv file as there are many new capabilities which you need to set. See the on-line Design Topics documentation for some of the most important ones (default constraint groups, via shapes, etc.). My .cdsinit file branches for specific IC6.1 things but is otherwise the same.

     The Assura menu issue is known, if you have a CDB version of Assura in your shell path instead of an OA version, it not only does not load the Assura menus but messes up the OA layout menus. We are looking for a fix to this at this time. If you check your cds.log file you will have an error which is not clear about the Assura issue. If necessary, that is you do not have Assura for IC6.1, remove the ASSURAHOME definition from your shell setup routines.

     Ted

Reply

  •  The lib.defs file is a new definition file which is used by non Virtuoso OA based tools. If you are using Encounter or 3rd party OA based tools, the lib.defs file is currently required. The cds.lib file has additional capabilities which are not supported by lib.defs so Cadence is developing an OA plug-in that other tools can use the cds.lib file in place of the lib.defs file with all the bells and whistles that cds.lib supports.

    It is always good to start with a new .cdsenv file as there are many new capabilities which you need to set. See the on-line Design Topics documentation for some of the most important ones (default constraint groups, via shapes, etc.). My .cdsinit file branches for specific IC6.1 things but is otherwise the same.

     The Assura menu issue is known, if you have a CDB version of Assura in your shell path instead of an OA version, it not only does not load the Assura menus but messes up the OA layout menus. We are looking for a fix to this at this time. If you check your cds.log file you will have an error which is not clear about the Assura issue. If necessary, that is you do not have Assura for IC6.1, remove the ASSURAHOME definition from your shell setup routines.

     Ted

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.