• 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. Logic Design
  3. high fanout nets synthesis

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 61
  • Views 15689
  • 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

high fanout nets synthesis

archive
archive over 19 years ago

Is Encounter able to synthesis and add buffer tree to high fanout nets such as "reset"?
If so, how to do it? Should it be done before or after CTS?
Thanks!


Originally posted in cdnusers.org by yx228
  • Cancel
Parents
  • archive
    archive over 19 years ago

    Hi,

    I believe it is not mandatory to have the hign fanout net being preserve during synthesis as long as you know they are high fanout nets and will remove the synthesis buffer tree in Encounter prior to creating a new one.

    However I agree with crispy duck and recognize that it is good practice to protect those nets during synthesis as it will make the job easier in the backend especially if the list of such nets is not provided.

    Eric.


    Originally posted in cdnusers.org by evenditti
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 19 years ago

    Hi,

    I believe it is not mandatory to have the hign fanout net being preserve during synthesis as long as you know they are high fanout nets and will remove the synthesis buffer tree in Encounter prior to creating a new one.

    However I agree with crispy duck and recognize that it is good practice to protect those nets during synthesis as it will make the job easier in the backend especially if the list of such nets is not provided.

    Eric.


    Originally posted in cdnusers.org by evenditti
    • 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