HC210 datasheet(115/228 Pages) ALTERA

115 / 228 page

Altera Corporation

5–23

September 2008

Overall Migration Flow

If testing identifies problems requiring ECO changes, equivalent changes

can be applied to both Stratix II and HardCopy II revisions, as described

in the next section.

Applying ECO Changes

The general flow for applying equivalent changes in companion revisions

is as follows:

Make changes in one revision using the Chip Planner tools (Chip

Planner, Resource Property Editor, and Change Manager), then

verify and export these changes. The procedure for doing this is as

follows:

Make changes using the Chip Planner tool.

Perform a netlist check using the Check and Save All Netlist

Changes command.

Verify correctness using timing analysis, simulation, and

prototyping (Stratix II only). If more changes are required,

repeat steps a-b.

Export change records from the Change Manager to Tcl scripts,

or .csv or .txt file formats.

This exported file is used to assist in making the equivalent

changes in the companion revision.

Open the companion revision in the Quartus II software.

Using the exported file, manually reapply the changes using the

Chip Planner tool.

As stated previously, some changes can be reapplied directly to the

companion revision (either manually or by applying the Tcl

commands), while others require some modifications.

Perform a Revision Compare operation. The revisions should now

match once again.

Verify the correctness of all changes (you may need to run timing

analysis).

Run the HardCopy II Assembler and the HardCopy II Netlist Writer

for design submission along with handoff files.

HC210 Datasheet(PDF) 115 Page - Altera Corporation