Home > Community > Forums > Digital Implementation > ENCOUNTER ECO - module


* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 ENCOUNTER ECO - module 

Last post Tue, Jun 26 2012 1:16 PM by checkerbum2. 2 replies.
Started by checkerbum2 26 Jun 2012 11:52 AM. Topic has 2 replies and 1434 views
Page 1 of 1 (3 items)
Sort Posts:
  • Tue, Jun 26 2012 11:52 AM

    ENCOUNTER ECO - module Reply


    we use encounter to implement most of our ECO's.

    However, we have an ECO which requires too many gates. 

    We have heard that some people rip out a module,

    and have the tool replace the module with the new netlist.


    The question is what is the procedure to do that?

    It is easy enough to locate the module in the netlist -

    but beyound that - how do we ensure that all the gates are declared as "free" or spares.

    then how do we place the new netlist in its place?  (ps, i am not a backend guy - but this is my requirement)


    • Post Points: 20
  • Tue, Jun 26 2012 12:28 PM

    • Scrivner
    • Top 100 Contributor
    • Joined on Thu, Oct 9 2008
    • Ridgeland, MS
    • Posts 75
    • Points 1,475
    Re: ENCOUNTER ECO - module Reply

    In your ECO verilog netlist, just remove the module you want to get rid of from the netlist. When you import the ECO netlist and the old DEF into Encounter it will recognize that the gates in that module are no longer needed and mark them as spares. They can then be used for any newly added logic.


    For more detail on how to perform ECOs, see Chapter 42 - ECO Flows in the Encounter Digital Implementation System User Guide.

    • Post Points: 5
  • Tue, Jun 26 2012 1:16 PM

    Re: ENCOUNTER ECO - module Reply
    • Post Points: 5
Page 1 of 1 (3 items)
Sort Posts:
Started by checkerbum2 at 26 Jun 2012 11:52 AM. Topic has 2 replies.