Using the NicheStack TCP/IP Stack - Nios II Edition Tutorial

ID 683574
Date 10/04/2021
Public
Document Table of Contents

1.7.2. NicheStack TCP/IP Stack Default Task Creation

The NicheStack TCP/IP Stack creates one or more system level tasks during system initialization, when you call the netmain() function. Users have complete control over these system level tasks through a global configuration file named ipport.h, located in the directory structure for the BSP project, in the iniche/src/h/nios2 folder.

You can edit the #define statements in ipport.h to configure the following options for the NicheStack TCP/IP Stack:

  • Module Inclusion—Identifies which built-in NicheStack modules should be started
  • Module Priority—Identifies what MicroC/OS-II priority the module task should use
  • Module Stack Size—Identifies what MicroC/OS-II stack size the module should use

For more information about other NicheStack TCP/IP Stack options that can be enabled at run-time, refer to the NicheStack TCP/IP Stack documentation in the NicheStackRef.zip file located in the <Nios II EDS install path>/components/altera_iniche/UCOSII/31src directory.

In the Nios II Simple Socket Server design example, only the minimum required NicheStack TCP/IP Stack tasks have been configured to run. These tasks are as follows:

  • tk_netmain—Initializes the stack, including networking interfaces
  • tk_nettick—A time management task that the networking stack uses

For more information about these NicheStack TCP/IP Stack tasks, refer to the “Task Priorities in the Nios II Simple Socket Server Design” section.