Request for Support with CDF Update Issue after importing .spi file in virtuoso

Hi Yogesh,

Please ensure enable trigger callback in the 'Input' tab...

Rob.

Thank you, RobMan.

I did that in the first place while importing the .spi file, but the problem persists.

If you can suggest some skill code modifications or share your skill code, that would be a great help!

Thanks again,

Cheers!

Yogesh

Andrew has written some code to trigger the callbacks...

How to call CDF callbacks procedurally from SKILL to update CDF parameters?

In this instance though it's unclear on what the dependency might be. If you tweak the 'w' (e.g. 150) on the schematic does the 'Wfg' update?

Rob.

Rob,Thank you for your help.

However, I'm still facing the same problem. I would appreciate it if Andrew and Aurel could also provide their insights on the cause and potential solutions.

If you could help fix the skill code I've written, that would be a big favour.

For example

Clean library :

CDF parameter of mos

Wfg = 140  nm

w    =   140 nm

Imported .spi  library :

CDF parameter of mos

Wfg = 100  nm

w    =   140 nm

My skill code for CDF update 

let((libName cdfId oldParam)
libName = "STD_CELL_SPI"
foreach(cell ddGetObj(libName)~>cells
cdfId = cdfGetBaseCellCDF(cell)
when(cdfId
;; Use cdfFindParamByName to locate "Wgf"
oldParam = cdfFindParamByName(cdfId "Wfg")
when(oldParam
;; Create "w" and transfer ALL necessary attributes
cdfCreateParam(cdfId
?name "w"
?prompt oldParam~>prompt
?defValue oldParam~>defValue
?type oldParam~>paramType
?display oldParam~>display
?callback oldParam~>callback
?units oldParam~>units
?choices oldParam~>choices ; Added: essential for cyclic/radio
?parseAsNumber oldParam~>parseAsNumber
?parseAsCEL oldParam~>parseAsCEL
)

;; Correct way to delete: cdfDeleteParam is valid if defined,
;; otherwise parameters are typically managed via cdfId~>parameters
cdfDeleteParam(oldParam)

;; Save the base CDF changes to disk
cdfSaveCDF(cdfId)
printf("Updated %s: Wfg changed to w\n" cell~>name)
)
)
)
)

I will be grateful for your help. Please help in !

Thanks!

Rob,Thank you for your help.

However, I'm still facing the same problem. I would appreciate it if Andrew and Aurel could also provide their insights on the cause and potential solutions.

If you could help fix the skill code I've written, that would be a big favour.

For example

Clean library :

CDF parameter of mos

Wfg = 140  nm

w    =   140 nm

Imported .spi  library :

CDF parameter of mos

Wfg = 100  nm

w    =   140 nm

My skill code for CDF update 

let((libName cdfId oldParam)
libName = "STD_CELL_SPI"
foreach(cell ddGetObj(libName)~>cells
cdfId = cdfGetBaseCellCDF(cell)
when(cdfId
;; Use cdfFindParamByName to locate "Wgf"
oldParam = cdfFindParamByName(cdfId "Wfg")
when(oldParam
;; Create "w" and transfer ALL necessary attributes
cdfCreateParam(cdfId
?name "w"
?prompt oldParam~>prompt
?defValue oldParam~>defValue
?type oldParam~>paramType
?display oldParam~>display
?callback oldParam~>callback
?units oldParam~>units
?choices oldParam~>choices ; Added: essential for cyclic/radio
?parseAsNumber oldParam~>parseAsNumber
?parseAsCEL oldParam~>parseAsCEL
)

;; Correct way to delete: cdfDeleteParam is valid if defined,
;; otherwise parameters are typically managed via cdfId~>parameters
cdfDeleteParam(oldParam)

;; Save the base CDF changes to disk
cdfSaveCDF(cdfId)
printf("Updated %s: Wfg changed to w\n" cell~>name)
)
)
)
)

I will be grateful for your help. Please help in !

Thanks!

First of all, this is a community forum, so asking for a response (in your initial post) from specific forum members is a bit presumptuous (I'm on vacation too). Secondly, I would have given exactly the same answers as Rob did.

Your code will not do what you want, as it is creating a new CDF parameter in the Base CDF itself. That's not your issue, and so your code is completely inappropriate. It's not a matter of fixing it but throwing it away altogether.

The right answer is one of the approaches that Rob suggested. You didn't give any specific information about what the SPICE file looked like, what mapping you used, or which PDK you're using. However, I wonder whether there is an order dependency in the CDF callbacks. If so, try choosing the "For all parameters specified on the instance line" checkbox on SPICE IN (shown in Rob's screenshot above), or using the ?order argument to CCSinvokeCdfCallbacks to limit the callbacks to call (say) just "w" it might be calling the callback for Wfg first which then sets w from Wfg). You gave no information about what happened when you tried either approach earlier or exactly what you tried.

OK, back to vacation time...

Andrew