Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 13940
  • 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

SPICE cellview: how to use?

ZoltanT

Hello everyone,

I've just noticed that there is a "spice" cellview from the dropdown list in the create new cellview form. By creating a spice cellview the text editor will open. Where can I find information about the intended use of this cellview type? I was not able to use the appropriate search terms in the knowledgebase, i.e. support.cadence.com. Apparently "spice cellview" was not enough.

I imagine a use-case like this: someone adds a spice model file this way. After creating a symbol and probably some termMapping, the netlister and simulator will pick up the "spice" cellview through switch view list or hierarchy editor. With other words: there is no need to add the spice model file with Setup -> Model Files, and add the "model" CDF parameter in the CDF Editor. Maybe a terminal/port check between the spice netlist and the symbol could have been implemented.

I'm using ICADV12.3.

Thanks!
Zoltan

  • Hi Zoltan,

    If you create a spice or a spectre view type, the contents of the text will be parsed and it will extract the terminals from the subckt header within the view, and then this will be used to create view-specific CDF so that it knows what order to write the terminals in when an instance of that view is going to be used. It will also prompt you to create a symbol if one doesn't exist. It will also compare the pins against the symbol if it does exist (provided you hit the File->Extract or "save" icon with the check mark over the top of it (the equivalent of check-and-save).

    You don't have to do any messing around with the CDF yourself - you simply need to select the view to use in the hierarchy editor or in the switch view list.

    So I think this does what you want already.

    Andrew.

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.