• 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 SKILL
  3. create custom via and save it

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 143
  • Views 21373
  • 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

create custom via and save it

primemath
primemath over 8 years ago

Hi,

I was going through the create via form and saw that there is an option to save custom via.
But I can make the change and save it to the library, but then each time I restart icfb, the change is lost and it reverts to the previous.
How do i save it for usage even after restarting the icfb ?

Regards,
Priyankar

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Priyankar,

    Which IC version are you using? Type getVersion(t) in the CIW...

    The create via form changes quite a bit from one version to another, so it's important to know. I didn't see an option to save a custom via on the create via form in IC617 ISR8, but I may have been looking at the wrong thing or may be using a completely different version to you.

    Regards,

    Andrew.

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

    Andrew,

    This is the IC version that i am using "sub-version  IC6.1.6-64b.500.14.EHF2305 "



    This is the snapshot of the save via variant

    Regards,
    Priyankar

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

    OK, you were talking about saving via variants, not custom vias. I wondered whether that was what you meant, but given you were talking about "icfb" (which the tool has not been called since IC611 or so) threw me.

    If you pick the option to save to the design, you must give a name for the new via variant, and then you must save the design before exiting virtuoso. Having done that, in the next session I see:

    In other words, pick on the drop-down on the cyclic field, and ensure that you press the + in the tree next to the via that it was a variant of - and you should see all your saved via variants. A via variant is just a via with a set of parameters.

    In this case, I called it myM2M1 when I saved it. Of course, it has to be a variant of a via that is in the currently active validVias constraint for it to show up.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • primemath
    primemath over 8 years ago
    Andrew,

    I understand this approach,
    but as soon as i restart my icfb my save vias are lost, how can i keep them intact for later use ?

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

    Priyankar,

    The form I showed was in the session of virtuoso having quit and restarted. So it was working fine for me.

    You should be able to see them if you open your design and do:

    geGetEditCellView()~>viaVariants~>??

    If they're not there - did you really save the via variant and save the design before quitting Virtuoso? I'm also assuming  you're opening the same design (if you saved to design).

    Regards,

    Andrew.

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

    Andrew,

    i did save it but when i restart the icfb i see only the via i have placed whne i open create via i dont see that via option available any more ...

    This is the snapshot showing via placed but not coming under create via options.

    Regards,
    Priyankar

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

    Hi Priyankar,

    In the tree in the drop-down list on the left side there's a [+] next to contPSD_OA. Click on that [+] to expand it (it will then show [-]). Then you should see it. In my picture I was showing the expanded tree, whereas you're seeing the collapsed tree which is what appears by default.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • primemath
    primemath over 8 years ago
    Hi Andrew,

    Thanks That is right it was my mistake i didnt notice that.
    But when i try to access the same via in different design i am not able to access how can i do that ?

    Regards,
    Priyankar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • primemath
    primemath over 8 years ago
    Andrew,
    Also even when i do file->closedata then also my saved changes are lost.
    Regards,
    Priyankar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Hi Priyankar,

    When you save a viaVariant into a design, it's only for that design. You'd have to save it to the technology library if you want to share it amongst multiple designs (you could always create your design library to reference the technology library rather than attaching it, and then  you would be able to save into your own technology library - this is the ITDB mechanism).

    Currently the "Load Physical View" command in VLS XL doesn't support loading via variants from another design - there's CCR 1062215 asking for this, but it hasn't been implemented yet. If you want this, please contact customer support so that a duplicate request can be filed.

    I do have some SKILL code written by a colleague a few years back to transfer via variants from one design to another, but I'm not sure it's quite in a fit state to publish here.

    I am also rather doubtful that "close data" could lose the saved changes (unless you didn't actually save the cellView; note that the save icon on the create via form doesn't actually cause the cellView to be saved to disk - it just stores the viaVariant in the cellView; you must hit the save icon in the layout editor to actually save the changes). Maybe you didn't save the cellView.

    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