• 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. Copy CDF between pcells, callback fails in copy

Stats

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

Copy CDF between pcells, callback fails in copy

RVERP
RVERP over 2 years ago

I have an application where I create a new pcell that is based on existing techno pcells. For this I copy the CDF from the techno pcell. I make a copy with cdfGetBaseCellCDF of the techno CDF and place it on my new pcell with cdfCopyCDF. The datatype is specified as baseCellData.

What I want to become is that the callback of my original and my copy behaves in the same way. Changing one CDF parameter and triggering the CB that then updates a variety of other parameters. I used this application in a number of different technologies and the application always behaves as aspected.

Until now, now I have a techno that doesn't seem to work this way. I copy the CDF to my new pcell, but when I change a parameter I get following error:

*** Error in routine cdfParseFloatString:
Message: *Error* cdfParseFloatString: argument #1 should be a string (type template = "t") at line 230 of file "*ciwInPort*"
Entering new debug toplevel due to error:

So the CB uses an incorrect variable, but since the baseCell CDF is a copy, everything must be correct here. I did a cross check between my original CDF of the techno pcell and my copied one. The default values are identical, but in my copy the CB fails while in the original it obviously passes. Are there any other sources of data the cdf CB can use that I'm overlooking here?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    It might be that the CDF callback for the technology is expecting other data to be there. For example, some foundries use a set of properties on the cell property bag (data.dm) to set default values and guide the callbacks; maybe those also have to be copied across to the destination cell?

    It's hard to diagnose without seeing the callback code unfortunately, because it rather depends on what is being passed to cdfParseFloatString.

    Andrew

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

    Thanks for the info. I have to look into it but I'm afraid copying the data.dm is not an option for my application.

    Having some insight in the callback procedure would indeed help a lot. I'll ask the fab, maybe they send me a copy SmileySmileySmiley

    • 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