Nichestack OS tutorial 1 - Process of Starting a Module

Brief Introduction about NicheStack

                                                                Nichestack is primarily a TCP/IP stack with an inbuilt OS called Nichestack OS. Using the Nichestack OS, the TCP/IP stack can be directly run on a hardware or can be run on top of different third party RTOS. For this the Nichestack OS API should be mapped to the relevant RTOS API. There are different Nichestack ports already available including UCOS ii, FREE RTOS etc. Nichestack also supports another feature called Super-loop, particularly targeting the non-OS based systems. In Super-loop, there will be only one task with a single call-stack.

Nichestack was initially developed by Interniche technologies and it is taken over by HCC-Embedded and now by TUXERA.   

                                            

This post excludes the details about the Super-loop and Nichetsack OS on a third party RTOS.

Modules:

                This TCP/IP stack consists of different application layer protocols like FTP, HTTP etc. Each application layer protocol will be called as a "module"

Devices:

                There are different communication drivers present in the Nichestack such as Ethernet, PPP etc. These drivers associated with an interface is called as a "Device".

The below diagram describes the step by step process, while starting a module using Nichestack. Under the section initialize the modules, the socket section mentioned is with respect to server code.