Forum Discussion
Honored ContributorPausing target processor: not responding.
when i try to run as NIOS II hardware, i am getting this error,
Using cable "USB-Blaster [USB-0]", device 1, instance 0x00 Pausing target processor: not responding. Resetting and trying again: FAILED Leaving target processor paused how can i correct it, Its running in the simulator though (NIOS instruction set simulator)17 Replies
Altera_Forumhello,
i am currently working on DE2 70 altera kit for my final year project and want to send messages using ethernet port. i am working using SOPC builder. Firstly i want to run a small program(eg. LEDs). i have created a NIOS II system using SOPC builder, then i have used altera monitor program to compile a c program. system got downloaded on to the board but when i m trying to load it i am getting the following error. Usingcable "USB-Blaster [USB-0]", device1,instance 0x00 Pausingtargetprocessor: not responding. Resetting and trying again: FAILED Leavingtargetprocessorpaused please kindly help me to sort this error.- Altera_Forum
Did you chech the clock and reset signals, as already suggested in the thread?
- Altera_Forum
i have assigned the clock and reset to iCLK_50 and iKEY(0) in the pin assignment vhdl file. but still it doest work. arent they correct?
- Altera_Forum
Can you check the polarity of your reset signal? The reset input on an SOPC/QSYS design is active low, so it needs to be '1' for the CPU to work. I don't know the polarity of the KEY signals on the DE2 board.
- Altera_Forum
I had some problems with the board,
now got response from the board - Altera_Forum
I had a similar problem that was solved by making sure the NIOS reset output (jtag_debug_module_reset) is connected to the reset inputs of the other components, including the NIOS itself (reset_n). The loading process was unable to pause the processor until this change was made.
- Altera_Forum
I too got similar error and resolved it by making sure that my Clock and Reset pins at the top level were correctly assigned (Pin Planner/ Assignment Editor). Once fixed, this resolved the problem.
So it appears, for such messages, one must look closely at the top level (including Nios / Connected components) Clock and Reset connections.
