spectremdl and the setting of section in the include stateme

[Svenn Are Bjerkem]

Hi,

I wanted to give spectremdl a quick try to make some extencive corner
simulations. Seems that it is not possible to put a variable in place
of the actual section for section= in the include statement in the
netlist. I tried by defining a parameter called "corner" and then do
a

parameters corner="tt"

and then

include "/path/to/my/pdk/" section=corner

I wanted to use this with a paramset

design_corner paramset {
corner
"tt"
"ss"
"ff"
}

and in the mdl file:
foreach design_corner {
// do something
}

But this doesn't seem to work. This way of simulation does not seem to
be covered by the mdl documentation.
Solutions anybody?

--
Svenn

 

[Andrew Beckett]

On Thu, 26 Jul 2007 09:32:23 -0000, Svenn Are Bjerkem
<svenn.bjerkem@googlemail.com> wrote:

Hi,

I wanted to give spectremdl a quick try to make some extencive corner
simulations. Seems that it is not possible to put a variable in place
of the actual section for section= in the include statement in the
netlist. I tried by defining a parameter called "corner" and then do
a

parameters corner="tt"

and then

include "/path/to/my/pdk/" section=corner

I wanted to use this with a paramset

design_corner paramset {
corner
"tt"
"ss"
"ff"
}

and in the mdl file:
foreach design_corner {
// do something
}

But this doesn't seem to work. This way of simulation does not seem to
be covered by the mdl documentation.
Solutions anybody?

I filed a PCR some time ago to ask for the section name to be parameterizable -
don't have the number handy, but I suggest you file a service request with
Cadence and ask for a duplicate to be created. If more customers ask for this,
it's more likely to get done.

You can do it with OCEAN, but not with a spectre sweep, or with mdl, as far as I
know (because it can't be parameterized). You can do it with altergroups in
spectre, but a sweep would be more convenient.

Regards,

Andrew.
--
Andrew Beckett
Senior Solution Architect
Cadence Design Systems, UK.