re-attaching library to different tech lib

Discussion in 'Cadence' started by vlsidesign, Feb 1, 2007.

  1. vlsidesign

    vlsidesign Guest

    I am migrating a library from Metal7 to Metal6. So I programmatically
    delete M7, change via types (ie. m1m7 to m1m6), and also re-attach
    library to the new tech lib. Most all of the vias re-attaches properly
    and point to new tech lib, but there seem to be some of the vias that
    don't, that are buried down in the hierarchy. I don't see a pattern in
    the ones that don't re-attach properly, so I was thinking to
    programmatically open all the cells in the library one at a time, and
    change the via 'libName' attribute to the new name. I have both tech
    libs (old and new) in my cds.lib file, but it will not let me change
    that attribute to the new name. I was hoping to get any suggestions to
    point me in the right direction or hints on how I might be able to
    resolve this. Thank you for any help and/or tips.
     
    vlsidesign, Feb 1, 2007
    #1
  2. vlsidesign

    S. Badel Guest

    Most all of the vias re-attaches properly
    I'm curious why this happens...
    No. It's a read-only attribute. To change an instance reference,
    use leReplaceAnyInstMaster() or leRemasterInstances().


    There is also ccpRenameReferenceLib(), which corresponds to "Rename Reference Library"
    in the Library Manager.



    Stéphane
     
    S. Badel, Feb 2, 2007
    #2
  3. vlsidesign

    vlsidesign Guest

    I'll try to find out why it is not doing all the symbolic vias, and
    post it here if I find out.
    I experimented, and leReplaceAnyInstMaster() function will work in my
    code well.
    Thank you so much for posting, this is very big help.
     
    vlsidesign, Feb 2, 2007
    #3
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.