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

entering superloop niche while using uCOS ?

Altera_Forum
Honored Contributor II
‎02-21-2011 02:31 AM
1,012 Views

Dear all, 

 

Currently I'm developing a gigabit ethernet interface project on Stratix IV. The FPGA has to receive data continuously from a DSP board and transmit them to PC. The connection between the FPGA and the PC is via TCP/IP. So it means the FPGA has to send data via TCP/IP in repetition (transmitting data for each data packet). 

I have written the C code based on the SimpleSocketServer, and the current design can transmit the data discretely (not continuous data). However, when I tried to make it transmit the continuous data (just adding iteration in the TCP/IP transmisiion process), I got the following error : 

 

dtrap - needs breakpoint dtrap - needs breakpoint  

 

From this forum, somebody ever said that this "dtrap - needs breakpoint" error may happen when we use superloop niche mode. However, in my design I think I don't use the superloop niche because my design use uCOS-II. 

 

So anyone, please help me to figure out how to solve this problem... Or if anyone ever develop a system that transmit continuous data like me, please kindly give me an example of the appropriate way in C code to handle this thing. :( 

 

Thanks
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎02-21-2011 09:44 AM
344 Views

like the name says, to find out what is happening you need to run your application with a debugger and put a breakpoint on dtrap(). Then when the debugger stops, go up in the function call list and find out where dtrap() was called. If you are lucky you'll find a comment next to the call saying what the problem is. The Interniche stack developers were too lazy to write real error messages.

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.