Configuring 2 Cyclone III's from one EPCS16 Using 2.5V

Ok, I did the following to load my two FPGA's separately, and got both FPGA's doing their thing.

1. Used "Convert Programming File" (CPF) utility to combine the two *.sof files into a *.pof for loading into the EPCS16, for programming the two FPGA's.

1a. In the Advanced menu of the CPF I selected the "Disable AS/AP mode CONF_DONE pin error check" check box. It had previously been checked but grayed out. I am not sure what being grayed out means (?).

2. Loaded the EPCS16 with this *.pof. Powered down. Powered back up. And ...

a) No blinking lights, FPGA logic not running.

b) nStatus High and NOT pulsing low. Not re-configuring.

c) nCEO Low and not toggling.

d) Config_Done (OR'ed from both FPGA's) Low, not happy.

e) Init_Done from first FPGA Low, not happy.

3. Attached USB Blaster to JTAG port for second FPGA and loaded second FPGA with its own *.sof.

a) Blinking lights from both FPGA's. FPGA logic running in both FPGA's.

b) nStatus High and NOT pulsing low. Not re-configuring.

c) nCEO Low and not toggling.

d) Config_Done (OR'ed from both FPGA's) High, happy.

e) Init_Done from first FPGA High, happy.

OK, mystery fans, what is my problem loading both FPGA's from the EPCS16 and having them work ?

My Speculations:

1. When I selected the "AS/AP mode CONF_DONE pin error check" I got the FPGA's to relax about

the error in the configuration (wherever it is) and this allowed me to program the second FPGA through the JTAG.

2. Signs indicate trouble with the configuration of the second FPGA from the EPCS16.

Also Noticed:

When loading the EPCS16 using the USB Blaster and the Quartus II Programmer utility the process goes through the following. I noted that the "Programming device 1" step quits and moves on to verification when the "Progress Bar" in the top corner of the window has only reach 35%.

Info: Device 1 silicon ID is 0x14

Info: Erasing ASP configuration device(s)

Info: Blank-checking device 1

Info: Programming device 1 <<<<<<<<<<<<<<<< Quits when progress bar has only reached 35%

Info: Performing verification on device 1