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

  • Hi Ted,

    I've taken your advice and had a look at that documantation and also contacted cadence to help with the issues as we go along. I think our transaltion is a bit simpler as our process vendor has actually provided us with a OA version of the kit.

    So the method i found that sort of works for us ( i say sort of as we have lots of small isues that may or may not be related) was to:

    - Start oa from a new distinct oa directory

    - create a new cds.lib here (did so with a text eitor) and define only the oa_kit technology

    - Run the converter from the CIW, select one libray to convert, stu_test in our case

    I see now that IC6 also uses a def.lib, so we are considering whether or not to disable def.lib for now (this can be done by a setenv according to the documentation)  


    Thanks 

    Stu 

     p.s

    I've also found a couple of other things thus far that have helped me get IC6 running:

    1) Start from fresh with the .cdsenv & .cdsinit from the IC6 samples

    2) Set the $path to include the ASSURA IC6 ...tools/bin as otherwise my layout had issues loading the menus. I'm looking into this in morw deoth as we are not 100% sure why this is the case. 

     

Reply

  • Hi Ted,

    I've taken your advice and had a look at that documantation and also contacted cadence to help with the issues as we go along. I think our transaltion is a bit simpler as our process vendor has actually provided us with a OA version of the kit.

    So the method i found that sort of works for us ( i say sort of as we have lots of small isues that may or may not be related) was to:

    - Start oa from a new distinct oa directory

    - create a new cds.lib here (did so with a text eitor) and define only the oa_kit technology

    - Run the converter from the CIW, select one libray to convert, stu_test in our case

    I see now that IC6 also uses a def.lib, so we are considering whether or not to disable def.lib for now (this can be done by a setenv according to the documentation)  


    Thanks 

    Stu 

     p.s

    I've also found a couple of other things thus far that have helped me get IC6 running:

    1) Start from fresh with the .cdsenv & .cdsinit from the IC6 samples

    2) Set the $path to include the ASSURA IC6 ...tools/bin as otherwise my layout had issues loading the menus. I'm looking into this in morw deoth as we are not 100% sure why this is the case. 

     

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.