|
μC/TCP-IP is a compact, reliable, high-performance TCP/IP protocol stack, optimized for embedded systems.
Built from the ground up with Micrium quality, scalability and reliability, μC/TCP-IP enables the rapid configuration of required network options to minimize time-to-market.
μC/TCP-IP allows for adjustment of the memory footprint based upon design requirements. μC/TCP-IP can be configured to include only those network components necessary to the system. When a component is not used, it is not included in the build, saving valuable memory space.
The μC/TCP-IP design introduces a new concept: Large and small buffers. 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 system, it is quite possible that the amount of information to transmit 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. μC/TCP-IP allows the designer to maximize the system performance by defining different quantities of small and large buffers.
The source code for μC/TCP-IP is an extremely robust and highly reliable TCP/IP solution. μC/TCP-IP is designed to be certifiable for use in avionics, compliant for use in FDA-certified devices, and in other safety-critical products.
μC/TCP-IP requires the presence of an RTOS for task scheduling and mutual exclusion. To meet this requirement, Micrium provides source code to allow network applications to readily accommodate μC/OS-II and μC/OS-III.
Note: Based on the component’s extensible kernel interface, other non-Micrium kernels can also be adapted to μC/TCP-IP, but are not supported
The features of µC/TCP-IP include:
Delivered with complete 100% ANSI C source code and in-depth documentation.
Scalable to contain only required features and minimize memory footprint.
Zero copy buffer management.
Flexibility to select large and small buffers.
High performance.
Supports multiple interfaces.
Support for any real-time kernel available. Micrium’s µC/OS-III or µC/OS-II is recommended. Sold separately.
Built in SSL (Secure Sockets Layer) API. Supports most SSL stacks. Contact Micrium to learn more about the µC/SSL module developed with our partner Mocana Inc.
μC/TCP-IP features a hardware abstraction layer allowing quick porting to any new Ethernet device controllers (and addition to Micrium’s list of supported devices).
Micrium offers a large selection of Ethernet device controller drivers. Additional drivers are added on a regular basis.
If your desired Ethernet device controller driver is not listed, you can consult the μC/TCP-IP user manual, which contains a chapter on driver development. You can also ask Micriμm to develop the driver for you. Please call us for a quote.
Micrium uses Ixia’s IxANVL to validate the compliance of the stack with the networking RFCs. IxANVL is used by Developers and manufacturers of networking equipment and Internet devices to validate protocol compliance and interoperability.
The following document lists the different RFCs supported by µC/TCP-IP.
Download uC-TCPIP-V2 RFC Compliance Matrix (PDF, 90 KB)
µC/TCP-IP specifications include, but are not limited to, the following:
Supported Processors |
Almost all processors are supported by µC/TCP-IP. |
Other Related Micrium Products |
μC/OS-II, μC/OS-III, μC/FS, µC/Clk, µC/DHCPc, µC/DNSc, µC/HTTPs, µC/FTPc, µC/FTPs, µC/TFTPs, µC/TFTPc, µC/POP3c, µC/SMTPc, µC/SNTPc, µC/TELNET. |
Real-time Kernel |
Required. Micrium’s μC/OS-III or μC/OS-II suggested and supported. |
Transport Layer |
TCP and/or UDP |
Protocol supported |
IGMP-V2 (Multicast), ICMP, ARP |
Interface type |
Ethernet (802.3 and Ethernet), Wifi*, Loopback |
Socket API |
2 set of proprietary Socket APIs and standard BSD socket. |
Dynamic Host Configuration Protocol – client
Delivered with complete 100% ANSI C source code.
Scalable to contain only required features and minimize memory footprint.
Support dynamic IP address configuration for multiple interfaces.
Support for any real-time kernel available. A kernel is required.
Domain Name System – client
Delivered with complete 100% ANSI C source code and in-depth documentation.
Easy configuration
Simple API
File Transfer Protocol- client
Delivered with complete 100% ANSI C source code.
Scalable to contain only required features and minimize memory footprint.
Support authentication.
Transfer via buffers or files.
Support any File system (not required if all transfers are done via buffers)
Support SSL (Secure Sockets Layer)
File Transfer Protocol- server
Delivered with complete 100% ANSI C source code.
Scalable to contain only required features and minimize memory footprint.
Single connection.
Callback function is used to authenticate user.
Support any File system, A file system is required.
Support SSL (Secure Sockets Layer).
HyperText Transport Protocol server, a.k.a. web server
Delivered with complete 100% ANSI C source code.
Scalable to contain only required features and minimize memory footprint.
Single connection.
Support of dynamic token replacement in HTML documents.
Support of handling post form submissions (CGI).
Support any File system or can be used via a static file system which is provided.
Support for any real-time kernel available. A kernel is required.
Support SSL (Secure Sockets Layer).
Post Office Protocol – client
Delivered with complete 100% ANSI C source code.
Easy configuration
Simple API
Simple Mail Transfer Protocol – client
Delivered with complete 100% ANSI C source code.
Easy configuration
Simple API
Simple Network Management Protocol Agent
Delivered as a source code SDK in highly portable ANSI C, or as a binary SDK
SNMPv3 support
Includes MIB compiler
Full implementation of SNMP Version 3 Agent with USM, VACM and SNMPv3 application MIBs
The SNMP Agent is provided by DMH Software.
Simple Network Time Protocol – client
Delivered with complete 100% ANSI C source code.
Easy configuration
Simple API
Secure Socket Layer, supporting the following RFCs:
RFC-2246: TLS Protocol Version 1.0
RFC-3268: AES Ciphersuites for Transport Layer Security
RFC-3280: Internet X.509 Public Key Infrastructure
RFC-3546: Transport Layer Security Extensions (partially supported)
RFC-4279: Pre-Shared Key Ciphersuites for Transport Layer Security
RFC 4346: TLS 1.1
RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)
RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
RFC 5288: AES Galois Counter Mode (GCM) Cipher Suites for TLS
RFC 5289: TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
RFC 5430: Suite B Profile for Transport Layer Security (TLS)
RFC 5746: Renegotiation Indication Extension
RFC 6066: Transport Layer Security (TLS) Extensions (partially supported, for Server Name Indication (SNI) and Certificate Status (OCSP stapling) extensions only)
60K of RAM is required per secured socket.
Telnet – server
Delivered with complete 100% ANSI C source code.
Callback function is used to authenticate user.
Callback function is used to handle any external command.
Support SSL (Secure Sockets Layer).
Trivial File Transfer Protocol – client
Delivered with complete 100% ANSI C source code.
Easy configuration
Simple API
Support any File system, A file system is required.
Trivial File Transfer Protocol – server
Delivered with complete 100% ANSI C source code.
Easy configuration
Support any File system, A file system is required.
The table below shows the list of hardware architectures from our silicon partners for which we provide Ethernet controller support. It also indicates its location indicating if it is part of the microcontroller (MCU), part of a field-programmable gate array (FPGA), or external to the device (External).
If you don’t see the driver you are looking for please contact our sales department. We can give you the latest information on new driver development.
μC/TCP-IP provides these Ethernet controller drivers:
Manufacturer |
Driver |
Device Family |
Location |
MAC Type |
---|---|---|---|---|
Actel |
A2Fx00 |
A2Fx00 |
MCU |
Ethernet 10/100 |
Altera |
TSE |
Stratix V, Stratix IV, Arria V, Arria II, Cyclone V, Cyclone IV & HardCopy IV |
FPGA |
Ethernet 10/100/1000 |
Atmel |
AT91RM9200 |
RM9200 |
MCU |
Ethernet 10/100 |
Atmel |
MACB |
AVR32 |
MCU |
Ethernet 10/100 |
Atmel |
MACB_AP7000 |
AVR32 AP7000 |
MCU |
Ethernet 10/100 |
Davicom |
DM9000 |
- |
External |
Ethernet 10/100 |
Freescale |
FEC |
- |
MCU |
Ethernet 10/100 |
Freescale |
FEC_MPC55xx |
MPC55xx |
MCU |
Ethernet 10/100 |
Freescale |
MACNet |
Kinetis |
MCU |
Ethernet 10/100 |
STMicroelectronics |
GMAC |
STM32Fxxxx MB9BFD10T MB9BF610T MB9BF210T LPC185x LPC183x LPC435x LPC433x |
MCU |
Ethernet 10/100 |
Luminary Micro |
LM3S9Bxx |
LM3S9B9x |
MCU |
Ethernet 10/100 |
Luminary Micro |
LM3Sxxxx |
LM3Sxxxx |
MCU |
Ethernet 10/100 |
Microchip |
PIC32 |
PIC32MX6/7 |
MCU |
Ethernet 10/100 |
NXP |
LPCxxxx |
LPC17xx LPC23xx LPC24xx LPC32x0 |
MCU |
Ethernet 10/100 |
Renesas |
H8S2472 |
H8S2472 |
MCU |
Ethernet 10/100 |
Renesas |
RX-EtherC |
RX62N RX63N |
MCU |
Ethernet 10/100 |
Renesas |
SH-EtherC |
SH-Ether |
MCU |
Ethernet 10/100 |
SMSC |
LAN911x |
LAN911x |
External |
Ethernet 10/100 |
STMicroelectronics |
STM32Fxxx |
STM32Fxxx |
MCU |
Ethernet 10/100 |
STMicroelectronics |
STR912 |
STR912 |
MCU |
Ethernet 10/100 |
Texas Instruments |
OMAP-L1x |
OMAP-L137 OMAP-L138 |
MCU |
Ethernet 10/100 |
Toshiba |
TMPM369 |
TMPM369 |
MCU |
Ethernet 10/100 |
Xilinx |
XPS_LL_TEMAC |
Virtex-5 LX, Virtex-5 LXT, Virtex-5 SXT, Virtex-4 FX, Virtex-4 LX, Virtex-4 SX, Spartan-6, Spartan-3A, Spartan-3A DSP, Spartan-3AN & Virtex-6 |
FPGA |
Ethernet 10/100/1000 |
μC/TCP-IP provides these Wi-Fi controller drivers:
Manufacturer |
Driver |
Device Family |
Location |
MAC Type |
---|---|---|---|---|
Redpine Signals |
RS9110n2x |
RS9110-N-11-2x-(xx) |
External |
Wi-Fi |
μC/TCP-IP provides these physical layer (PHY) drivers:
Manufacturer |
Driver |
PHY Chip |
Media Interface |
Media Interface Location |
- |
Generic |
- |
(R)MII |
EMAC |
Texas Instruments |
DP83848C |
DP83848C |
(R)MII |
EMAC |
Texas Instruments |
DP83640 |
DP83640 |
(R)MII |
EMAC |
AMD |
AM79C874 |
AM79C874 |
(R)MII |
EMAC |
Marvell |
88E1111 |
88E1111 |
GMII/RGMII/MII |
EMAC |
The following Ethernet driver are currently under development and will be released soon:
Manufacturer |
Driver |
Device Family |
Location |
MAC Type |
---|---|---|---|---|
Infineon |
XMC4500 |
XMC4500 |
MCU |
Ethernet 10/100 |
Texas Instruments |
AM35x |
AM35x |
MCU |
Ethernet 10/100 |
Texas Instruments |
AM389x |
AM389x |
MCU |
Ethernet 10/100/1000 |
The following PHY driver are currently under development and will be released soon:
Manufacturer |
Driver |
PHY Chip |
Media Interface |
Media Interface Location |
---|---|---|---|---|
LSI |
ET1011C |
ET1011C |
GMII/RGMII/MII |
EMAC |