New Contributor
Regular ContributorMay i know which bitstream you are programming into it?
Also, can you check the nSTATUS pin state during device boot up? Would like to root cause the issue.
New ContributorThe issue appears to not be hardware or original EPCS16 POF related as an EPCS16 was installed in place of the EPCQ16A and using Quartus II on a legacy computer setup, I can repeatedly program and verify with success. I should mention that with the free downloadable Quartus Prime Programmer I have not been able to get a successful verification (by checking the verify option either with the program option or separately) even after what Prime says is a “successful” programming step.
The nStatus timing state is proper but have only monitored it on hardware with EPCS16 or first time EPCQ16A that enters proper user mode. Concern about resinstalling additional configuration devices on this particular board will limit future EPCQ16A troubleshooting efforts.
>The same USB Blaster is being used for both Quartus II and Quartus Prime setups with the only difference being the legacy setup is running an older version of Windows while the computer that is running Prime is Windows 10 Enterprise (with USB Blaster driver installed from the installed Prime folder). As I have previously stated, I can get a successful programming with proper user mode if the EPCQ16A is brand new (although not able to get successful verification).
>With an EPCS16 installed and using the original EPCS16 POF generated by Quartus II, I was able to successfully use the Quartus Prime Programmer and repeatedly successfully program (and verify) the board with proper user mode function.
It appears that something in the conversion of the original SOF to the EPCQ16A POF in Quartus Prime Programmer conversion section appears isn't proper.
Figure 9-7 in the Cyclone III Handbook is the hardware connection.
A decision has been made to source/procure more EPCS16 parts if prompt resolution can't be made,. Thanks.
