Stats

  • Locked Locked
  • Replies 8
  • Subscribers 145
  • Views 18706
  • 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

SKILL Variable

hrishikesh

I am new to Cadence SKILL. I am trying to understand a SKILL script file containing many procedures. Many of these procedures use a variable which holds a constant list. But it doesn't seem to be assigned anywhere in the script file. Can you suggest any possible place from where it could be assigned? Is there any way in SKILL to import variables from another file?

Parents

  • Hrishikesh

    If you use this code:

     procedure(CCFwhereVarSet(varName newValue)
        printf("Variable %s set to %L in %L\n" varName newValue get_filename(piport))
        ; stacktrace()
        newValue
    )

    and then do:

    setguard('theVarYouWantToCheck 'CCFwhereVarSet)

    (replace 'theVarYouWantTo Check with whatever name you're looking for), it will tell you the file where it is set (if a SKILL file; not if set in a context file unfortunately). You could also uncomment the stacktrace() to tell you which function it was in when the variable was set.

    Might help...

    Andrew.

Reply

  • Hrishikesh

    If you use this code:

     procedure(CCFwhereVarSet(varName newValue)
        printf("Variable %s set to %L in %L\n" varName newValue get_filename(piport))
        ; stacktrace()
        newValue
    )

    and then do:

    setguard('theVarYouWantToCheck 'CCFwhereVarSet)

    (replace 'theVarYouWantTo Check with whatever name you're looking for), it will tell you the file where it is set (if a SKILL file; not if set in a context file unfortunately). You could also uncomment the stacktrace() to tell you which function it was in when the variable was set.

    Might help...

    Andrew.

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.