Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 14235
  • 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

ultra pcell with dbCreateParamInstByMasterName

bsrin

Hi All,

I am creating a ultra pcell consists of pch_fet cell (pcell) using dbCreateParamInstByMasterName. The pcell has "l" and "w" parameters. While Instantiating the ultra pcell with required l and w, it looks only l and w are changing. But, other parameters like dummies w and l are not changing. It seems the callbacks associated with l and w of pch_fet are not executed.

Can somebody tell me how to overcome this issue. How to get the callbacks associated l and w of basic pcell. 

 

Thanks,

bsrin 

  • theopaone

    Hi Bsrin

    You are correct, the callbacks do not get evaluated when creating a pcell instance. The callbacks are associated with the CDF which is bypassed when you use dbCreateParamInstByName. You have to find the callbacks and evaluate them in your code.

    Finding the instance CDF:

    instId = dbCreateParamInstByName( ... )

    cdfgData = cdfGetInstCDF( instId )

    Now you have a variable called cdfgData, in SKILL this is in scope of your callbacks.

    wParam = cdfFindParamByName( cdfgData "w" )

    when( wParam~>callback evalstring(wParam~>callback) )

    This should update the other parameter(s) on the instance as a side effect of the callback.

    Ted

  • skillUser

    Hi Bsrin,

    In addition to what Ted said, there are two functions that might help, vfoSetParam() and vfoSetParams()  which can set a CDF parameter (or multiple parameters, if using the second function) and trigger the callback(s) to run.

    Hopefully this will help you.

    Best regards,

    Lawrence.

  • bsrin

    Hi Ted/Lawrence,

    Sorry for the late reply,  I'm in vacation. 

    First of all, thanks for your detailed solution. Its working fine now.

    Thanks,

    bsrin.

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.