Create a tech lib with skill

Discussion in 'Cadence' started by camelot, Mar 5, 2010.

  1. camelot

    camelot Guest

    Hi,
    could someone help me in creating a technology library in skill?

    Example:
    I've a tech file named mytech.ascii (in ascii format) and I want to
    create the lib "NEW_TECH_LIB" loading this ASCII techfile. Something
    similar to the first option when you create a new lib interactively.

    Thank you,

    Camelot
     
    camelot, Mar 5, 2010
    #1
  2. camelot

    Riad KACED Guest

    Hi Camelot,

    The following Skill procedure does what you want.
    1. Load this procedure into your CIW
    2. Execute the procedure as following:
    CIW> RKcreateTechLib("NEW_TECH_LIB" "." "mytech.ascii")
    The second argument above, i,e "." is the path where "NEW_TECH_LIB" is
    created. The current directory in this example. You may change this.
    The techFile Skill functions as below are all documented in the
    Technology File and Display Resource File SKILL Reference Manual. This
    manual is available from your Cadence stream at the following
    location:
    $CDSHOME/doc/sktechfile/sktechfile.pdf

    ; Skill starts here
    procedure( RKcreateTechLib(libName libPath techFileName "ttt")
    let((techFileId)
    ; 1. Create the technology library
    when( ddCreateLib(libName libPath)
    ; 2. create the techfile fo the technology library, open it in W
    mode
    techFileId = techOpenTechFile(libName "techfile.cds", "w")
    ; 3. compile the ascii techfile for the new library
    tcLoadTechFile(techFileId techFileName "w")
    ; 4. save the compiled techFile to the new library
    techSaveTechFile(techFileId)
    ; 5. close the techFile
    techCloseTechFile(techFileId)
    )
    )
    )
    ; Skill ends here

    Regards,
    Riad.
     
    Riad KACED, Mar 5, 2010
    #2
  3. camelot

    camelot Guest


    Thank you very much!!

    Regards,

    Camelot
     
    camelot, Mar 8, 2010
    #3
  4. camelot wrote, on 03/08/10 07:20:
    Probably wise to call techGetTechFileName() rather than hardcoding
    "techfile.cds" as then it will work in both IC5141 and IC61. If you use
    "techfile.cds" you'll need to change the code when you go to IC61.

    For example:

    techGetTechFileName(techOpenDefaultTechFile())

    Regards,

    Andrew.
     
    Andrew Beckett, Mar 9, 2010
    #4
  5. camelot

    camelot Guest

    Yes Andrew, I used this function just for compatibility issues, thank
    you, once again :) , for underlining it!

    Camelot
     
    camelot, Mar 9, 2010
    #5
  6. camelot

    Riad KACED Guest

    Hi Andrew,

    Thanks for highlighting this !
    I did not know this one I would admit.

    Regards,
    Riad.
     
    Riad KACED, Mar 9, 2010
    #6
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.