• 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 - how to map to a total width from w and m in the...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 4552
  • 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 - how to map to a total width from w and m in the CDL

WMACH
WMACH over 11 years ago

Hello,

I have used SpiceIn to import my CDL (which includes MOSFETS, diodes and resistors). I had good results except when it comes to MOSFETs. The issue is related to the fact that my MOSFET devices, in my cadence librasy, have width per finger "wf" and a calculated total width "wt", which would be taken care of by a callback whenever there is a change in "wf" or the multiplier "m".

In my device map I have a mapping from the width "w" in the CDL to the schematic in Cadence as "wf". Since "wt" is not being mapped, the callback assigns to it a default value, which is not necessarily the product of "w" x "m" from the CDL.

So, at this point in order to get the correct value of "wt" I have to query my MOSFET devices and "pretend" I'm making a change just to trigger the callback to do its job. The problem is that my schematic has hundreds of MOSFET instances and I have lots of schematics, so I manual way to do this would be really impractical.

Two questions:

1. Is there a way in SpiceIn to map to "wf" (schematic view) from "w" x "m" (CDL)? if so, how can I do that.

2. Is there a Cadence routine to make the change automatically as described above such that I can cause the callback to recalculate values? with this I could implement a routine to repeat this operation on every device in my schematic.

Any help would be greatly appreciated,

Thanks.

  • Cancel
Parents
  • skillUser
    skillUser over 11 years ago

    Hi,

    Great news! Actually Solution 11018344 is referenced in Solution 11724692 (as I'd mentioned: "and gives a reference to another solution regarding calling the callbacks"), I just didn't provide the link to it directly here.  This is probably your best option as it will run all of the device callbacks - the code I'd suggested would only change the one "wf" parameter on each device (and you'd have to write it!).

    I'm glad that things seem to be resolved.

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 11 years ago

    Hi,

    Great news! Actually Solution 11018344 is referenced in Solution 11724692 (as I'd mentioned: "and gives a reference to another solution regarding calling the callbacks"), I just didn't provide the link to it directly here.  This is probably your best option as it will run all of the device callbacks - the code I'd suggested would only change the one "wf" parameter on each device (and you'd have to write it!).

    I'm glad that things seem to be resolved.

    Best regards,

    Lawrence.

    • 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