
Altera Corporation
23
Configuration Devices for SRAM-Based LUT Devices Data Sheet
Power &
Operation
This section describes Power-On Reset (POR) delay, error detection, and
3.3-V and 5.0-V operation of Altera configuration devices.
Power-On Reset
During initial power-up, a POR delay occurs to permit voltage levels to
stabilize. When configuring an APEX II, APEX 20K, Mercury, ACEX 1K,
FLEX 10K, or FLEX 6000 device with an EPC4, EPC8, EPC16, EPC2, EPC1,
or EPC1441 device, the POR delay occurs inside the configuration device,
and the POR delay is a maximum of 200 ms. When configuring a
FLEX 8000 device with an EPC1213, EPC1064, or EPC1064V device, the
POR delay occurs inside the FLEX 8000 device, and the POR delay is
typically 100 ms, with a maximum of 200 ms.
Error Detection Circuitry
The EPC4, EPC8, EPC16, EPC2, EPC1, and EPC1441 configuration devices
have built-in error detection circuitry for configuring APEX II, APEX 20K,
Mercury, ACEX 1K, FLEX 10K, or FLEX 6000 devices only.
Built-in error-detection circuitry uses the
nCS
pin of the configuration
device, which monitors the
CONF_DONE
pin on the APEX II, APEX 20K,
Mercury, ACEX 1K, FLEX 10K, or FLEX 6000 device. An error condition
occurs if the
CONF_DONE
pin does not go high after all the configuration
data has been sent, or if the
CONF_DONE
pin goes high before the
configuration device has completed sending configuration data. When an
error condition occurs, the configuration device drives its
OE
pin low,
which drives the APEX II, APEX 20K, Mercury, ACEX 1K, FLEX 10K, or
FLEX 6000 device’s
nSTATUS
pin low, indicating an error. After an error,
configuration automatically restarts if the
Auto-Restart Configuration on
Frame Error
option is turned on in the
Global Project Device Options
dialog box (Assign menu) in the MAX+PLUS II software. For APEX 20K,
APEX II, and Mercury devices, the Quartus II software provides a similar
option.
In addition, if the APEX II, APEX 20K, Mercury, ACEX 1K, FLEX 10K, or
FLEX 6000 device detects a cyclic redundancy code (CRC) error in the
received data, it may also flag the error by driving
nSTATUS
low. This low
signal on
nSTATUS
resets the configuration device, allowing
reconfiguration. CRC checking is performed when configuring all
APEX II, APEX 20K, Mercury, ACEX 1K, FLEX 10K, or FLEX 6000
devices.