• 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. Digital Implementation
  3. Signal Integrity analysis in SOC Encounter

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 13946
  • 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

Signal Integrity analysis in SOC Encounter

trav1s
trav1s over 14 years ago

Hello Cadence community.

Our foundry provides a 150nm process, and our designs are not high-speed by any means. They have not provided a noise library for use with SOC Encounter v9.12 (.cdb or .udn). I have tried to create a cdb file using the make_cdb utility, but there seems to be a major version problem with our spice model file, so I have not had any success with that.

I would like some advice as to what I should do. I know noise analysis plays a bigger role the smaller the process geometry is, but should noise be a concern in 150nm? Our foundry has provided other data files for the Cadence flow, so is the fact that they omitted a noise library a sign that it is not necessary? Is the Liberty timing library (.lib) enough?

  • Cancel
Parents
  • Kari
    Kari over 13 years ago

     We never worried about SI at 130nm and above, but it did come back to haunt us in one 130nm project. I would say at 150nm you don't need to worry about it too much. Set the nanoroute variables for avoiding SI just to be safe; it will make sure you don't have too many long parallel routes.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 13 years ago

     We never worried about SI at 130nm and above, but it did come back to haunt us in one 130nm project. I would say at 150nm you don't need to worry about it too much. Set the nanoroute variables for avoiding SI just to be safe; it will make sure you don't have too many long parallel routes.

    • 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