Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 2787
  • 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

*E,CUBSPA Assignment of string to real or integer type parameter

tpungi

Hello,

I have a VAMS design with the following instance:

~~~

my_subckt #( .param1("2"), .param2("2.002u"), .param3("1.928u"))

// rest of code

~~~

And a SPICE subckt as:

~~~

.subckt my_subckt node1 node2 node3 param1=0.36e-6 param2=0.36e-6 param3=1

*rest of code

~~~

The amscf.scs block I am using looks like this:

~~~
amsd {
portmap subckt=my_subckt
config cell=my_subckt use=spice

ie vsup=1.8
}

~~~

When trying to compile the design using xrun I am getting the following Error:

my_subckt #( .param1("2"), .param2("2.002u"), .param3("1.928u"))
                                      |
xmelab: *E,CUBSPA : Assignment of string to real or integer type parameter.

The my_subckt is taken directly from PDK model library. And VAMs are also generated, using the same model library.

What exactly am I missing?

  • Andrew Beckett

    It appears that they should not be strings - the parameters in the SPICE are floating point numbers, so I'm not sure why you have them set as strings on the instance line in the Verilog-AMS netlist. It should be:

    my_subckt #( .param1(2), .param2(2.002u), .param3(1.928u))

    Andrew

  • tpungi
    in reply to Andrew Beckett

    Thanks for the reply.

    These .vams are generated by Virtuoso tool itself.

    So if that means I have to write a script to remove all the unnecessary " " to make it work.

  • Andrew Beckett
    in reply to tpungi
    tpungi said:
    So if that means I have to write a script to remove all the unnecessary " " to make it work.

    No, you should not need to do this. Assuming that the netlister is stopping at this block, it suggests that the CDF for the cell is wrong and has the parameters marked as string types (probably OK) but doesn't have parseAsCEL or parseAsNumber set to yes for each of the parameters. So the CDF probably just needs fixing...

    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.