μC/TCP-IP用户手册：TCP-IP经典教程

需积分: 0 53 浏览量更新于2024-07-28 收藏 530KB PDF 举报

"TCP/IP-Manual ucTCP/IP.pdf" 这篇文档是关于TCP/IP协议栈的用户手册，由Micriµm公司编撰，版本为V1.92，是一份详实的学习资料，适用于嵌入式系统。手册包含了TCP/IP协议的基本概念、工作原理以及在Micrium的嵌入式系统中的实现细节。 TCP/IP（传输控制协议/因特网协议）是互联网上通信的基础，由四层模型构成：应用层、传输层、网络层和数据链路层。在这个手册中，读者可以了解到各个层次的主要协议，如应用层的HTTP、FTP，传输层的TCP和UDP，网络层的IP，以及数据链路层的Ethernet等。 TCP是一种面向连接的、可靠的传输协议，它确保数据包按照正确的顺序到达目的地，并通过三次握手建立连接，四次挥手释放连接。而UDP则是无连接的，不保证数据的可靠传输，但其效率更高。 IP协议则负责将数据包发送到正确的目的地，它使用IP地址进行寻址。在实际网络中，由于网络的复杂性，IP还涉及到子网划分和路由选择。手册中可能会详细介绍如何在嵌入式系统中配置TCP/IP协议栈，包括网络接口的设置、IP地址的分配、端口的绑定、数据包的发送和接收等。此外，还可能涉及错误处理机制、性能优化方法以及与其他协议的交互。 Micriµm的ucTCP/IP是一个轻量级的TCP/IP协议栈，适合于资源有限的嵌入式环境。手册中会阐述如何集成和使用这个库，包括API函数的调用、错误处理和调试技巧。该手册警告读者，虽然内容尽可能准确，但可能存在错误，且规格可能会因功能或性能改进而不时更新。因此，使用者应确保使用的是最新版的手册，并理解Micrium对此不做任何明示或暗示的保修。手册版权属于Micriµm，未经许可，不得提取部分内容或修改PDF文件。软件的使用和复制需遵循特定的许可条款。此外，手册中提到的公司名称、产品名称可能是其各自公司的商标。这份TCP/IP手册对于学习和应用TCP/IP协议，特别是对于在嵌入式系统中实现TCP/IP功能的开发者来说，是一份极其有价值的参考资料。

Figure 1-3, Directory tree for µC/TCP-IP based project

All Micrium software is

laced under

icrium\Software

Processor specific header files. These are provided by

the chi

manufacturer and define CPU I/O re

isters.

All sample code is placed under the ‘EvalBoards’

sub-directory. Specific evaluation boards are further

characterized by the board manufacturer (Cogent) and

the specific board (CSB337) followed by the tools used

to build the example (IAR’s Embedded Workbench).

This directory contains files that are common to all

exam

les. BSP stands for ‘Board Su

ort Packa

e’.

This directory contains files that are specific to the

example, in this case, Example #1. This directory also

contains build specific files. The ‘Exe’ directory contains

the executable code that can be downloaded to the

target.

This directory contains files that are CPU and compiler

specific. The directory contains cpu_c.c, cpu_a.asm

and cpu_def.h.

This directory contains library files to replace standard

library functions such as memset(), memcpy(),

strcpy(), strcat(), etc. The reason we do this is to

simplify third party certification of your products.

This directory contains the processor specific source

files for the µC/OS-II ARM port running in ARM mode

and using the IAR toolchain.

This directory contains the processor independent

source files for the µC/OS-II RTOS.

This is the main directory for µC/TCP-IP.

µC/TCP-IP files related to network interfaces are placed under

the IF sub-directory. However, µC/TCP-IP currently only

supports Ethernet and this directory contains code which is

inde

endent of an

ecific Ethernet chi

All Network Interface Controllers (NIC) driver software is found in the NIC sub-

directory. The AT91RM9200 directory contains the code specific to this NIC.

µC/TCP-IP assumes the presence of an RTOS and the OS directory

contains ports to different RTOSs. The uCOS-II directory contains the

µC/OS-II I specific files for µC/TCP-IP. driver software is found in the NIC

sub-directory. The AT91RM9200 directory contains the code specific to this

NIC.

This directory contains the CPU, NIC and RTOS independent code for µC

TCP-IP.

1.01.01 BSP (Board Support Package)

As described in Figure 1-3, the BSP (Board Support Package) directory contains common code that can be used in

more than one example. Specifically, the BSP directory contains the following files:

bsp.c

bsp.h

net_bsp.c

net_bsp.h

net_isr.c

csb33x_lnk_ram.xcl

bsp.c and bsp.h

BSP stands for Board Support Package and we place ‘services’ that the board provides in such a file. In our

case, bsp.c contains I/O, timer initialization code, LED control code, and more. The I/Os that we use on

the board are initialized when BSP_Init() is called.

The concept of a BSP is to hide the hardware details from the application code. It is important that

functions in a BSP reflect the function and does not make references to any CPU specifics. For example,

the code to turn on an LED is called LED_On() and not csb337_led(). If you use LED_On() in your

code, you can easily port your code to another processor (or board) simply by rewriting LED_On() to

control the LEDs on a different board. The same is true for other services. You will also notice that BSP

functions are prefixed with the function’s group. LED services start with LED_, Timer services start with

Tmr_, etc. In other words, BSP functions don’t need to be prefixed by BSP_.

net_bsp.c, net_bsp.h and net_isr.c

This file contains code specific to the NIC (Network Interface Controller) used and other functions that are

dependent of the hardware. Specifically, this file contains code to read data from and write data to the NIC,

provide delay functions, control power to the NIC, get a time stamp and more.

csb33x_lnk_ram.xcl

This file contains the linker command file for the IAR toolchain. This file specifies where code and data is

placed in memory. In this case, all the code is placed in RAM to make it easier to debug. When you are

ready to deploy your product, you will most likely need to create a csb33x_lnk_flash.xcl to locate

your code in Flash instead of RAM.

1.01.02 Ex1

This directory contains the code for this example and consist of:

app.c

app_cfg.h

Ex1.*

fs_conf.h

includes.h

net_cfg.h

os_cfg.h

app.c

This file contains the application code for example #1. As with most C programs, code execution start at

main() which is shown in listing 1-1. The example #1 starts µC/TCP-IP and a set of services that run

on top of it. These services (like web server) are sold separately from µC/TCP-IP. See section 1.02 to

know how to disable some services in the example if you have not purchased them.

Listing 1-1

int main (void)

{

#if (OS_TASK_NAME_SIZE >= 16)

CPU_INT08U err;

#endif

BSP_Init(); /* (1) Initialize BSP. */

APP_TRACE_DEBUG("Initialize OS...\n");

OSInit(); /* (2) Initialize OS. */

/* (3) Create start task. */

OSTaskCreateExt( AppTaskStart,

(void *)0,

(OS_STK *)&AppStartTaskStk[APP_START_OS_CFG_TASK_STK_SIZE - 1],

APP_START_OS_CFG_TASK_PRIO,

(OS_STK *)&AppStartTaskStk[0],

APP_START_OS_CFG_TASK_STK_SIZE,

(void *)0,

OS_TASK_OPT_STK_CHK | OS_TASK_OPT_STK_CLR);

/* (4) Give a name to tasks. */

#if (OS_TASK_NAME_SIZE >= 16)

OSTaskNameSet(OS_TASK_IDLE_PRIO, "Idle task", &err);

OSTaskNameSet(OS_TASK_STAT_PRIO, "Stat task", &err);

OSTaskNameSet(APP_START_OS_CFG_TASK_PRIO, "Start task", &err);

#endif

APP_TRACE_DEBUG("Start OS...\n");

OSStart(); /* (5) Start OS. */

}

L1-1(1) We start by initializing the I/Os we’ll be using on this board as well as the µC/OS-II tick interrupt

and the AT91RM9200’s interrupt controller.

L1-1(2) The example code assumes the presence of an RTOS called µC/OS-II and OSInit() is used to

initialize µC/OS-II.

L1-1(3) µC/OS-II requires that we create at least ONE application task. This is done by calling

OSTaskCreateExt() and specifying the task start address, the top-of-stack to use for this task, the

priority of the task and a few other arguments.

L1-1(4) µC/OS-II allows you to assign names to tasks that have been created. We thus assign a name to the

application task. These names are used mostly during debug. In fact, task names are displayed during

debug when using IAR’s C-Spy debugger (or other µC/OS-II aware debuggers).

L1-1(5) In order to start multitasking, your application needs to call OSStart(). OSStart() determines

which task, out of all the tasks created, will get to run on the CPU. In this case, µC/OS-II will run

AppTaskStart().

The first, and only ‘application’ task that µC/OS-II runs is shown in listing 1-2.

Listing 1-2

static void AppTaskStart (void *p_arg)

{

(void)p_arg; /* Prevent compiler warning. */

APP_TRACE_DEBUG("Initialize interrupt controller...\n");

BSP_InitIntCtrl(); /* (1) Initialize interrupt controller. */

APP_TRACE_DEBUG("Initialize OS timer...\n");

Tmr_Init(); /* (2) Initialize OS timer. */

#if (OS_TASK_STAT_EN > 0)

APP_TRACE_DEBUG("Initialize OS statistic task...\n");

OSStatInit(); /* (3) Initialize OS statistic task. */

#endif

#if APP_FS_ENABLED

AppInit_FS(); /* (4) Initialize file system. */

#endif

AppInit_TCPIP(); /* (5) Initialize TCP/IP stack. */

#if APP_DHCPc_ENABLED

AppInit_DHCPc(); /* (6) Initialize DHCP client. */

#endif

#if APP_HTTPs_ENABLED

APP_TRACE_DEBUG("Initialize HTTP server...\n");

HTTPs_Init(); /* (7) Initialize HTTP server. */

#endif

#if APP_FTPs_ENABLED

APP_TRACE_DEBUG("Initialize FTP server...\n");

/* (7) Initialize FTP server. */

FTPs_Init(AppIP_Addr, FTPs_CFG_DTP_IPPORT);

#endif

#if APP_TFTPs_ENABLED

APP_TRACE_DEBUG("Initialize TFTP server...\n");

TFTPs_Init(); /* (7) Initialize TFTP server. */

#endif

#if APP_DNSc_ENABLED

DNSc_Init(AppIP_DNS_Srvr); /* (8) Initialize DNS client. */

AppTest_DNSc(); /* Test DNS client. */

#endif

#if APP_FTPc_ENABLED

AppTest_FTPc(); /* (8) Test FTP client. */

#endif

#if APP_POP3c_ENABLED

AppTest_POP3c(); /* (8) Test POP3 client. */

#endif

#if APP_SMTPc_ENABLED

AppTest_SMTPc(); /* (8) Test SMTP client. */

#endif

#if APP_SNTPc_ENABLED

AppTest_SNTPc(); /* (8) Test SNTP client. */

#endif

APP_TRACE_DEBUG("Create application task...\n");

AppTaskCreate(); /* (9) Create application task. */

APP_TRACE_DEBUG("\n******************************************************************");

APP_TRACE_DEBUG("\n* *");

APP_TRACE_DEBUG("\n* Micrium uC/TCP-IP TTCP Performance measurement *");

APP_TRACE_DEBUG("\n* AT91RM9200 on Cogent CSB337 SDK *");

APP_TRACE_DEBUG("\n* *");

APP_TRACE_DEBUG("\n******************************************************************");

APP_TRACE_DEBUG("\n");

TTCP_Init(); /* (10)Initialize TTCP application */

#endif

LED_Off(1);

LED_Off(2);

LED_Off(3);

while (DEF_YES) { /* Task body, always written as an infinite loop. */

OSTimeDlyHMSM(0, 0, 0, 100);

}

L1-2(1) AppTaskStart() starts off by initializing the AT91RM9200 interrupt controller and start handling

interruptions.

L1-2(2) Enable the timer tick source from the microcontroller. µC/OS-II needs a time base to determine

when it’s time to preempt a task and let the next task scheduled to run. Details as to how this is done

can be found in the µC/OS-II book.

L1-2(3) If you set OS_TASK_STAT_EN to 1 in os_cfg.h then the µC/OS-II statistic task is initialized by

calling OSStatInit(). OSStatInit() basically figures out how fast the CPU is running in

order to determine how much CPU usage your application will be consuming. Details as to how this

is done can be found in the µC/OS-II book.

L1-2(4) Initialize File System. This is optional. File System is used by some µC/TCP-IP services. If you

purchased the µC/FTPs, µC/HTTPs or µC/TFTPs, you also need µC/FS.

L1-2(5) We then initialize the TCP/IP stack by calling NetInit(). NetInit() initializes all of

µC/TCP-IP’s data structures and creates two tasks. One task waits for packets to be received and the

other task manages timers.

剩余144页未读，继续阅读

k14789

粉丝: 2
资源: 3

μC/TCP-IP用户手册：TCP-IP经典教程

思科《TCP-IP路由技术卷2》.PDF

基于TCP-IP协议实现上位机对UR机器人的远程控制.pdf

TCP-IP Illustrated(1、2、3卷)中文版

tf6310-tcp-ip.exe

计算机数据包分片命令,TCP-IPIP数据报分片实验

ip6tables中的“-A FORWARD -o eth1 -p tcp -m tcp --tcp-flags SYN,RST SYN -m comment --comment "!fw3: Zone wan MTU fixing" -j TCPMSS --clamp-mss-to-pmtu”中的TCPMSS 如何修改TCP SYN包的最大字段大小

tshark 构造checksum错误的包

openwrt中的ip6tables中的“-A FORWARD -o eth1 -p tcp -m tcp --tcp-flags SYN,RST SYN -m comment --comment "!fw3: Zone wan MTU fixing" -j TCPMSS --clamp-mss-to-pmtu”

iptables -t nat -A PREROUTING -i eth1 -d 192.168.100.1 -p tcp -dport 22 -j DNAT --to-destination 192.168.110.110:22怎么修改

tcp-ip技术大全

最新资源