• 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. PCB Design
  3. Modeling and Simulating Line-Interface IOs of Communications...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 164
  • Views 12774
  • Members are here 0
More Content
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

Modeling and Simulating Line-Interface IOs of Communications Chips

archive
archive over 18 years ago

I have encountered a consistent practice by most vendors telecommunications chip vendors. They do not provide IBIS models for the line-interface IOs of their chips (e.g. Ethernet, E1/T1, etc.). These IOs are usually left non-connected (NC) in the IBISDevice models. 

However, these IOs must still be modeled and simulated to develop an understanding of the constraints governing its proper operation.

Please let me know how such IOs can be modeled and simulated, or provide any information that may be of help in this situation.


Originally posted in cdnusers.org by anassar
  • Cancel
Parents
  • archive
    archive over 18 years ago

    When you work at a semiconductor company, how (even IF) IBIS models are constructed is largely a function of customer demand. If/when there's something you need in an IBIS model, you need to make that request to the IC manufacturer. If you work at a large company that buys lots of volume, the IC vendor will work quickly to satisfy your request - particularly if you make your request through your purchasing department. (They control the contracts on what needs to be delivered, and how and when. Adding delivery of a certain type of IBIS model can be included in this.)

    If you work at a smaller company that isn't buying a significant volume, I'd still encourage you to make your request. They may not act on it as fast, but when a number of similar requests come in they eventually get the message.

    That said, a successful SI engineer can't always wait on getting the model from a semi vendor. Be ready to make educated assumptions and approximations. Some data is better than none. Download the macromodel templates available at this site, and learn how to use them. Many IC vendors are not yet skilled at making good differential driver models, even thinking they can't be done in PCB simulators. But that isn't so, and there's a ton of info at cdnusers about how to model them. Many SI engineers don't care for making models, but it's part of the job.

    So work both paths in parallel: (1) make requests of the IC vendor, and (2) learn to make your own models. I did both things on a recent project, and the vendor's model arrived the day I finished the project. When I compared their model with mine, I actually liked mine better. (I didn't feel they did a good job of spanning min/typ/max. I suspect they were new at making models.) However, comparing the models further helped to confirm that my assumptions were correct. IO drivers are not a mystery and, with the exception of Gbit Rx EQ, the majority of IC vendors solutions are quite the same.

    Hope that helps,
    Donald


    Originally posted in cdnusers.org by Donald Telian
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    When you work at a semiconductor company, how (even IF) IBIS models are constructed is largely a function of customer demand. If/when there's something you need in an IBIS model, you need to make that request to the IC manufacturer. If you work at a large company that buys lots of volume, the IC vendor will work quickly to satisfy your request - particularly if you make your request through your purchasing department. (They control the contracts on what needs to be delivered, and how and when. Adding delivery of a certain type of IBIS model can be included in this.)

    If you work at a smaller company that isn't buying a significant volume, I'd still encourage you to make your request. They may not act on it as fast, but when a number of similar requests come in they eventually get the message.

    That said, a successful SI engineer can't always wait on getting the model from a semi vendor. Be ready to make educated assumptions and approximations. Some data is better than none. Download the macromodel templates available at this site, and learn how to use them. Many IC vendors are not yet skilled at making good differential driver models, even thinking they can't be done in PCB simulators. But that isn't so, and there's a ton of info at cdnusers about how to model them. Many SI engineers don't care for making models, but it's part of the job.

    So work both paths in parallel: (1) make requests of the IC vendor, and (2) learn to make your own models. I did both things on a recent project, and the vendor's model arrived the day I finished the project. When I compared their model with mine, I actually liked mine better. (I didn't feel they did a good job of spanning min/typ/max. I suspect they were new at making models.) However, comparing the models further helped to confirm that my assumptions were correct. IO drivers are not a mystery and, with the exception of Gbit Rx EQ, the majority of IC vendors solutions are quite the same.

    Hope that helps,
    Donald


    Originally posted in cdnusers.org by Donald Telian
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data
Cadence Guidelines

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