• 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. How to automatically store technology version on instance...

Stats

  • Locked Locked
  • Replies 17
  • Subscribers 144
  • Views 19136
  • 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 automatically store technology version on instance in schematics and layout?

Sheppy
Sheppy over 9 years ago

Hi,

I'd like to store the version number of the PDK on an instance when this instance is instantiated in schematic or layout. I need this in order to be able to check with which version of the PDK a particular design has been made. Later, I will create a script that hierarchically checks all instances of a given design, and reports the used versions. This will then be a script run at tape-out to ensure all devices are generated with the correct (latest) PDK version.

It could be done by adding a parameter with the version number as value to the CDF, like this:

cdfCreateParam( cdfId
        ?name           "PDK_version"
        ?prompt         "PDK Version"
        ?defValue       "x.y.z"
        ?type           "string"
        ?display        "t"
        ?editable       "nil"
        ?storeDefault   "yes"
)

However, if the PDK gets updated, the version number will be increased, which would mean, with this implementation, that the CDF of all cells in the library have to be updated to the new version. Of course, this could be automated, but i would like to use a different approach.

The version of the PDK which is loaded in Virtuoso is stored in an environment variable called TECH_VERSION. It can be retrieved by doing:

getShellEnvVar( "TECH_VERSION" )

What I would like to happen is that when the instance is instantiated, the value of TECH_VERSION is automatically stored in the CDF parameter PDK_version. Something like this doesn't work:

cdfCreateParam( cdfId
        ?name           "PDK_version"
        ?prompt         "PDK Version"
        ?defValue       "getShellEnvVar( \"TECH_VERSION\" )"
        ?type           "string"
        ?display        "t"
        ?editable       "nil"
        ?storeDefault   "yes"
)

This would simply put the text "getShellEnvVar( "TECH_VERSION" )" as value in the "PDK_version" field.

An other solution could be by putting some code in a call-back procedure that puts the version number in the parameter value. However, this only works when this call-back procedure is triggered. If a default device is instantiated, with no modifications to its parameters, the call-back will not be triggered, thus the version number will not be set.

So, I think this has to be a post-instantiation trigger. And I don't know how to do that properly. Any help is highly appreciated.

If an other solution is possible, I would surely like to know that as well.

Thanks in advance.

With kind regards,

Sjoerd

  • Cancel
Parents
  • Sheppy
    Sheppy over 9 years ago

    Hi Yi,

    Very interesting solution to their problem, Never thought of "hijacking" a standard form.

    I have tested it, but it doesn't work. It doesn't work with specifying a different _doneAction procedure. The problem is: the form for creating a new instance does not have an "OK" button, so the form is never "done". I haven't found an other entry in the form that gets triggered once an instance has been created (by clicking in the layout/schematics window). Just for reference, below the code I tested.

    procedure( spdkHiCreateInst()
        let( (  ( port nil )
            ( fileName "/tmp/spdkHiCreateInst.il" ) )
            port = outfile( fileName )
            fprintf( port "leHiCreateInst()\n" )
            fprintf( port "leCreateInstForm->_doneAction = \"spdkHiCreateInstCB()\"" )
            close( port )
            load( fileName )
            sh( strcat( "rm -f " fileName ) )
        ) ;;; end of let
    ) ;;; end of procedure spdkHiCreateInst

    procedure( spdkHiCreateInstCB()
        let( ()
            ;;; Call the original callback...
            finishEnterFun()
            ;;; And the custom part...
            printf( "Done!\n" )
        ) ;;; end of let
    ) ;;; end of procedure spdkHiCreateInstCB

    hiSetBindKey( "Layout" "<Key>I" "spdkHiCreateInst()" )

    The code (the procedure spdkHiCreateInst) is working. When I do the lines below with the form still open, it is showing that the _doneAction is set to my custom callback.

    f=hiGetCurrentForm()

    formStruct@0x16edd3e0

    f->_doneAction

    "spdkHiCreateInstCB()"

    This is identical to:

    leCreateInstForm->_doneAction

    "spdkHiCreateInstCB()"

    Although it is not working in this particular case,  I'll keep this solution, might be useful for some other problem.

    Thanks for all your suggestions.

    With kind regards,

    Sjoerd

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Sheppy
    Sheppy over 9 years ago

    Hi Yi,

    Very interesting solution to their problem, Never thought of "hijacking" a standard form.

    I have tested it, but it doesn't work. It doesn't work with specifying a different _doneAction procedure. The problem is: the form for creating a new instance does not have an "OK" button, so the form is never "done". I haven't found an other entry in the form that gets triggered once an instance has been created (by clicking in the layout/schematics window). Just for reference, below the code I tested.

    procedure( spdkHiCreateInst()
        let( (  ( port nil )
            ( fileName "/tmp/spdkHiCreateInst.il" ) )
            port = outfile( fileName )
            fprintf( port "leHiCreateInst()\n" )
            fprintf( port "leCreateInstForm->_doneAction = \"spdkHiCreateInstCB()\"" )
            close( port )
            load( fileName )
            sh( strcat( "rm -f " fileName ) )
        ) ;;; end of let
    ) ;;; end of procedure spdkHiCreateInst

    procedure( spdkHiCreateInstCB()
        let( ()
            ;;; Call the original callback...
            finishEnterFun()
            ;;; And the custom part...
            printf( "Done!\n" )
        ) ;;; end of let
    ) ;;; end of procedure spdkHiCreateInstCB

    hiSetBindKey( "Layout" "<Key>I" "spdkHiCreateInst()" )

    The code (the procedure spdkHiCreateInst) is working. When I do the lines below with the form still open, it is showing that the _doneAction is set to my custom callback.

    f=hiGetCurrentForm()

    formStruct@0x16edd3e0

    f->_doneAction

    "spdkHiCreateInstCB()"

    This is identical to:

    leCreateInstForm->_doneAction

    "spdkHiCreateInstCB()"

    Although it is not working in this particular case,  I'll keep this solution, might be useful for some other problem.

    Thanks for all your suggestions.

    With kind regards,

    Sjoerd

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information