Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

Programming Cyclone II with DE2 board

Altera_Forum
Honored Contributor II
‎09-22-2013 07:34 PM
1,322 Views

I'm currently trying to program a simple Verilog file that turns on an LED when the switch is triggered, but Quartus is giving me an error: 

 

Error (209014): CONF_DONE pin failed to go high in device 1 

 

I've selected the correct chip type (EP2C35F672C6N), and it compiles correctly, and my board is in PROG mode. Is there anything else I'm doing wrong with it?
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎09-26-2013 09:14 PM
460 Views

That error message is a JTAG programming error message I believe. 

 

I don't have a DE2, but if it's like the DE0, the PROG mode switch switches it so you are talking to the Active Serial flash device. So you program that with the POF file. If you want to talk to it via JTAG, it's left in RUN mode. 

 

The other possibility is you have a bad USB Blaster. They are have transceivers on their outputs that can be damaged if ever over-voltaged, or left connected to the board when not connected to a USB power source. 

 

Pete
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.