TM C/ TCP-IP Protocol Stack C/TCP-IP Protocol Stack DESCRIPTION PERFORMANCE C/TCP-IP is a compact, reliable, high-performance TCP/IP protocol In order to meet the demanding requirements of embedded systems, stack, optimized for embedded systems. Built from the ground up with with C/TCP-IP critical sections are kept to a minimum, while Micrium quality and scalability, C/TCP-IP enables rapid configuration selected run-time validations can be disabled to enhance of required network options to minimize time-to-market. performance. C/TCP-IP implements zero copy buffer management for greatest efficiency. With C/TCP-IP, the full advantage of high- C/TCP-IP allows for adjustment of the memory footprint based on performance DMA is enabled. Ethernet controllers can be harnessed design requirements. C/TCP-IP can be configured to include only so that TCP/IP stack is a true ZERO COPY stack. needed network modules. When a module is not used, it is not included in the build, saving valuable memory space. SUPPORT C/TCP-IPs design introduces a new concept: Large and small buffers. C/TCP-IP currently supports multiple simultaneous Network A large buffer is of the size required to transport a complete Ethernet frame. This is what other TCP/IP stacks do. But, in an embedded Interface Controller (NIC) interfaces system, it is quite possible that the amount of information to transmit C/TCP-IP supports Ethernet and wireless NICs. and receive does not require the use of a full Ethernet frame. In this case using buffers of the size of full Ethernet frames is a waste of RAM. Additional drivers are added on a regular basis. Check Micrium.com for a complete list of drivers. C/TCP-IP allows the designer to maximize the system performance by defining different quantities of small and large buffers. APPLICATION ADD-ON MODULES C/TCP-IP requires the presence of an RTOS for task scheduling and C/DHCPc Dynamic Host Configuration Protocol (client) mutual exclusion. To meet this requirement, Micrium provides source C/DNSc Domain Name System (client) code to allow network applications to readily accommodate C/OS-II C/FTPc File Transfer Protocol (client) and C/OS-III. Based on the modules ostensible Kernel interface, C/FTPs File Transfer Protocol (server) other Kernels can also be adapted to C/TCP-IP. C/HTTPs HyperText Transport Protocol (server) a.k.a. Webserver C/TCP-IP can be used on 16-, 32-, and even 64-bit CPUs or DSPs. C/POP3c Post Office Protocol (client) APPLICATIONS C/SMTPc Simple Mail Transfer Protocol (client) C/SNTPc Simple Network Time Protocol (client) The source code for C/TCP-IP is an extremely robust and highly C/TFTPc Trivial File Transfer Protocol (client) reliable TCP/IP solution. C/TCP-IP is designed to be certifiable for C/TFTPs Trivial File Transfer Protocol (server) use in avionics, compliant for use in FDA-certified devices, and in C/TELNETs Telnet (server) other safety-critical products. The table above lists the application modules available from Micrium. FEATURES The lowercase c or s at the end of the product name represents the Client version or Server version of the module. Any application Memory footprint is adjustable modules following the Berkeley 4.4 (BSD) socket interface can be Flexibility to select large and small buffers used with C/TCP-IP. RTOS required: C/OS-II, C/OS-III, or other Zero copy buffer management High performance ANSI C source code Supports multiple NIC interfaces 1 Micrim data sheet for C/TCP-IP (2/16/12) +1 954 217 2036 email: sales micrium.com www.micrium.comC/TCP-IP ARCHITECTURE Other HTTP FTP SMTP DHCP DNS TFTP Other Application Transport TCP UDP and / or ICM IGM Network ARP I PP SLI Link and / or Ethernet / wireless and / or Serial Physical At every layer where And/Or is indicated, at least one of the protocols must be used. This is particularly important for embedded systems with limited resources. For example, should an application not require TCP capabilities, C/TCP-IP can be configured to include UDP only at the Transport layer. At the Application layer, an application can use any of the Micrium applications or none. At the Link and Physical layers, there is a choice of Local Area Networking (LAN) technologies. Multiple Network Interfaces are available via the C/TCP-IP multi-homing feature. For pricing, delivery, and ordering information, please visit Micriums website at: www.micrium.com. For the way Engineers work 2 Micrim data sheet for C/TCP-IP (2/16/12) +1 954 217 2036 email: sales micrium.com www.micrium.com