English
Language : 

HC4GX15 Datasheet, PDF (192/668 Pages) Altera Corporation – HardCopy IV Device Handbook
1–24
Chapter 1: HardCopy IV Design Flow Using the Quartus II Software
Engineering Change Order (ECO)
ECOs can be categorized in two ways for HardCopy development:
■ Migrating one-to-one changes
■ Migrating changes that must be implemented differently
Migrating One-to-One Changes
Some examples of migrating one-to-one changes are changes such as creating,
deleting, or moving pins, changing pin or PLL properties, or changing pin
connectivity (provided the source and destination of the connectivity changes are
I/Os or PLLs).
To duplicate the same ECO in the Quartus II software, use the Change Manager and
record all ECOs for the FPGA revision. Ensure that the same ECO operations occur on
each revision for both the Stratix FPGA and HardCopy ASIC revisions to avoid a
revision comparison failure.
To generate a .tcl script of the ECO operations in the Stratix FPGA revision and apply
it to the HardCopy revision, follow these steps:
1. In the Stratix FPGA revision, open Change Manager.
2. On the View menu, click Utility Windows and select Change Manager.
3. Perform the ECO in the Chip Planner or Resource Property Editor. You will see
the ECO operations in the Change Manager.
f For the information about ECO operations in the Stratix FPGA revision, refer to the
Engineering Change Management with the Chip Planner chapter in volume 2 of the
Quartus II HandBook.
4. Export the ECO operations from the Change Manager to Tcl Script. On the
Change Manager, right mouse click the entry. Click Export, and then click Export
All Changes AS…
5. Save the .tcl script, to be used in the HardCopy revision.
In the HardCopy revision, apply the .tcl script to the companion revision using the
following procedure.
1. Open the generated .tcl script from the Quartus II software or a text editor tool.
Edit the line project_open <project> - revision <revision> to refer to the
appropriate companion revision. Save the .tcl script.
2. Apply the .tcl script to the companion revision. On Tools menu, scroll the Tcl
Scripts pull-down menu, and select ECO Tcl and click Run.
Migrating Changes that Must be Implemented Differently
Unlike migrating changes one-to-one, some changes must be implemented on the
Stratix FPGA and HardCopy ASIC revisions differently. Changes affecting the logic
of the design can fall into this category. Examples of these are LUTMASK changes,
LC_COMB/HSADDER creation and deletion, and connectivity changes not covered
in the previous section.
HardCopy IV Device Handbook, Volume 2
© January 2010 Altera Corporation