HC230F1020 Altera, HC230F1020 Datasheet - Page 114

• Manufacturer Part Number: HC230F1020
• Manufacturer: Altera

Specifications of HC230F1020

• Lead Free Status / RoHS Status: Not Compliant

HardCopy Series Handbook, Volume 1
Overall
Migration Flow
5–22
Changes that Cannot be Migrated
A small set of changes cannot be implemented in the other architecture
because they do not make sense in the other architecture. The best
example of this occurs when moving logic in a design; because the logic
fabric is different between the two architectures, locations in Stratix II
make no sense in HardCopy II and vice versa.
This section outlines the migration flow and the suggested procedure for
implementing changes in both revisions to ensure a successful Revision
Compare such that the design can be submitted to the HardCopy Design
Center.
Preparing the Revisions
The general procedure for migrating changes between devices is the
same, whether going from Stratix II to HardCopy II or vice versa. The
major steps are as follows:
1.
2.
3.
4.
Make/Delete LC_FF
Editing Logic Connectivity
Table 5–3. Implementation Suggestions for Various Changes (Part 2 of 2)
Compile the design on the initial device.
Migrate the design from the initial device to the target device in the
companion revision.
Compile the companion revision.
Perform a Revision Compare operation. The two revisions should
pass the Revision Compare.
Change Type
The basic creation and deletion is the same on both
architectures. However, as with LC_COMB creation
and deletion, the location of an LC_FF in a
HardCopy II revision has no meaning in the
Stratix II revision and vice versa.
Because a Stratix II LCELL_COMB atom may have
to be broken up into several HardCopy II
LCELL_COMB atoms, the source or destination
ports for connectivity changes may need to be
analyzed to properly implement the change in the
companion revision.
Suggested Implementation
Altera Corporation
September 2008