• 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. Incorrect multiplier in Spice In

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14264
  • 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

Incorrect multiplier in Spice In

wcheong
wcheong over 6 years ago

Hi,

I used Spice In to import SPICE netlist to generate schematic in IC181 (version ICADVM18.1-64b.500.4). The technology is in tsmcN16 and library is defined in cds.lib. Schematic was generated without any error. However, it failed LVS due to the incorrect number of multiplier.

Original SPICE netlist: M_0 nn2 net122 VSS VSS nch_18_mac l=150.0n nfin=15 m=18

spiceIn.log:

    Inst: M_0
        Created net 'nn2'.
        Created net 'net122'.
        Found net 'VSS'.
        Found net 'VSS'.
        Created net 'nch_18_mac'.

        Master Cell: 'nch_18_mac'.
        Master Cellview: 'tsmcN16.nch_18_mac:symbol' found.
        Created instance 'M_0'.
        Created connection between net 'nn2' and term 'D'.
        Created connection between net 'net122' and term 'G'.
        Created connection between net 'VSS' and term 'S'.
        Created connection between net 'VSS' and term 'B'.
        Created propName='model'; propType='string'; propVal='nch_18_mac'.
        Created propName='l'; propType='string'; propVal='1.5e-07'.
        Created propName='nfin'; propType='string'; propVal='15'.
        Created propName='m'; propType='string'; propVal='18'.

LVS netlist: MM_0 nn2 net122 VSS VSS nch_18_mac l=1.5e-07 nfin=15 m=1

Is there any solution for this issue? Please let me know if there is any existing solution or discussion about this issue. Thanks.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    The most likely situation is that the the parameter is not called "m" but something else. It may be being mapped (via the propMapping) to netlist as m, but it might be called something else (e.g. multi) on the component itself. You'll need to look at the CDF definition to see what's going on. 

    I can't discuss that technology in an open forum since that would break the NDA with the foundry - so you might be better off talking to customer support if you can't figure it out yourself.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wcheong
    wcheong over 6 years ago in reply to Andrew Beckett

    I changed "m" to "multi" as defined in CDF and it works.

    Thanks, Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • wcheong
    wcheong over 6 years ago in reply to Andrew Beckett

    I changed "m" to "multi" as defined in CDF and it works.

    Thanks, Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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