• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. *Error* almGetParameterList: argument #1 should be a string...

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 149
  • Views 12418
  • 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

*Error* almGetParameterList: argument #1 should be a string (type template = "ttggg") - nil

Danielrayray
Danielrayray over 4 years ago

Hi all,

While I try to run the simulation, virtuoso window appears below error messages(black box).

I have checked all the schematic parameters, they looks fine though.

Can somebody help me to figure out what is going on.

Error message:

Thanks in advance.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    I've not seen any reports of this error in general, so I suspect it's something to do with a custom netlisting procedure or something in your environment. This is best handled via customer support, but as a first step, perhaps you can do:

    _stacktrace=40

    and see if it provides more detail when the errors occur. If not, try also setting:

    sstatus(errsetTrace t)

    and trying again. It may give more fo a clue from where this is breaking.

    Thanks,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Danielrayray
    Danielrayray over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your kind reply.

    Do you mean these two code typed in the virtuoso CIW command line?

    Appreciate so much

    Daniel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Danielrayray
    Danielrayray said:
    Do you mean these two code typed in the virtuoso CIW command line?

    Yes.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Danielrayray
    Danielrayray over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

    I will try it at my working day.

    Since it seems that our license provider has some problems regards to IC6.

    Thanks for your kind support again.

    Sincerely

    Daniel 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Danielrayray
    Danielrayray over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

    I try to type these two command in the CIW and run it again.

    And the CIW pops up the following errors. But I have no idea what this is.

    Can you give me your suggestions?

    Many thanks.

    Sincerely

    Daniel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Danielrayray

    Hi Daniel,

    OK, that looks like a bug in the netlist procedure for one of the devices in your PDK (SpectreMOSNetlistPro is not a Cadence function). Probably you need to contact the foundry. Which foundry/process/PDK (and PDK version number) are you using?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Danielrayray
    Danielrayray over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

    I use the pseudo PDK from our country national lab (TSRI in Taiwan).

    I will pop up the issue to them.

    Thanks for your kind support.

    If solve, I will update it.

    Sincerely

    Daniel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Danielrayray

    Daniel,

    I wouldn’t be expecting a custom netlist procedure to be calling almGetParameterList, so something is definitely a bit unusual in the implementation. 

    Hope they can resolve it once you’ve reported it!

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Danielrayray
    Danielrayray over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

    So, you mean that it may go something wrong with the model file or the .tf file?

    Since I tried to switch back the old version, it is perfectly okay.

    Thanks for your kindly reply again!

    Sincerely

    Daniel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Danielrayray

    Hi Daniel,

    It's not the model files or ".tf" file that's the issue here. The PDK has declared in the CDF (in the simulation information for one fo the MOS devices, presumably) that they are using a custom netlist procedure, SpectreMOSNetlistPro, and that function is defined somewhere - probably in a SKILL file (either normal or encrypted) or a SKILL context file (.cxt) that is loaded when the PDK is used (maybe via the libInit.il file in the technology library or library containing this MOS device). That function is calling almGetParameterList - and the failure is happening because of that (I don't know what that code is doing, or why they think they need to call almGetParameterList).

    Are you saying that if you switch back to the old version of the PDK, it's OK? If so, presumably something changed between the two implementations; either they didn't have a custom netlist procedure, or the implementation of that procedure changed.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information