Configuration Handbook - Kamami.pl

Configuring Mercury, APEX 20K (2.5 V), ACEX 1K & FLEX 10K DevicesJTAG-chain device programming is ideal when the system containsmultiple devices, or when testing your system using JTAG BST circuitry.Figure 8–26 shows multi-device JTAG configuration.Figure 8–26. JTAG Configuration of Multiple Devices Using a Download CableDownload Cable10-Pin Male HeaderMercury, APEX 20K (2.5-V), Mercury, APEX 20K (2.5-V), Mercury, APEX 20K (2.5-V),(JTAG Mode)ACEX 1K or FLEX 10K Device ACEX 1K or FLEX 10K Device ACEX 1K or FLEX 10K Device(1) VCC (1) VCC(1) VCC (1) VCC(1) VCC (1) VCC(1) VCC1 kΩ1 kΩ1 kΩPin 11 kΩ1 kΩ1 kΩ1 kΩVCC (1) VCCnSTATUSnSTATUSnSTATUS(2) nCONFIG(2) nCONFIG(2) nCONFIG1 kΩ(2) MSEL0(2)CONF_DONEMSEL0(2)CONF_DONEMSEL0 CONF_DONE(2) MSEL1(2) MSEL1(2) MSEL1VCC nCE (4)VCC nCE (4)VCC nCE (4)TRST TRST TRSTVIO(3) TDITDOTDITDOTDITDOTMS TCKTMS TCKTMS TCK1 kΩNotes to Figure 8–26:(1) The pull-up resistor should be connected to the same supply voltage as the USB Blaster, MasterBlaster (VIO pin),ByteBlaster II or ByteBlasterMV cable.(2) The nCONFIG, MSEL0, and MSEL1 pins should be connected to support a non-JTAG configuration scheme. If onlyJTAG configuration is used, connect nCONFIG to V CC , and MSEL0 and MSEL1 to ground.(3) Pin 6 of the header is a VIO reference voltage for the MasterBlaster output driver. VIO should match the device’sV CCIO . Refer to the MasterBlaster Serial/USB Communications Cable Data Sheet for this value. In the ByteBlasterMV, thispin is a no connect. In the USB Blaster and ByteBlaster II, this pin is connected to nCE when it is used for ActiveSerial programming, otherwise it is a no connect.(4) nCE must be connected to GND or driven low for successful JTAG configuration.The nCE pin must be connected to GND or driven low during JTAGconfiguration. In multi-device PS, PPS, and PPA configuration chains, thefirst device’s nCE pin is connected to GND while its nCEO pin isconnected to nCE of the next device in the chain. The last device’s nCEinput comes from the previous device, while its nCEO pin is left floating.After the first device completes configuration in a multi-deviceconfiguration chain, its nCEO pin drives low to activate the seconddevice’s nCE pin, which prompts the second device to beginconfiguration. Therefore, if these devices are also in a JTAG chain, youshould make sure the nCE pins are connected to GND during JTAGconfiguration or that the devices are JTAG configured in the same orderas the configuration chain. As long as the devices are JTAG configured inthe same order as the multi-device configuration chain, the nCEO of theprevious device will drive nCE of the next device low when it hassuccessfully been JTAG configured.Altera Corporation 8–61August 2005 Configuration Handbook, Volume 1