Stats

  • Locked Locked
  • Replies 31
  • Subscribers 148
  • Views 29611
  • 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

How to change via level with skill in IC6

Eric L14

 In IC6, I have a bindkey which change via level (via1 to via2) . Main part of the code is:

; Current selected via
viaToBeChanged=car(geGetSelSet())

; new via identifier
newVia=dbOpenCellViewByType( technName viaName "layout" nil "r")
if( newVia then
  viaToBeChanged~>master=newVia
)

Do you know how doing the same thing in IC6 ?

Thanks in advance

Eric

Parents

  • From the cdb2oa syntax description I understand the following:

    viamap file is a list of the CDB via cellview masters to be created in the new oa library. It is also stated that the translator adds a new oaCustomViaDef in the new oa library.

    viamap is misleading as name since it does not seem to do any mapping.

    In our migration flow (tech1->tech2) We still need to convert let's say Via1 name into V1 by the mean of i.e.: dbCreateStdViaVariant or dbCreateVia and extract all via parameters from Via1 to copy them into V1. We must then erase all Via1 vias since in the target technology there is not such viaDef and we do not have the right to create one. 

    Please correct me if I am wrong but I do not see any major difference between dbCreateVia  and dbCreateStdViaVariant if it is not for the way we pass via parameters such as via layer enclosures, space, viaDef etc.

    As for 2 it would be great if there was already a solution but we have already our custom solution developed as you described. There is no point for us filling in a CCR for this.

    Can you please let us know if there is a CCR filled in for a function doing what you have described in you post of 01-14-2013 1:15 PM of this thread and we asked in the previous post? I mean the via pcell migration function or something similar. If any we would like to have it as reference in case we fill in a similar CCR.

    Best regards,

    Antonios

Reply

  • From the cdb2oa syntax description I understand the following:

    viamap file is a list of the CDB via cellview masters to be created in the new oa library. It is also stated that the translator adds a new oaCustomViaDef in the new oa library.

    viamap is misleading as name since it does not seem to do any mapping.

    In our migration flow (tech1->tech2) We still need to convert let's say Via1 name into V1 by the mean of i.e.: dbCreateStdViaVariant or dbCreateVia and extract all via parameters from Via1 to copy them into V1. We must then erase all Via1 vias since in the target technology there is not such viaDef and we do not have the right to create one. 

    Please correct me if I am wrong but I do not see any major difference between dbCreateVia  and dbCreateStdViaVariant if it is not for the way we pass via parameters such as via layer enclosures, space, viaDef etc.

    As for 2 it would be great if there was already a solution but we have already our custom solution developed as you described. There is no point for us filling in a CCR for this.

    Can you please let us know if there is a CCR filled in for a function doing what you have described in you post of 01-14-2013 1:15 PM of this thread and we asked in the previous post? I mean the via pcell migration function or something similar. If any we would like to have it as reference in case we fill in a similar CCR.

    Best regards,

    Antonios

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.