Raw TCP/IP interface for lwIP
Authors: Adam Dunkels, Leon Woestenberg, Christiaan Simons
lwIP provides three Application Program's Interfaces (APIs) for programs
to use for communication with the TCP/IP code:
* low-level "core" / "callback" or "raw" API.
* higher-level "sequential" API.
* BSD-style socket API.
The sequential API provides a way for ordinary, sequential, programs
to use the lwIP stack. It is quite similar to the BSD socket API. The
model of execution is based on the blocking open-read-write-close
paradigm. Since the TCP/IP stack is event based by nature, the TCP/IP
code and the application program must reside in different execution
contexts (threads).
The socket API is a compatibility API for existing applications,
currently it is built on top of the sequential API. It is meant to
provide all functions needed to run socket API applications running
on other platforms (e.g. unix / windows etc.). However, due to limitations
in the specification of this API, there might be incompatibilities
that require small modifications of existing programs.
** Threading
lwIP started targeting single-threaded environments. When adding multi-
threading support, instead of making the core thread-safe, another
approach was chosen: there is one main thread running the lwIP core
(also known as the "tcpip_thread"). The raw API may only be used from
this thread! Application threads using the sequential- or socket API
communicate with this main thread through message passing.
As such, the list of functions that may be called from
other threads or an ISR is very limited! Only functions
from these API header files are thread-safe:
- api.h
- netbuf.h
- netdb.h
- netifapi.h
- sockets.h
- sys.h
Additionaly, memory (de-)allocation functions may be
called from multiple threads (not ISR!) with NO_SYS=0
since they are protected by SYS_LIGHTWEIGHT_PROT and/or
semaphores.
Only since 1.3.0, if SYS_LIGHTWEIGHT_PROT is set to 1
and LWIP_ALLOW_MEM_FREE_FROM_OTHER_CONTEXT is set to 1,
pbuf_free() may also be called from another thread or
an ISR (since only then, mem_free - for PBUF_RAM - may
be called from an ISR: otherwise, the HEAP is only
protected by semaphores).
** The remainder of this document discusses the "raw" API. **
The raw TCP/IP interface allows the application program to integrate
better with the TCP/IP code. Program execution is event based by
having callback functions being called from within the TCP/IP
code. The TCP/IP code and the application program both run in the same
thread. The sequential API has a much higher overhead and is not very
well suited for small systems since it forces a multithreaded paradigm
on the application.
The raw TCP/IP interface is not only faster in terms of code execution
time but is also less memory intensive. The drawback is that program
development is somewhat harder and application programs written for
the raw TCP/IP interface are more difficult to understand. Still, this
is the preferred way of writing applications that should be small in
code size and memory usage.
Both APIs can be used simultaneously by different application
programs. In fact, the sequential API is implemented as an application
program using the raw TCP/IP interface.
--- Callbacks
Program execution is driven by callbacks. Each callback is an ordinary
C function that is called from within the TCP/IP code. Every callback
function is passed the current TCP or UDP connection state as an
argument. Also, in order to be able to keep program specific state,
the callback functions are called with a program specified argument
that is independent of the TCP/IP state.
The function for setting the application connection state is:
- void tcp_arg(struct tcp_pcb *pcb, void *arg)
Specifies the program specific state that should be passed to all
other callback functions. The "pcb" argument is the current TCP
connection control block, and the "arg" argument is the argument
that will be passed to the callbacks.
--- TCP connection setup
The functions used for setting up connections is similar to that of
the sequential API and of the BSD socket API. A new TCP connection
identifier (i.e., a protocol control block - PCB) is created with the
tcp_new() function. This PCB can then be either set to listen for new
incoming connections or be explicitly connected to another host.
- struct tcp_pcb *tcp_new(void)
Creates a new connection identifier (PCB). If memory is not
available for creating the new pcb, NULL is returned.
- err_t tcp_bind(struct tcp_pcb *pcb, ip_addr_t *ipaddr,
u16_t port)
Binds the pcb to a local IP address and port number. The IP address
can be specified as IP_ADDR_ANY in order to bind the connection to
all local IP addresses.
If another connection is bound to the same port, the function will
return ERR_USE, otherwise ERR_OK is returned.
- struct tcp_pcb *tcp_listen(struct tcp_pcb *pcb)
Commands a pcb to start listening for incoming connections. When an
incoming connection is accepted, the function specified with the
tcp_accept() function will be called. The pcb will have to be bound
to a local port with the tcp_bind() function.
The tcp_listen() function returns a new connection identifier, and
the one passed as an argument to the function will be
deallocated. The reason for this behavior is that less memory is
needed for a connection that is listening, so tcp_listen() will
reclaim the memory needed for the original connection and allocate a
new smaller memory block for the listening connection.
tcp_listen() may return NULL if no memory was available for the
listening connection. If so, the memory associated with the pcb
passed as an argument to tcp_listen() will not be deallocated.
- struct tcp_pcb *tcp_listen_with_backlog(struct tcp_pcb *pcb, u8_t backlog)
Same as tcp_listen, but limits the number of outstanding connections
in the listen queue to the value specified by the backlog argument.
To use it, your need to set TCP_LISTEN_BACKLOG=1 in your lwipopts.h.
- void tcp_accepted(struct tcp_pcb *pcb)
Inform lwIP that an incoming connection has been accepted. This would
usually be called from the accept callback. This allows lwIP to perform
housekeeping tasks, such as allowing further incoming connections to be
queued in the listen backlog.
ATTENTION: the PCB passed in must be the listening pcb, not the pcb passed
into the accept callback!
- void tcp_accept(struct tcp_pcb *pcb,
err_t (* accept)(void *arg, struct tcp_pcb *newpcb,
err_t err))
Specified the callback function that should be called when a new
connection arrives on a listening connection.
- err_t tcp_connect(struct tcp_pcb *pcb, ip_addr_t *ipaddr,
u16_t port, err_t (* connected)(void *arg,
struct tcp_pcb *tpcb,
err_t err));
Sets up the pcb to connect to the remote host and sends the
initial SYN segment which opens the connection.
The tcp_connect() function returns immediately; it does not wait for
the connection to be properly setup. Instead, it will call the
function specified as the fourth argument (the "connected" argument)
when the connection is established. If the connection could not be
properly established, either because the other host refused the
connection or because the other host didn't answer, the "err"
callback function of this pcb (registered with tcp_err, see below)
will be called.
The tcp_connect() function can return ERR_MEM if no memory is
available for enqueueing the SYN segment. If the SYN indeed was
enqueued successfully, the tcp_connect() function returns ERR_OK.
--- Sending TCP data
TCP data is sent by enqueueing the data with a call to
没有合适的资源?快使用搜索试试~ 我知道了~
兆易创新单片机MCU,GD32FFPRTGU6国产替换ST,GD32FFPRTGU6固件库
共918个文件
h:352个
c:301个
txt:95个
需积分: 5 0 下载量 137 浏览量
2024-04-10
11:40:13
上传
评论
收藏 3.39MB RAR 举报
温馨提示
内容包含: 1、完整工程的固件库,代码库 2、该型号单片的寄存器和函数中文说明(pdf文件)
资源推荐
资源详情
资源评论
收起资源包目录
兆易创新单片机MCU,GD32FFPRTGU6国产替换ST,GD32FFPRTGU6固件库 (918个子文件)
usbd_msc.Debug.cspy.bat 2KB
HID_keyboard.Debug.cspy.bat 2KB
Custom_HID.Debug.cspy.bat 2KB
usbd_printer.Debug.cspy.bat 2KB
Project.GD32F30X_CL.cspy.bat 2KB
CDC_ACM.Debug.cspy.bat 2KB
HID_IAP.Debug.cspy.bat 2KB
HID_LPM.Debug.cspy.bat 2KB
usbd_dfu.Debug.cspy.bat 2KB
keilkilll.bat 459B
LCD.bin 45KB
LED.bin 2KB
CDC_ACM.pbd.browse 1.44MB
usbd_msc.pbd.browse 1.21MB
Project.pbd.browse 1.18MB
Custom_HID.pbd.browse 1.18MB
gd32f30x_enet.c 152KB
picture.c 140KB
mib2.c 103KB
ff.c 98KB
sdcard.c 94KB
gd32f30x_timer.c 76KB
sockets.c 71KB
dhcp.c 65KB
tcp_in.c 60KB
ppp.c 57KB
lcp.c 56KB
tcp.c 54KB
etharp.c 52KB
tcp_out.c 51KB
api_msg.c 47KB
gd32f30x_rcu.c 44KB
msg_in.c 43KB
pbuf.c 39KB
ipcp.c 38KB
system_gd32f30x.c 35KB
auth.c 35KB
gd32f30x_adc.c 35KB
udp.c 34KB
ip.c 33KB
ppp_oe.c 33KB
usbh_std.c 32KB
gd32f30x_can.c 31KB
dns.c 31KB
test_tcp_oos.c 31KB
gd32f30x_fmc.c 31KB
ccsbcs.c 29KB
ip_frag.c 29KB
mib_structs.c 29KB
gd32f30x_exmc.c 28KB
igmp.c 27KB
gd32f30x_usart.c 26KB
gd32f30x_sdio.c 25KB
usbd_std.c 25KB
usbh_core.c 25KB
usb_core.c 25KB
chap.c 24KB
api_lib.c 24KB
gd32f30x_spi.c 24KB
mem.c 24KB
fsm.c 23KB
usbh_ctrl.c 23KB
netif.c 23KB
gd32f30x_dma.c 23KB
usbd_std.c 22KB
gd32f30x_i2c.c 22KB
msg_out.c 21KB
test_tcp.c 21KB
exmc_nandflash.c 19KB
usbh_int.c 19KB
gd32f30x_gpio.c 19KB
fat.c 19KB
vj.c 18KB
fs.c 18KB
autoip.c 18KB
usbd_int.c 18KB
ioman.c 18KB
file.c 18KB
dfu_core.c 17KB
asn1_dec.c 16KB
pap.c 16KB
gd32f307z_lcd_eval.c 16KB
iap_core.c 15KB
bbb_scsi_driver.c 15KB
tcpip.c 15KB
slipif.c 14KB
dir.c 14KB
init.c 14KB
memp.c 14KB
asn1_enc.c 14KB
timers.c 13KB
gd32f30x_dac.c 13KB
inet_chksum.c 13KB
usbd_core.c 13KB
ili9320.c 13KB
cdc_acm_core.c 12KB
custom_hid_core.c 12KB
exmc_norflash.c 12KB
icmp.c 12KB
md5.c 11KB
共 918 条
- 1
- 2
- 3
- 4
- 5
- 6
- 10
资源评论
weixin_42682147
- 粉丝: 0
- 资源: 49
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- Kepware.KEPServerEX.v4.264.401.Incl.Keygen-SSG
- 行人重识别-通过顺序决策实现跨域行人重识别算法-附项目源码-优质项目实战.zip
- HTML、CSS制作家乡介绍网页.zip
- 361050291.apk
- 华硕B250 PLUS支持6789代BIOS
- 基于javaScript开发的图书管理系统+数据库+源码+项目展示+开发文档(毕业设计&课程设计&项目开发)
- HTML+CSS制作的个人博客网页 2.zip
- 华硕B250M-PIXIU支持6789代BIOS
- c# winfrom 音量控制 静音
- 【OpenHarmony】 ArkTS 语法基础 ② ( ArkTS 自定义组件 )
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功