• 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 Design
  3. SpiceIn "subtype" User Property

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 1382
  • 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

SpiceIn "subtype" User Property

garobe
garobe over 9 years ago

Hi,

I found another thread with a similar problem, but it ended without a real solution (link is below), so I'm hoping to see if there have been any updates regarding it.  I have successfully created schematics from a CDL netlist, but can't get the SpiceIn tool to stop creating a User Property called "subtype."  In one particular case, it creates the "subtype" User Property and assigns a local value of "NFET."  This appears to be causing a problem in ADE as Spectre is looking for an "NFET" subtype when only an "nfet" exists.

If I could either have SpiceIn not create the subtype User Property, or change it so that the local value is not capitalized, I believe things should start working again, though I'm not certain.  I am not terribly familiar with Skill, so I'm hoping there is a solution that involves setting up SpiceIn correctly rather than hacking schematics...

Thanks,

Gideon

community.cadence.com/.../18414

  • Cancel
  • Quek
    Quek over 9 years ago

    Hi Gideon

    Would you please try adding "model cdlModel" as one of the parameters to be mapped during spiceIn? I used this to prevent spiceIn from overwriting the value of the original "model" CDF parameter from the device.


    Best regards
    Quek

    • 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