• 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. Any way to keep all netlist modification from IPO/CTS to...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 1125
  • 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

Any way to keep all netlist modification from IPO/CTS to lower levels?

Tongju
Tongju over 16 years ago

I am working on implementing a block using FE. Usually, after I finally achieve timing-closure, I will dump/save verilog netlist and verilog-In the netlist into Cadence dfII to create new schematic for the block, which will reflect the netlist changes from IPO/CTS.  However, at this time, front-end team has a customized top level schematic: lower level symbols are located in proper places; all the wire connections are hand-drawn and clearly labeled...   They love it so much and don't like to lose it. So, they asked me whether or not it is possible to tell FE only put changes to lower level modules duing CTS/IPO and keep top level untouch even during IPO/CTS, then, we only need to verilog-in the lower level module into dfII and top level schematic that they love will survive.

 Any body has tried the similar or have a good idea to achieve this?

 Thanks,

 Tongju

  • Cancel
Parents
  • Tongju
    Tongju over 16 years ago

    Hi Bob,

     Thank you very much for your advice. Since there are so many sub-modules in  this block, partitioning the block may be too much for me to do although it may be a very good idea in other situations.  I will try the "dont_touch" on the top-level nets and see how far I can go.

     Tongju

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Tongju
    Tongju over 16 years ago

    Hi Bob,

     Thank you very much for your advice. Since there are so many sub-modules in  this block, partitioning the block may be too much for me to do although it may be a very good idea in other situations.  I will try the "dont_touch" on the top-level nets and see how far I can go.

     Tongju

    • 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