• 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. cdb2oa from command line on multi processors?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14308
  • 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

cdb2oa from command line on multi processors?

stuso
stuso over 14 years ago

Hi all,

is it possible to run cdb2oa from the command line on multiple processors? I'm looking for a way to speed it up a little, i'm converting a whole projects worth of libs from cdb 5141 to OA IC6 & its taking some time.

Cheers

Stu

 

 

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Stu,

    There's no multi-threaded or distributed options for cdb2oa (not really worth the bang for the buck). However, there's nothing to stop you running it for more than one library in parallel, provided you've sorted out any dependencies first.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stuso
    stuso over 14 years ago

    Hi Andrew, sorry but what do you mean by dependencies?

    Here is an example of the command i am running:

     cdb2oa -cdslibpath 5141_cds.lib -lib STU_LIB -log .STU.log -mapundefinedpingroups strong -ignorelocks -oalibpath ./NEW_OA_LIB -abspath -mapviaparams

    One issue i can see is that this command currently writes the new lib to my OA cds.lib, so 2 parallel cdb2oa runs may attempt to edit the new cds.lib at the same time. I'll check the manual see what i can do to disable writing to cds.lib (which is not really required anyway as I can do that manually).

    Thanks

    Stu

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

    Hi Stu,

    By dependencies I mean that you ideally want to convert the libraries bottom up. If you're converting a single library, you should be OK. One way to workaround the writing of a cds.lib (I didn't check to see if there's an arg to stop this) is to do the conversion in a separate directory per library, and then combine them afterwards.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stuso
    stuso over 14 years ago

     Hi Andrew, yes i see what you mean now & yes we have tried to do such a bottom up approach as sensibly as possible  (we have ~ 50 libs in this project).

    Thanks for all the advice

    Stu

     

    • 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