Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 17359
  • 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

spectre: Parameters in .Alter Statement Not effecting Digital Vector File Stimuli

Eberhard2010

Hallo guys,

i've a common netlist (see below). It uses .ALTER (spice) statement and digital vector file input (stimuli). This is because alter or altergroup in spectre syntax does not work anyway.

 <<<<<<<<<<<<<

simulator lang=spectre
  finalTimeOP info what=oppoint where=rawfile
  modelParameter info what=models where=rawfile
  element info what=inst where=rawfile
  outputParameter info what=output where=rawfile
  designParamVals info what=parameters where=rawfile
  primitives info what=primitives where=rawfile
  subckts info what=subckts where=rawfile
  saveOptions options save=allpub

vec_include "../circuit_stimuli/Stimuli_102.vec" hlcheck=0

*Input Stimuli-File
parameters Supply_vec=5 \
            slope_vec=0.05 \
             zero_vec=0 \
              vth_vec=2.5

 *Main Netlist
X1 (vecIN1 vecIN2 QN VDD GND) NAND2X1
Cload (QN0 0) capacitor c=1e-12

GND_source (GND 0) vsource dc=0 type=dc
VDD_source (VDD 0) vsource dc=5 type=dc

*Analysis
tran0 tran stop=1us

simulator lang=spice

.ALTER myalt
  .param slope_vec=0.01
.END

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

The parameters below "Input Stimuli File" are used in the *.vec file. The first (initial ones) are working fine. Now, the alter Statement changes these design variables correctly. However it seems to have no effect on the generated stimuli for the next run. Is there a way to tell spectre to "regenerate stimuli" after design Variables are changed? Or how should I rewrite it?

I got one situation in which it runs correctly, so there is a solution out there. Now i try to reveal it again.

Thanks for your help in advance.

 Regards Eberhard

Parents
  • Andrew Beckett

    Eberhard,

    You'll need to contact customer support. I just tried this, and I don't get the crash (I'm using a newer version than you either  10.1.1.428.isr24 or 11.1.0.467.isr12) - note I changed the parameter=slope_vec to param=slope_vec (or similar) - the keyword for the sweep statement is param not parameter.

    Regardless of this, it doesn't work - the change in the parameter (either via alter or sweep) doesn't affect the vector read. I'd expect that if it worked for alter, it would also work for sweep (and also if it doesn't work for alter, it also wouldn't work for sweep).

    So you need to log a service request so that we can get this fixed.

    Kind Regards,

    Andrew.

Reply
  • Andrew Beckett

    Eberhard,

    You'll need to contact customer support. I just tried this, and I don't get the crash (I'm using a newer version than you either  10.1.1.428.isr24 or 11.1.0.467.isr12) - note I changed the parameter=slope_vec to param=slope_vec (or similar) - the keyword for the sweep statement is param not parameter.

    Regardless of this, it doesn't work - the change in the parameter (either via alter or sweep) doesn't affect the vector read. I'd expect that if it worked for alter, it would also work for sweep (and also if it doesn't work for alter, it also wouldn't work for sweep).

    So you need to log a service request so that we can get this fixed.

    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.