Stats

Locked Locked
Replies 2
Subscribers 91
Views 1321
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

ENCOUNTER ECO - module

checkerbum2 over 13 years ago

Hi,

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)

Andy

Scrivner over 13 years ago

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

Cancel
checkerbum2 over 13 years ago

Thanks,
andy
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.