• 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. Design migration tool

Stats

  • Locked Locked
  • Replies 21
  • Subscribers 125
  • Views 38563
  • 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

Design migration tool

Faizan UL HAQ
Faizan UL HAQ over 10 years ago

Hi,

I have a problem to transfer the simulation files from one design kit to another design kit in cadence virtuoso. The simulation files and circuit diagrams are quite many and it will take ages for me if i tranfer the files manually. Is there any kind of tool which can convert one design kit circuit diagrams into another design kit circuit diagrams.
BR

  • Cancel
  • seanhuang
    seanhuang over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    With your help, I could modify "l" successfully, but "w" is not correct, no matter whether I add ("w" "lFinger Width") in conv.config. It seems that it only transferred the original w value into "User Property" instead of "CDF Parameter": As you can see the attached snapshot, Finger Width in "User Property" is right (600n), but in "CDF Parameter" it's always "2u". Is there any way to change "Finger Width" of "CDF Parameter"? Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to seanhuang

    You are not giving the correct destination parameter name - you’ve used the prompt that is shown on the form rather than the parameter name, which is why it is creating user defined properties (for Length as well). You need to do Tools->CDF->Edit and then look at what each property name is and use those instead. 

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • seanhuang
    seanhuang over 6 years ago in reply to Andrew Beckett

    Hi Andrew, sorry to trouble you again: With your help I could do successful migration, but when I copy the whole environment to my another workstation, it even couldn't execute the command (everything is same except different workstation). Please help to look at the snapshot and help me. Thanks so much!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to seanhuang

    This is indicating that it couldn’t open the file conv.config. That’s either because you didn’t have the permissions but looking at the fact that a full path worked it’s more likely to be because the SKILL path doesn’t include the working dir. Check what:

    getSkillPath()

    returns. Does it include “.”? If not, you can either give the path as “./conv.config” or use:

    setSkillPath(cons(“.” getSkillPath()))

    before running the abConv... function

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • seanhuang
    seanhuang over 6 years ago in reply to Andrew Beckett

    Hi Andrew, You are brilliant! Please help me for the last issue: Most transistor's length is "180n" as the string, but I encountered one transistor is "400n" which showed as the number "4e-07" in SKILL (As you can see from the snapshot). However when I manually change from 400n to 400.0n (or any other number) in Object Properties, the SKILL will recognize it as the string instead of the number. It's so strange! Thanks a lot!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to seanhuang

    Inside the fixing function (where you have the printf) you can put:

    if(numberp(val) then

      valAsNum=val

    else

      valAsNum=cdfParseFloatString...

    )

    I’m writing this on a mobile device so the cdfParseFloatString in the else branch is the line that’s already in the code. 

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • seanhuang
    seanhuang over 6 years ago in reply to Andrew Beckett

    You are so helpful, Andrew! Now everything works perfectly!Thank you so much!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Nikhil Malwatkar
    Nikhil Malwatkar over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    We want to try modifying this script for Layout migration. Is it possible for you to share the config file for this code? We want to check how the config file is written.

    Regards,

    Nikhil Malwatkar

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Nikhil Malwatkar

    I can't give the config for your case because I don't know what exactly you need to migrate. There's an example config in the comments at the top of the code, and there are numerous examples given in the other replies to this post. So there really ought to be enough examples to get you started.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Nikhil Malwatkar
    Nikhil Malwatkar over 5 years ago in reply to Andrew Beckett

    Thank you for your reply. We are trying to migrate a complete project from 1 technology to another technology. Both technologies are internal to my company. Thus the layouts to be migrated will have multiple level of hierarchies with standard logic cells/components etc. In such a case will the config file above (or others shared already) be helpful? 

    • 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