uIP (micro IP)

The uIP is an open-source implementation of the TCP/IP network protocol stack intended for use with tiny 8- and 16-bit microcontrollers. It was initially developed by Adam Dunkels of the "Networked Embedded Systems" group at the Swedish Institute of Computer Science, licensed under a BSD style license, and further developed by a wide group of developers.

UIP
Stable release
1.0[1] / 27 March 2013 (27 March 2013)
Repository
Platformembedded systems
TypeTCP/IP stack
LicenseBSD

uIP can be very useful in embedded systems because it requires very small amounts of code and RAM. It has been ported to several platforms,[2][3][4] including DSP platforms.[5]

In October 2008, Cisco, Atmel, and SICS announced a fully compliant IPv6 extension to uIP, called uIPv6.[6]

Implementation

uIP makes many unusual design choices in order to reduce the resources it requires. uIP's native software interface is designed for small computer systems with no operating system. It can be called in a timed loop, and the call manages all the retries and other network behavior. The hardware driver is called after uIP is called. uIP builds the packet, and then the driver sends it, and optionally receives a response.

It is normal for IP protocol stack software to keep many copies of different IP packets, for transmission, reception and to keep copies in case they need to be resent. uIP is economical in its use of memory because it uses only one packet buffer. First, it uses the packet buffer in a half-duplex way, using it in turn for transmission and reception. Also, when uIP needs to retransmit a packet, it calls the application code in a way that requests for the previous data to be reproduced.

Another oddity is how uIP manages connections. Most IP implementations have one task per connection, and the task communicates with a task in a distant computer on the other end of the connection. In uIP, no multitasking operating system is assumed. Connections are held in an array. On each call, uIP tries to serve a connection, making a subroutine call to application code that responds to, or sends data. The size of the connection array is a number that can be adjusted when uIP is recompiled.

uIP is fully compliant with the RFCs that define TCP, UDP and IP. It also implements the mandatory maintenance protocol ICMP.

Versions

uIP 0.9[7] is the version with the least dependence on operating systems, the smallest resource use, and the only version that presents a pure event loop API, but in its original form does not support IP version 6, only the older, more common IPv4. It may be used in embedded systems with very small amounts of resources.

It was delivered with a set of examples of higher-level protocols that also run on an event loop system, including HTTP (a simple web server), SMTP (simple mail transmission protocol), FTP (file transfer protocol), telnet (terminal emulation), and others. Despite the examples and its small size, uIP 0.9 can be difficult to apply because it does not use any form of socket API.[8]

uIP is widely used code with well-known weaknesses. The design minimizes and separates 32-bit arithmetic so that it can be adjusted or optimized for 8 and 16-bit CPUs. Also, 16-bit software timers (common on small microcontrollers) can overflow and cause defective operation. This can be fixed with a timer system that does not overflow (e.g. the timers count down or use modular arithmetic).

Another issue is that its single packet buffer can have substantial throughput problems because a PC host usually delays the "ACK" packet, waiting for more packets. In slow, serial port implementations, the ack-throughput can be fixed by modifying uIP to send every packet as two half-packet fragments. uIP systems with fast ethernet or WiFi can modify the hardware driver to send every packet twice.[5]

Some PCs do not correctly respond to a fast uIP system on a local ethernet, because the uIP system can start a responding packet before the PC is ready to receive it. The solution is to call the uIP system less frequently in the main loop (Windows PCs are designed for a response time of about 1 millisecond). Typical implementations of uIP have a fixed IP address, which can make them impractical in real networks, although some have implemented DHCP.[9][10]

Later versions of uIP, including the reference version of uIPv6, are integrated with Contiki, an operating system that uses coroutines for cooperative multitasking. Contiki provides the multitasking needed by a simplified socket API, simplifying the use of uIP. These versions may be less popular than 0.9 however. Many examples of embedded code do not use them.[11][12][13]

See also

References
  1. "Release 1.0". 27 March 2013. Retrieved 18 March 2019.
  2. Metzinger, Zach (March 25, 2008). "APPLICATION NOTE 4205 - Using the uIP Stack to Network a MAXQ Microcontroller". Maxim Integrated Products, Inc. Retrieved February 2, 2015.
  3. "AN057 – uIP V1.0 TCP/IP Stack for eCOG1k and eCOG1X, Version 1.0" (PDF). Cyan Technology Ltd. January 28, 2008. Archived from the original (PDF) on February 18, 2012. Retrieved February 18, 2012.
  4. Curtis, Paul. "Adam Dunkel's uIP on the Olimex EasyWeb2 and LPC-E2124". Rowley Associates Limited. Retrieved February 2, 2015.
  5. Barnett, Drew; Massa, Anthony J. (February 1, 2005). "Inside the uIP Stack". Dr Dobbs Journal. Retrieved February 2, 2015.
  6. "Cisco, Atmel and the Swedish Institute of Computer Science (SICS) Collaborate to Support a Future Where Any Device Can Be Connected to the Internet". Cisco. October 14, 2008. Retrieved February 2, 2015.
  7. Dunkels, Adam. "Tagged releases". uIP tagged releases on GitHub. Retrieved February 2, 2015.
  8. See Dunkel's original web site, above, on the wayback machine.
  9. See Code-Red sample code for the RDB4078 PCB, 2012.
  10. Dunkel provided sample code for DHCP.
  11. Metzinger, above
  12. FreeRTOS web site examples, 2013
  13. Code-Red examples, above.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.