uIP 1.0嵌入式TCP/IP栈详解与模块指南

lwIP

web服务器

4星 · 超过85%的资源需积分: 9 82 浏览量更新于2024-07-26 收藏 1.52MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

uIP技术手册（1.0版本）是一份详细的嵌入式TCP/IP栈开发指南，由Adam Dunkels编写，发布于2006年6月，针对不会英语的读者提供了有道翻译的支持。该手册主要介绍uIP（Ultra Lightweight IP），一个轻量级的网络协议栈，特别适合资源受限的嵌入式系统。 1. **uIP TCP/IP Stack** - uIP是专为小型、低功耗设备设计的轻量级TCP/IP堆栈，它提供基本的互联网通信功能，如IP协议栈的核心组件，包括IP、ICMP、UDP等。 - 主要控制循环确保了高效的通信处理，同时考虑到内存管理和性能优化。 2. **Architecture-Specific Functions** - 由于uIP是架构特定的，手册详细解释了如何根据目标硬件平台定制和实现特定的功能，以适应不同的硬件环境。 3. **Memory Management** - 由于资源限制，内存管理在uIP中至关重要。手册涉及内存分配策略和数据结构优化，以最大限度地利用有限的存储空间。 4. **Application Programming Interface (API)** - 提供了一套完整的API，使得开发者能够方便地在uIP上构建应用，包括初始化、配置、设备驱动接口以及应用程序级别的功能调用。 5. **Examples and Protocol Implementations** - 手册包含了示例代码，帮助读者理解如何使用uIP进行实际项目中的网络通信，同时也展示了各种协议的实现细节。 6. **Performance** - 除了详细介绍uIP的架构和功能，手册还关注了性能优化，包括吞吐量、延迟和能效等方面，这对于嵌入式系统的实时性和能源效率至关重要。 7. **Module Documentation** - 部分章节深入讲解了uIP的核心模块，如Protothreads（一种异步编程模型）、应用程序模块、配置函数、初始化函数、设备驱动接口和应用程序级别的函数，以及用于设备驱动的变量和数据结构。 8. **uIP Configuration and Initialization** - 提供了详细的配置选项和初始化过程，帮助用户根据具体需求定制和设置uIP的行为。 9. **uIP TCP/IP Stack Implementation** - 进一步阐述了uIP内部工作原理，包括IP地址解析协议和架构特定的uIP功能，这对于理解底层网络通信机制很有帮助。这份uIP技术手册为嵌入式开发人员提供了关于如何在资源受限环境中部署和使用uIP TCP/IP栈的全面指南，从基础概念到高级定制，涵盖了所有必要的技术和实施细节。

资源详情

资源推荐

10 The uIP TCP/IP stack

1.7.4 Utilizing TCP Flow Control

This example shows a simple application that connects to a host, sends an HTTP request for a ﬁle and

downloads it to a slow device such a disk drive. This shows how to use the ﬂow control functions of uIP.

void example4_init(void) {

u16_t ipaddr[2];

uip_ipaddr(ipaddr, 192,168,0,1);

uip_connect(ipaddr, HTONS(80));

}

void example4_app(void) {

if(uip_connected() || uip_rexmit()) {

uip_send("GET /file HTTP/1.0\r\nServer:192.186.0.1\r\n\r\n",

48);

return;

}

if(uip_newdata()) {

device_enqueue(uip_appdata, uip_datalen());

if(device_queue_full()) {

uip_stop();

}

if(uip_poll() && uip_stopped()) {

if(!device_queue_full()) {

uip_restart();

}

When the connection has been established, an HTTP request is sent to the server. Since this is the only

data that is sent, the application knows that if it needs to retransmit any data, it is that request that should

be retransmitted. It is therefore possible to combine these two events as is done in the example.

When the application receives new data from the remote host, it sends this data to the device by using

the function device_enqueue(). It is important to note that this example assumes that this function copies

the data into its own buffers. The data in the uip_appdata buffer will be overwritten by the next incoming

packet.

If the device’s queue is full, the application stops the data from the remote host by calling the uIP function

uip_stop(). The application can then be sure that it will not receive any new data until uip_restart() is called.

The application polling event is used to check if the device’s queue is no longer full and if so, the data ﬂow

is restarted with uip_restart().

1.7.5 A Simple Web Server

This example shows a very simple ﬁle server application that listens to two ports and uses the port number

to determine which ﬁle to send. If the ﬁles are properly formatted, this simple application can be used as a

web server with static pages. The implementation follows.

struct example5_state {

char

dataptr;

unsigned int dataleft;

};

void example5_init(void) {

uip_listen(HTONS(80));

uip_listen(HTONS(81));

Generated on Mon Jun 12 10:23:20 2006 for uIP 1.0 by Doxygen

1.7 Examples 11

}

void example5_app(void) {

struct example5_state

s = (struct example5_state)uip_conn->appstate;

if(uip_connected()) {

switch(uip_conn->lport) {

case HTONS(80):

s->dataptr = data_port_80;

s->dataleft = datalen_port_80;

break;

case HTONS(81):

s->dataptr = data_port_81;

s->dataleft = datalen_port_81;

break;

}

uip_send(s->dataptr, s->dataleft);

return;

}

if(uip_acked()) {

if(s->dataleft < uip_mss()) {

uip_close();

return;

}

s->dataptr += uip_conn->len;

s->dataleft -= uip_conn->len;

uip_send(s->dataptr, s->dataleft);

}

The application state consists of a pointer to the data that should be sent and the size of the data that is left

to send. When a remote host connects to the application, the local port number is used to determine which

ﬁle to send. The ﬁrst chunk of data is sent using

uip_send(). uIP makes sure that no more than MSS bytes

of data is actually sent, even though s->dataleft may be larger than the MSS.

The application is driven by incoming acknowledgments. When data has been acknowledged, new data

can be sent. If there is no more data to send, the connection is closed using uip_close().

1.7.6 Structured Application Program Design

When writing larger programs using uIP it is useful to be able to utilize the uIP API in a structured way.

The following example provides a structured design that has showed itself to be useful for writing larger

protocol implementations than the previous examples showed here. The program is divided into an uIP

event handler function that calls seven application handler functions that process new data, act on acknowl-

edged data, send new data, deal with connection establishment or closure events and handle errors. The

functions are called newdata(), acked(), senddata(), connected(), closed(), aborted(), and timedout(), and

needs to be written speciﬁcally for the protocol that is being implemented.

The uIP event handler function is shown below.

void example6_app(void) {

if(uip_aborted()) {

aborted();

}

if(uip_timedout()) {

timedout();

}

if(uip_closed()) {

closed();

}

Generated on Mon Jun 12 10:23:20 2006 for uIP 1.0 by Doxygen

1.7 Examples 13

s->textlen -= uip_conn->len;

s->textptr += uip_conn->len;

if(s->textlen == 0) {

switch(s->state) {

case STATE_HELLO:

s->state = STATE_WORLD;

s->textptr = "world!\n";

s->textlen = 7;

break;

case STATE_WORLD:

uip_close();

break;

}

static void senddata(void) {

struct example6_state

s = (struct example6_state

)uip_conn->appstate;

if(s->textlen > 0) {

uip_send(s->textptr, s->textlen);

}

The application state consists of a "state" variable, a "textptr" pointer to a text message and the "textlen"

length of the text message. The "state" variable can be either "STATE_WAITING", meaning that the

application is waiting for data to arrive from the network, "STATE_HELLO", in which the application is

sending the "Hello" part of the message, or "STATE_WORLD", in which the application is sending the

"world!" message.

The application does not handle errors or connection closing events, and therefore the aborted(), timedout()

and closed() functions are implemented as empty functions.

The connected() function will be called when a connection has been established, and in this case sets the

"state" variable to be "STATE_WAITING" and the "textlen" variable to be zero, indicating that there is no

message to be sent out.

When new data arrives from the network, the newdata() function will be called by the event handler func-

tion. The newdata() function will check if the connection is in the "STATE_WAITING" state, and if so

switches to the "STATE_HELLO" state and registers a 6 byte long "Hello " message with the connection.

This message will later be sent out by the senddata() function.

The acked() function is called whenever data that previously was sent has been acknowleged by the receiv-

ing host. This acked() function ﬁrst reduces the amount of data that is left to send, by subtracting the length

of the previously sent data (obtained from "uip_conn → len") from the "textlen" variable, and also adjusts

the "textptr" pointer accordingly. It then checks if the "textlen" variable now is zero, which indicates that all

data now has been successfully received, and if so changes application state. If the application was in the

"STATE_HELLO" state, it switches state to "STATE_WORLD" and sets up a 7 byte "world!\n" message

to be sent. If the application was in the "STATE_WORLD" state, it closes the connection.

Finally, the senddata() function takes care of actually sending the data that is to be sent. It is called by

the event handler function when new data has been received, when data has been acknowledged, when

a new connection has been established, when the connection is polled because of inactivity, or when a

retransmission should be made. The purpose of the senddata() function is to optionally format the data that

is to be sent, and to call the

uip_send() function to actually send out the data. In this particular example,

the function simply calls

uip_send() with the appropriate arguments if data is to be sent, after checking if

data should be sent out or not as indicated by the "textlen" variable.

It is important to note that the senddata() function never should affect the application state; this should only

be done in the acked() and newdata() functions.

Generated on Mon Jun 12 10:23:20 2006 for uIP 1.0 by Doxygen

14 The uIP TCP/IP stack

1.8 Protocol Implementations

The protocols in the TCP/IP protocol suite are designed in a layered fashion where each protocol performs

a speciﬁc function and the interactions between the protocol layers are strictly deﬁned. While the layered

approach is a good way to design protocols, it is not always the best way to implement them. In uIP, the

protocol implementations are tightly coupled in order to save code space.

This section gives detailed information on the speciﬁc protocol implementations in uIP.

1.8.1 IP — Internet Protocol

When incoming packets are processed by uIP, the IP layer is the ﬁrst protocol that examines the packet.

The IP layer does a few simple checks such as if the destination IP address of the incoming packet matches

any of the local IP address and veriﬁes the IP header checksum. Since there are no IP options that are

strictly required and because they are very uncommon, any IP options in received packets are dropped.

1.8.1.1 IP Fragment Reassembly

IP fragment reassembly is implemented using a separate buffer that holds the packet to be reassembled. An

incoming fragment is copied into the right place in the buffer and a bit map is used to keep track of which

fragments have been received. Because the ﬁrst byte of an IP fragment is aligned on an 8-byte boundary,

the bit map requires a small amount of memory. When all fragments have been reassembled, the resulting

IP packet is passed to the transport layer. If all fragments have not been received within a speciﬁed time

frame, the packet is dropped.

The current implementation only has a single buffer for holding packets to be reassembled, and therefore

does not support simultaneous reassembly of more than one packet. Since fragmented packets are uncom-

mon, this ought to be a reasonable decision. Extending the implementation to support multiple buffers

would be straightforward, however.

1.8.1.2 Broadcasts and Multicasts

IP has the ability to broadcast and multicast packets on the local network. Such packets are addressed

to special broadcast and multicast addresses. Broadcast is used heavily in many UDP based protocols

such as the Microsoft Windows ﬁle-sharing SMB protocol. Multicast is primarily used in protocols used

for multimedia distribution such as RTP. TCP is a point-to-point protocol and does not use broadcast or

multicast packets. uIP current supports broadcast packets as well as sending multicast packets. Joining

multicast groups (IGMP) and receiving non-local multicast packets is not currently supported.

1.8.2 ICMP — Internet Control Message Protocol

The ICMP protocol is used for reporting soft error conditions and for querying host parameters. Its main

use is, however, the echo mechanism which is used by the "ping" program.

The ICMP implementation in uIP is very simple as itis restricted to only implement ICMP echo messages.

Replies to echo messages are constructed by simply swapping the source and destination IP addresses of

incoming echo requests and rewriting the ICMP header with the Echo-Reply message type. The ICMP

checksum is adjusted using standard techniques (see RFC1624).

Since only the ICMP echo message is implemented, there is no support for Path MTU discovery or ICMP

redirect messages. Neither of these is strictly required for interoperability; they are performance enhance-

ment mechanisms.

Generated on Mon Jun 12 10:23:20 2006 for uIP 1.0 by Doxygen

剩余260页未读，继续阅读

静谧蓝

粉丝: 0
资源: 4

uIP 1.0嵌入式TCP/IP栈详解与模块指南

uip1.0完整源码+应用+uip1.0中文说明pdf

UIP协议的中文介绍

uIP学习资料（全）

uip1.0的源代码

uip webserver 安装

UIP_LLH_LEN

UIP_IPUDPH_LEN

正点原子 uip client

uboot如何支持uip

uip udp 发送完成

lwip和uip移植 lpc1788

uip_arp是什么意思？

appeye_uip_warning

modbus tcp uip

modbus tcp uip enc28j60

stm32f103rbt6 dm9000cep uip telnet功能实现

编写一个shell函数，该函数接收一个UIP作为参数，并根据UID显示对应的用户名

*(unsigned int*)

嵌入式网络库C++ 有哪些

tcp/ip协议在嵌入式的应用

最新资源

(unsigned int)