• 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. Netlist with “assign” / RC and Encounter

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 12981
  • 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

Netlist with “assign” / RC and Encounter

Yemelya
Yemelya over 14 years ago

Hello,

There is a signal which crosses a few hierarchies and changes its name each time; but eventually it goes to analog macro and intention is to avoid any buffers on this net.
Using attributes “set_donot_touch” or “set_ideal_network” on this signal prevents RC from buffering it, but the problem that is keeps “assign” statement in the netlist each time the signal changes name / hierarchy.

My questions are:
1. Could it be a problem for Encounter P&R flow (or LVS/DRC) to deal with the netlist which includes “assign”?
2. Is there an elegant way to get rid of  this “assign” and to route this net  without buffers?

Thanks a lot!
__
Boris.

  • Cancel

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