Forum Discussion
Altera_Forum
Honored Contributor
19 years agoTry isolating the cause first. Disable a few SOPC Builder components at a time and tie those output pins to something safe (high or low). If you still have problems keep reducing the system until you determine what the culprit is. If you get down to an onchip memory, jtag uart, Nios II and still can't download code then start checking Quartus settings.
Once you have solved the problem just add the components back in. By the way, the method I recommend people bring up a design is to start small then add to the design. That way you don't have to debug a complicated system that you end up having to tear apart to find issues. 99% of the time I see this issue caused by one of two things: 1) Incorrect pin assignments 2) Unused I/O not set to input tri-state (common mistake when using Nios dev boards) Also I recommend searching for one of the strings for the error output like "Pausing target processor: not responding". You will find other posts on this topic as well.