HC210 datasheet(112/228 Pages) ALTERA

112 / 228 page

5–20

Altera Corporation

September 2008

HardCopy Series Handbook, Volume 1

With the Altera® Chip Planner tool, you can shorten the design cycle time

significantly. When changes are made to your design as ECOs, you do not

have to perform a full compilation in the Quartus II software. Instead,

you would make changes directly to the post place-and-route netlist,

generate a new programming file, test the revised design by performing

a gate-level simulation and timing analysis, and proceed to verify the fix

on the system (if you are using a Stratix II FPGA as a prototype). Once the

fix has been verified on the Stratix II FPGA, switch to the HardCopy II

revision, apply the same ECOs, run the timing analyzer and assembler,

perform a revision compare and then run the HardCopy II Netlist Writer

for design submission.

There are three scenarios from a migration point of view:

■

There are changes which can map one-to-one (that is, the same

change can be implemented on each architecture—Stratix II FPGA

and HardCopy II).

■

There are changes that must be implemented differently on the two

architectures to achieve the same result.

■

There are some changes that cannot be implemented on both

architectures.

The following sections outline the methods for migrating each of these

types of changes.

Migrating One-to-One Changes

One-to-one changes are implemented using identical commands in both

architectures. In general, such changes include those that affect only I/O

cells or PLL cells. Some examples of 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). These can be implemented

identically on both architectures.

If such changes are exported to Tcl, a direct reapplication of the generated

Tcl script (with a minor text edit) on the companion revision should

implement the appropriate changes as follows:

■

Export the changes from the Change Manager to Tcl.

■

Open the generated Tcl script, change the line "project_open

<project> -revision <revision>" to refer to the appropriate companion

revision.

■

Apply the Tcl script to the companion revision.

HC210 Datasheet(PDF) 112 Page - Altera Corporation

HC210 Datasheet(HTML) 112 Page - Altera Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL