• 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. Trigger callbacks automatically for a schematic pcell

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 6926
  • 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

Trigger callbacks automatically for a schematic pcell

prasadtammana
prasadtammana over 2 years ago

Hi, 

I've created a schematic pcell which has Width and Length as the parameters. Based on Length of the instance, I want to calculate another parameter called MOM_fingers. So I edited the CDF of the pcell and added a SKILL procedure as callback to calculate MOM_fingers based on Length. Every time I change the Length of the instance, I'm using CCSinvokeCdfCallbacks(geGetEditCellView()) to trigger the callbacks which is then updating the MOM_fingers. 

But, I want the callbacks to be triggered automatically, just like the way a transistor's total width gets updated immediately after changing the finger width of the transistor. Could someone let me know how to trigger the callbacks immediately after I update the Length of the pcell without using CCSinvokeCdfCallbacks(geGetEditCellView()). 

Thanks,

Prasad

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    If I've understood you properly, you have a cell (let's call it "prasadcell") which has parameters Width, Length and MOM_fingers. You've added a CDF callback on the Length parameter for the CDF of prasadcell which computes MOM_fingers (presumably sets cdfgData~>MOM_fingers~>value)? If so, the callbacks should be triggered when you create instance or edit properties on an instance of prasadcell - there's nothing extra you need to trigger it - that's how CDF callbacks are supposed to work.

    If that's not happening, something must be wrong with your setup, which is going to be hard to diagnose without seeing it. Perhaps you should contact customer support?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    If I've understood you properly, you have a cell (let's call it "prasadcell") which has parameters Width, Length and MOM_fingers. You've added a CDF callback on the Length parameter for the CDF of prasadcell which computes MOM_fingers (presumably sets cdfgData~>MOM_fingers~>value)? If so, the callbacks should be triggered when you create instance or edit properties on an instance of prasadcell - there's nothing extra you need to trigger it - that's how CDF callbacks are supposed to work.

    If that's not happening, something must be wrong with your setup, which is going to be hard to diagnose without seeing it. Perhaps you should contact customer support?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • prasadtammana
    prasadtammana over 2 years ago in reply to Andrew Beckett

    Hi Andrew, 

    Thanks for your reply. I added CDF callback on MOM_fingers parameter instead of Length parameter by mistake. I corrected it now and it is working as expected.

    Thank you,

    Prasad

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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