Honored Contributor
Honored ContributorHi Frank,
I verified the ECP16 using the Quartus II programmer. It says it is programmed ok. So I guess I have to believe it. My concern is that the file that I am using might be somehow broken or that this data gets corrupted when sent from EPC16 to ACEX. Regarding the restart on error part, I can tell that some of the file is sent because I get a pretty clear DCLK burst for a few milliseconds, something between 5 ms and 50 ms depending of the board configuration (I already tried so many things). So, I would hope it to restart because it does start configuration, no? Unless the FPGA releases nSTATUS and the configuration isnt properly started... but then, why would it pull nSTATUS low to indicate the error? This should by itself restart the EPC16 configuration controller. But it will require nSTATUS to go back high to signal the ACEX is ready for a second try... The serial scheme is described in the configuration handbook and seemed like a good alternative to having 5 (we have a total of 5 ACEX on the board) EPC2. You can set it to a concurrent programming scheme and then each of the 8 data outputs from EPC16 can be used to configure a different device. Thank you for your input. Do you have any other ideas?
