| 1. |
Can Altera guarantee
that the timing of a HardCopy device is the
same as that of a PLD? |
| 2. |
Can Altera provide
extraction timing data after HardCopy placement
and routing? |
| 3. |
Sometimes it is
very difficult to have a fully synchronous design.
There can be some asynchronous paths, such as
in a multi-clock domain design, where a path
goes from one clock to another. Can you still
guarantee timing in this situation? |
| 4. |
What happens if
design rules are not followed? |
| 5. |
What happens if
the customer's system tries to configure the
HardCopy device? |
| 6. |
Will minimum timing
in HardCopy devices be supported (required for
I/O issues with tSU and tCO)? |
| 7. |
What is the ICCSTANDBY
current in a HardCopy device? |
| 8. |
Will there be any
difference in the I/O timing between the PLD
and the HardCopy device? |
| 9. |
Will Altera be able
to guarantee minimum timing? |
| 10. |
Can the SignalTap
logic analysis be left instantiated so that
a design does not have to be recompiled? |
| 11. |
Does the HardCopy
device contain the same test circuits as the
PLD? |
| 12. |
How does the HardCopy
clock skew compare to that of the Altera high-density
devices? |
| 13. |
Are there any additional
I/Os in HardCopy devices for testing? |
| 14. |
How do you maintain
the pin placement to the original PLD? |
| 15. |
For a boundary scan,
what happens to all the unused I/O pins in a
HardCopy device? |
| 16. |
Will the customer
have to generate board-level test vectors due
to the changes in the HardCopy boundary-scan
chain ordering? |