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.

Passive Serial <strong>Configuration</strong>fFor more information on how to create configuration files for multideviceconfiguration chains, refer to Software Settings, chapter 6 and 7 involume 2 of the <strong>Configuration</strong> <strong>Handbook</strong>.In multi-device PS configuration, the first device’s nCE pin is connectedto GND while its nCEO pin is connected to nCE of the next device in thechain. The last device’s nCE input comes from the previous device, whileits nCEO pin is left floating. After the first device com<strong>pl</strong>etes configurationin a multi-device configuration chain, its nCEO pin drives low to activatethe second device’s nCE pin, which prompts the second device to beginconfiguration. All other configuration pins (nCONFIG, nSTATUS, DCLK,DATA0, and CONF_DONE) are connected to every device in the chain. Youshould pay special attention to the configuration signals because they canrequire buffering to ensure signal integrity and prevent clock skewproblems. Specifically, ensure that the DCLK and DATA lines are bufferedfor every fourth device.When configuring multi<strong>pl</strong>e devices, configuration does not begin until alldevices release their OE or nSTATUS pins. Similarly, since all deviceCONF_DONE pins are tied together, all devices initialize and enter usermode at the same time.Since all nSTATUS and CONF_DONE pins are tied together, if any devicedetects an error, configuration stops for the entire chain and the entirechain must be reconfigured. For exam<strong>pl</strong>e, if the first FPGA flags an erroron nSTATUS, it resets the chain by pulling its nSTATUS pin low. This lowsignal drives the OE pin low on the configuration device and drivesnSTATUS low on all FPGAs, which causes them to enter a reset state. Thisbehavior is similar to a single FPGA detecting an error.If the Auto-Restart <strong>Configuration</strong> After Error option is turned on, thedevices will automatically initiate reconfiguration if an error occurs. TheFPGAs will release their nSTATUS pins after a reset time-out period(maximum of 40 µs). When all the nSTATUS pins are released and pulledhigh, the configuration device tries to reconfigure the chain. If the Auto-Restart <strong>Configuration</strong> After Error option is turned off, the external systemmust monitor nSTATUS for errors and then pulse nCONFIG low for atleast 8 µs to restart configuration. The external system can pulse nCONFIGif nCONFIG is under system control rather than tied to V CC .7–10 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!