Configuration Handbook - Kamami.pl

Configuring Mercury, APEX 20K (2.5 V), ACEX 1K & FLEX 10K DevicesYou can use a single configuration chain to configure Mercury, APEX 20K,ACEX, and FLEX 10KE devices with other Altera devices that supportPPA configuration, such as Stratix ® or APEX II devices. To ensure that alldevices in the chain complete configuration at the same time or that anerror flagged by one device initiates reconfiguration in all devices, all ofthe device CONF_DONE and nSTATUS pins must be tied together.fFor more information on configuring multiple Altera devices in the sameconfiguration chain, refer to Configuring Mixed Altera FPGA Chainschapter 8 of volume 2 in the Configuration Handbook.Figure 8–23 shows the timing waveform for the PPA configurationscheme using a microprocessor.Figure 8–23. PPA Configuration Timing Waveformt CFGt STATUSnCONFIGnSTATUS (1)CONF_DONE (2)DATA[7..0]t CF2ST1t DSUt CSSUt CSHt CD2UMByte 0 Byte 1Byte n 1Byte n(4)(3) CS(3) nCSnWSRDYnBSY(4)t t CF2WSDH(4)t WSP(4)t RDY2WS(4)t WS2Bt BUSYt CF2ST0t CF2CDUser I/OsHigh-ZHigh-ZUser-ModeINIT_DONENotes to Figure 8–23:(1) Upon power-up, the Mercury, APEX 20K, ACEX 1K, or FLEX 10K device holds nSTATUS low for not more than 5 μsafter V CC reaches its minimum requirement.(2) Upon power-up, before and during configuration, CONF_DONE is low.(3) The user can toggle nCS or CS during configuration if the design meets the specification for t CSSU , t WSP , and t CSH .(4) DATA0 should not be left floating after configuration. It should be driven high or low, whichever is more convenient.DATA[7..1], CS, nCS, nWS, nRS and RDYnBSY are available as user I/O pins after configuration and the state oftheses pins depends on the dual-purpose pin settings.Figure 8–24 shows the timing waveform for the PPA configurationscheme when using a strobed nRS and nWS signal.Altera Corporation 8–53August 2005 Configuration Handbook, Volume 1