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

NicheStack TCP/IP Stack usage question "Maximum Number of Tasks must be four or less"

ZXiao1
Beginner
‎08-05-2018 08:35 AM
1,550 Views

Hi,

 I am using the NicheStack TCP/IP Stack in the UCOS . And I find the words "Maximum Number of Tasks must be four or less" in the software developer's handbook. I don't understand why the is task number constrain in this usage. Dose anyone know this ? 

thans

 

0 Kudos

Link Copied

1 Reply
JosephC_Intel
Moderator
‎08-16-2018 04:54 PM
794 Views

Hi Zxiao1,

 

NicheStack TCP/IP Stack allowing us to creates one or more system level tasks on initialization stages.

 

This is defined in advanced when netmain function is called. We can change this on the system level tasks through in ipport.h. Just go to your BSP project, in the iniche/src/h/nios2 folder under #define statement and config the module of priority, inclusion or stack size based on your requirements.

 

There are more information stated in below tutorial guide:

https://www.intel.com/content/dam/altera-www/global/en_US/pdfs/literature/tt/tt_nios2_tcpip.pdf

 

Best Regards,

JosephC

Intel Customer Support

Sales Marketing Group

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.