• 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. Conformal ECO Flow Basic Question

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 63
  • Views 15704
  • 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

Conformal ECO Flow Basic Question

moogyd
moogyd over 13 years ago

Hi,

I think that understand the basic flow, but these is one issue that causes issues.

 I have the current post layout netlist G1 - this is "golden"

I generate a new netlist using RTL compler G2 - this is "revised".

I can compare G1 and G2 and generate patch files using conformal ECO.

There is one major issue, and it is not clear how to handle. G1 contains clock, buffer and additional scan ports, which means that there are additional ports on the module of interest.When I look at the generated netlist (G3), non of these extra ports are used.e.g. The clock is not taken from the clock tree port, but from the origincal (pre P&R) clock net.

I have been looking at the ignore input/output command, but these don't seem to make any difference.

Am I overlooking some obvious switch on one of the commands?

 Thanks,

Steven

 

  • Cancel
  • hummingbird
    hummingbird over 13 years ago

     Hi Steven,

     Here's what I typically do:

    1. To preserve clock logic, use "analyze eco ... -preserve_clock"

    2. To preserve the scan logic, use "add pin constraint 0 scan_en -golden".  

    Conformal ECO automatically handles additional ports (i.e. scan, duplicated clk/set/reset, feedthrough...etc pins) in the layout netlist, even for the port inversion cases.  If you've not used FEF (flat eco flow) yet, I'd recommend to use FEF which is an improvement over the hierarchical ECO flow.

     Hope this helps.

    Regards,
    Vince
     

    • Cancel
    • Vote Up 0 Vote Down
    • 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