12.07.2015 Views

Configuration Handbook - Kamami.pl

Configuration Handbook - Kamami.pl

Configuration Handbook - Kamami.pl

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Fast Passive Parallel <strong>Configuration</strong>Figure 11–4. Multi-Device FPP <strong>Configuration</strong> Using an External HostMemoryADDR DATA[7..0]V CC (1) V CC (1)10 kΩ 10 kΩStratix III Device 1 Stratix III Device 2MSEL[2..0]MSEL[2..0]CONF_DONEnSTATUSnCEGNDCONF_DONEnSTATUSnCEGNDExternal Host(MAX II Device orMicroprocessor)GNDDATA[7..0]nCONFIGnCEODATA[7..0]nCONFIGDCLKnCEON.C.DCLKNote to Figure 11–4:(1) You should connect the pull-up resistor to a sup<strong>pl</strong>y that provides an acceptable input signal for all devices in thechain. V CC should be high enough to meet the V IH specification of the I/O standard on the device and the externalhost.In a multi-device FPP configuration, the first device's nCE pin isconnected to GND while its nCEO pin is connected to nCE of the nextdevice in the chain. The last device's nCE input comes from the previousdevice, while its nCEO pin is left floating. After the first device com<strong>pl</strong>etesconfiguration in a multi-device configuration chain, its nCEO pin driveslow to activate the second device's nCE pin, which prompts the seconddevice to begin configuration. The second device in the chain beginsconfiguration within one clock cycle; therefore, the transfer of datadestinations is transparent to the MAX II device. All other configurationpins (nCONFIG, nSTATUS, DCLK, DATA[7..0], and CONF_DONE) areconnected to every device in the chain. The configuration signals mayrequire buffering to ensure signal integrity and prevent clock skewproblems. Ensure that the DCLK and DATA lines are buffered for everyfourth device. Because all device CONF_DONE pins are tied together, alldevices initialize and enter user mode at the same time.All nSTATUS and CONF_DONE pins are tied together and if any devicedetects an error, configuration stops for the entire chain and you mustreconfigure the entire chain. For exam<strong>pl</strong>e, if the first device flags an erroron nSTATUS, it resets the chain by pulling its nSTATUS pin low. Thisbehavior is similar to a single device detecting an error.If the Auto-restart configuration after error option is turned on, thedevices release their nSTATUS pins after a reset time-out period(maximum of 100 ms). After all nSTATUS pins are released and pulledhigh, the MAX II device tries to reconfigure the chain without pulsing11–16 Altera CorporationStratix III Device <strong>Handbook</strong>, Volume 1 May 2007

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

Saved successfully!

Ooh no, something went wrong!