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

Lost JTAG communication

Altera_Forum
Honored Contributor II
‎06-24-2009 05:26 PM
1,255 Views

Hello All, 

 

I am using a Stratix II with an EPC16 configuration device. I've managed to create a situation where I cannot achieve JTAG communication after programming with a .POF file. My error was that I forgot to set the unused pins to the tristate condition and ended up grounding them instead. Is there a way to disable the load on power-up so that I can get the JTAG communication back or erase the configuration device so that I can load the corrected .POF file? 

Thanks.
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎06-24-2009 05:33 PM
549 Views

You could drive the nConfig pin low (short it to ground). I believe you can just do this momentarily. 

 

Jake
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎06-24-2009 08:56 PM
549 Views

Thanks Jake, 

 

I tried your suggestion, but it didn't work in this case. It got me thinking though that I could lift the Data0 pin and maybe the Stratix ll wouldn't program - this worked! Thanks for the reply. 

 

Gary
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.