Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13582
  • 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

How to make AMS Netlister evaluate pcells

Marode

Hi,

I have built a schematic pcell which instantiates different cells according to a parameter. The AMS Netlister does not generate and include different instances per parameter-set in the netlist.

If the generated pcell is placed several times with different parameters in a testbench, the normal spectre netlist adds one subckt per different parameter set (named something like ...pcell0 ...pcell1 etc.) with the correct instances in it.  For example if one instance has a parameter x=1 and one x=0 it will generate a cellName_pcell0 and a cellName_pcell1 subcircuit. 

In the AMS netlist the different CDF parameters can be seen(they are passed to the instance), but nevertheless only one and the same instance is there.

It seems like the pcells are not evaluated. Even though the different and correct instances can be seen in the hierarchy editor

I would be glad for any idea, hint or maybe solution.

Thanks.

  • This should work if you use the OSS netlister, rather than the Cell-Based netlister (in ADE).

    Regards,

    Andrew.

  •  Hi Andrew,

    thank you very much for your reply (I wonder why you know that, couldn't find a lot of documentation about it).

    Although I "hardcoded" the cells in the meantime, I went back to test if the OSS netlister can do the trick and it seems he does. I am used to use the AMS plugin in the hierarchy editor, were you can't use the OSS netlister. Probably I should change that habit, since there is no reason to use it.?

    Thanks again, regards,

    Joerg

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.