Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 15740
  • 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

bsource Interpreted Label cdsParam() display

T Opperman

I have a subckt model file that instances a bsource capacitor device labelled "c1". From the Results Browser and the ADE "print DC Operating Points" command, I can find the bsource operating point parameters are under "MyCircuitName.NonLinCap.c1". This contains the "cap" parameter which I am looking for.

I would like to display this DC "cap" parameter on the schematic while doing DC design using a cdsParam() label. So I edited the CDF parameters for this device, selected "Operating Point Results" and tried adding a parameter called "cap". When I click on "Annotate->DC Operating Points" in ADE, this device's label shows nothing. I have also tried to specify "c1.cap" under the Edit CDF->cdsParam() form. It does however work when I try to display Instance/CDF parameter, which tells me that there is nothing wrong with my symbol.

Any suggestions and how to display this DC parameter as a label on my schematic? I am currently working on IC614.

Regards,

Tjaart

Parents

  • I didn't see your last post until after I'd put together a small example, which is using precisely the code you provided (I thought it looked OK, I just wanted to check). So in the attached (assuming I can get it to upload), there's a library "mytechlib" with a testbench inside which references the "caplnmos" component (which was copied from cap in analogLib, and then the CDF changed to have a default model of caplnmos). There's an ADE state which you can load an simulate and then annotate the DC operating point.

    If you load "forum.il" (your code) and then do a Simulation->Netlist->Recreate, it should then work. The reason it probably didn't work for you was that you didn't force the netlist to be recreated. The opParamExprList info gets stored in the mapping directories when you netlist, and so if the CDF was changed after netlisting, it won't have an impact unless netlisting is done again (and if nothing changed in the schematic, you'll have to force a netlist change).

    Also, if possible, I'd change the base CDF if you can, because otherwise it will get lost if somebody does a File->Refresh in the CIW (you're only changing the user CDF in your code).

    bsource_opParam.zip

    Kind Regards,

    Andrew.

Reply

  • I didn't see your last post until after I'd put together a small example, which is using precisely the code you provided (I thought it looked OK, I just wanted to check). So in the attached (assuming I can get it to upload), there's a library "mytechlib" with a testbench inside which references the "caplnmos" component (which was copied from cap in analogLib, and then the CDF changed to have a default model of caplnmos). There's an ADE state which you can load an simulate and then annotate the DC operating point.

    If you load "forum.il" (your code) and then do a Simulation->Netlist->Recreate, it should then work. The reason it probably didn't work for you was that you didn't force the netlist to be recreated. The opParamExprList info gets stored in the mapping directories when you netlist, and so if the CDF was changed after netlisting, it won't have an impact unless netlisting is done again (and if nothing changed in the schematic, you'll have to force a netlist change).

    Also, if possible, I'd change the base CDF if you can, because otherwise it will get lost if somebody does a File->Refresh in the CIW (you're only changing the user CDF in your code).

    bsource_opParam.zip

    Kind Regards,

    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.