12.07.2015 Views

Configuration Handbook - Kamami.pl

Configuration Handbook - Kamami.pl

Configuration Handbook - Kamami.pl

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Passive Parallel Asynchronous <strong>Configuration</strong>To ensure DATA0 is not left floating at the end of configuration, themicroprocessor must take care to drive them either high or low,whichever is convenient on your board. After configuration, the nCS, CS,nRS, nWS, RDYnBSY, and DATA[7..1] pins can be used as user I/O pins.When the PPA scheme is chosen in the Quartus II software, as a defaultthese I/O pins are tri-stated in user mode and should be driven by themicroprocessor. To change this default option in the Quartus II software,select the Dual-Purpose Pins tab of the Device & Pin Options dialog box.If an error occurs during configuration, the FPGA drives its nSTATUS pinlow, resetting itself internally. The low signal on the nSTATUS pin alsoalerts the microprocessor that there is an error. If the Auto-Restart<strong>Configuration</strong> After Error option-available in the Quartus II software fromthe General tab of the Device & Pin Options dialog box-is turned on, theFPGA releases nSTATUS after a reset time-out period (maximum of40 µs). After nSTATUS is released and pulled high by a pull-up resistor,the microprocessor can try to reconfigure the target device withoutneeding to pulse nCONFIG low. If this option is turned off, themicroprocessor must generate a low-to-high transition (with a low pulseof at least 8 µs) on nCONFIG to restart the configuration process.The microprocessor can also monitor the CONF_DONE and INIT_DONEpins to ensure successful configuration. The CONF_DONE pin must bemonitored by the microprocessor to detect errors and determine whenprogramming com<strong>pl</strong>etes. If the microprocessor sends all configurationdata but CONF_DONE or INIT_DONE has not gone high, themicroprocessor must reconfigure the target device.1 If the optional CLKUSR pin is being used and nCONFIG is pulledlow to restart configuration during device initialization, youneed to ensure CLKUSR continues toggling during the timenSTATUS is low (maximum of 40 µs).When the FPGA is in user-mode, a reconfiguration can be initiated bytransitioning the nCONFIG pin low-to-high. The nCONFIG pin should below for at least 8 µs. When nCONFIG is pulled low, the FPGA also pullsnSTATUS and CONF_DONE low and all I/O pins are tri-stated. OncenCONFIG returns to a logic high state and nSTATUS is released by theFPGA, reconfiguration begins.Figure 7–21 shows how to configure multi<strong>pl</strong>e APEX 20KE andAPEX 20KC devices using a microprocessor. This circuit is similar to thePPA configuration circuit for a single device, except the devices arecascaded for multi-device configuration.7–46 Altera Corporation<strong>Configuration</strong> <strong>Handbook</strong>, Volume 1 August 2005

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!