Andrew Beckett
Senior Fellow
Offline
Life, don't talk to me about Life...
Posts: 1742
Bracknell, UK
|
If you're only changing included files (and not editing them via the ADE GUI), then that's not really anything to do with the fact that the netlister is incremental. There are two parts to the simulator input creation:
1. The netlist itself (which is netlisted from the design hierarchy) 2. The control statements etc which are added around this (inclusion of model files, parameters, analyses, outputs to save and so on).
Both of these should be triggered by a change in the source data for these parts (there have been bugs in the past, but I'm not aware of any outstanding problems).
The second issue is that spectre itself is normally run (in ADE or OCEAN) in what is called "interactive" mode - this means that the simulator does not exit at the end, and if a change in a design variable is made, it can do so in memory and quickly re-simulate without needing the simulator to start up, check out licenses, and parse the netlist. Bigger changes (resulting in a new netlist, or a new analysis, say) ADE will tell spectre to exit and re-read the new input.scs. If you just edit (in UNIX) one of the model files (say), spectre or ADE have no idea that it has changed, and consequently the simulation will be re-done with the same netlist.
Actually it's not necessary in that scenario to do a check-and-save, or a force renetlist. Just do Simulation->Stop and then the next time around spectre will definitely start again.
Your problem may be something else though - you didn't say what version you're using (type getVersion(t) in the CIW. or do Help->About) - maybe you have an older version that has a bug - maybe you should contact Cadence Customer Support if you're using something recent and this is still happening?
Regards,
Andrew.
|