HC230F1020 Altera, HC230F1020 Datasheet - Page 113

• Manufacturer Part Number: HC230F1020
• Manufacturer: Altera

Specifications of HC230F1020

• Lead Free Status / RoHS Status: Not Compliant

Altera Corporation
September 2008
f
A partial list of examples of this type are as follows:
■
■
■
■
Migrating Changes that must be Implemented Differently
Some changes must be implemented differently on the two architectures.
Changes affecting the logic of the design may fall into this category.
Examples are LUTMASK changes, LC_COMB/HSADDER creation and
deletion, and connectivity changes not covered in the previous section.
Another example of this would be to have different PLL settings for the
Stratix II and the HardCopy II revisions.
For more information about how to use different PLL settings for the
Stratix II and HardCopy II Devices, refer to AN432: Using Different PLL
Settings Between Stratix II and HardCopy II Devices.
Table 5–3
LUTMASK changes
Make/Delete LC_COMB
Table 5–3. Implementation Suggestions for Various Changes (Part 1 of 2)
I/O creation, deletion, and moves
I/O property changes (for example, I/O standards, delay chain
settings, etc.)
PLL property changes
Connectivity changes between non-LCELL_COMB atoms (for
example, PLL to I/O, DSP to I/O, etc.)
Change Type
summarizes suggested implementation for various changes.
Performing ECOs with Change Manager and Chip Planner
Because a single Stratix II atom may require
multiple HardCopy II atoms to implement, it may be
necessary to change multiple HardCopy II atoms to
implement the change, including adding or
modifying connectivity
If you are using a Stratix II LC_COMB in extended
mode (7-LUT) or using a SHARE chain, you must
create multiple atoms to implement the same logic
functions in HardCopy II. Additionally, the
placement of the LC_COMB cell has no meaning in
the companion revision as the underlying
resources are different.
Suggested Implementation
5–21