<Products> Industrial> TCP/IP> NicheStack IPv4

TCP/IP

NicheStack IPv4 & NicheLite TCP/IP

NicheStack and NicheLite are both fully functional and easily portable TCP/IP stacks that contain all basic protocols for Internet-, Intranet- and LAN-connections. They are supplied as source code (ANSI-C) together with a socket API and comprehensive, detailed online documentation.

Both stacks contain the following protocols and services:
  • Address Resolution Protocol (ARP)
  • Internet Protocol (IP)
  • Internet Control Message Protocol (ICMP)
  • Dynamic Host Configuration Protocol Client (DHCP-Client)
  • Trivial File Transfer Protocol (TFTP)
  • Transport Control Protocol (TCP)
  • User Datagram Protocol (UDP)
  • NicheTask (on request)
  • Nichetool: System optimization and online debugging tool

Additionally, the NicheStack also includes:

  • File Transfer Protocol (FTP)
  • TELNET
  • IP Multicast

Memory Requirements
The two stacks differ in some functional features and especially in different codesize: NicheLite is extremely slim and requires only about 12 kByte of code. However, it supports only one interface (Ethernet-Controller, PPP, etc.), does not allow routing or multicasting, and has only a mini-socket with BSD-subset. While NicheStack does not have these limitations, it does require more code memory: A standard application on a 32-bit processor with ARP, IP, ICMP, UDP, DHCP, TCP with a socket-API results in a code size of approximately 50 kBytes.

Overview Protocols/Services

NicheLite Mini-IP NicheStack
Code Size 4 kB 15 kB
UDP X X
IP X X
Routing - X
ICMP X X
ARP X X
Network 1 Interface Unlimited
Multicast - X

NicheLite Mini-TCP NicheStack
Code Size 6 kB 31 kB
TCP X X
Sockets Mini (BSD Subset) Full BSD


Specific Features

  • Easy integration: NicheStack and NicheLite can be used in connection with RTOS as well as being integrated in superloop systems. Special multitasking capabilities are not required.

  • Versatile, flexible memory management: memory is used economically and available again immediately after use.
  • Memory allocation via macros allows the adaptation to different compilers.

  • RTOS-independent: both stacks provide an "Application Process Interface" for major operating systems, simplifying integration into these operating systems.

  • Network interfaces: both stacks support Ethernet, Token Ring, SLIP and PPP.

  • Zero-Copy-Stack: for the exchange of data between various protocol levels, a single memory buffer is used.
    The buffer is passed by reference, not copied, from one protocol level to the next,providing maximum performance with minimal memory requirement.

  • 12 months support and warranty included in the package.