Stats

  • Locked Locked
  • Replies 7
  • Subscribers 126
  • Views 19351
  • 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

CDF simulation parameters do not update accordingly?

SUEE

Hi,

Last several weeks I mostly worked on the layout and yesterday I came back to run the simulation and found something weird.

During the last several weeks I update some instances pin name, for example I change one of the cellA pin name from "ABC" to "DEF". Yesday I run the spectre simulation and it showed a lot of warning messag because in the CDF "simulation information"/spectre the pin name is still "ABC.

 I think I never encoutered this kind of problem before, but why it happened thos time? The CDF parameters do not update accordingly?

(1) Is there any possible reason that causes this problem?

(2) What should I do to let icfb update automatically the CDF "Simulation Information" pin name, not manually? I think tens of cell pin name are changed during last several weeks so I do not want to update the CDF parameter one by one manually ....

 Thanks a lot !!

Parents

  • The point is that if you update the pins on the schematic, you're going to have to update the symbol anyway because netlisting will fail if there's a mismatch between the symbol and schematic pins. So having the CDF update based on the symbol makes sense - that's what is going to be used to control netlisting.

    Note that these are warning messages. If it detects that the termOrder information is wrong, it tells you, and discards the information and netlists using a built-in default order algorithm. It just warns you so that you know the order in the netlist is not what it was specified in the CDF, because that's wrong.

    I don't particularly want to post the whole solution here (you should be able to get access to this somehow even as a university), but you could just use:

    artGenerateHierSymbolCDF(geGetEditCellView())

    from your schematic (schematic's best, because this will ensure any pPar() expressions in your schematic also populate the parameters section in the CDF). You could even have this on a bindkey if you need to do it a lot.

    Regards,

    Andrew.

     

Reply

  • The point is that if you update the pins on the schematic, you're going to have to update the symbol anyway because netlisting will fail if there's a mismatch between the symbol and schematic pins. So having the CDF update based on the symbol makes sense - that's what is going to be used to control netlisting.

    Note that these are warning messages. If it detects that the termOrder information is wrong, it tells you, and discards the information and netlists using a built-in default order algorithm. It just warns you so that you know the order in the netlist is not what it was specified in the CDF, because that's wrong.

    I don't particularly want to post the whole solution here (you should be able to get access to this somehow even as a university), but you could just use:

    artGenerateHierSymbolCDF(geGetEditCellView())

    from your schematic (schematic's best, because this will ensure any pPar() expressions in your schematic also populate the parameters section in the CDF). You could even have this on a bindkey if you need to do it a lot.

    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.