Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
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.
12748 Discussions

"Connection Refused" error when debugging NIOS2 code.

Altera_Forum
Honored Contributor II
‎01-26-2010 06:13 PM
1,436 Views

Hello. 

 

I get the following errors in Eclipse when trying to debug my Nios2 program: 

 

:2342: Connection refused. 

 

A little more info: 

I am running Quartus & Nios2eds v9.1 

In the Debugger tab in the Debug Configurations dialog in Eclipse, I have the “Altera CDI GDB Debugger” selected. Is this correct? 

I am using a Cyclone EP1C20 dev board. 

I am connected to the dev board with a ByteBlaster2 . 

I am able to successfully build and load my FPGA design into the FPGA via Quartus. 

I am running an OpenCore2 time-limited Nios2 core. 

 

Any help in figuring out what I’m doing wrong would be greatly appreciated. 

 

Thank you 

Scott Wild
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎02-05-2010 06:34 AM
612 Views

I found it... If I click on the debug pane in Eclipse before starting the debugger, it works.

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.