Nucleus PLUS 网络手册：TCP/IP 实现与使用指南

需积分: 9 128 浏览量更新于2024-07-21 收藏 1.72MB PDF 举报

"Nucleus NET Reference Manual" 《Nucleus NET Reference Manual》是Accelerated Technology出版的一本关于TCP/IP Nucleus PLUS网络工具的手册，它详细阐述了这些工具的安装与运行方法。该手册是为那些需要在嵌入式系统中使用Nucleus PLUS内核进行网络功能开发的工程师们准备的。Nucleus PLUS是一个小巧、高效且实时的嵌入式操作系统内核，而Nucleus NET则提供了其网络通信的支持。手册内容可能包括但不限于以下几个方面： 1. **TCP/IP协议栈**：Nucleus NET实现了完整的TCP/IP协议栈，包括TCP（传输控制协议）、IP（互联网协议）、UDP（用户数据报协议）以及ICMP（因特网控制消息协议）等，使得嵌入式设备能够接入并通信于互联网。 2. **网络接口驱动**：手册会介绍如何配置和管理各种网络接口，如以太网、Wi-Fi或蓝牙等，以便设备能够通过这些接口进行网络连接。 3. **安装过程**：详细步骤指导用户如何在目标硬件上安装Nucleus NET组件，包括编译环境的设置、库文件的集成和配置文件的定制。 4. **网络服务**：Nucleus NET可能支持HTTP、FTP、SMTP等常见网络服务的实现，手册会解释如何启动和配置这些服务，以及如何处理客户端请求。 5. **错误处理和调试**：提供错误代码列表和调试指南，帮助开发者识别和解决网络操作过程中可能出现的问题。 6. **示例和应用**：包含实际的程序示例，展示如何在代码中使用Nucleus NET的API进行网络编程，这些例子可能涵盖了连接、发送和接收数据、创建服务器等基本操作。 7. **符号和样式约定**：手册中采用了特定的字体和格式来表示程序代码、文件名、菜单项和交互式显示，以方便读者快速识别。 8. **其他相关文档**：提到了《Nucleus PLUS Reference Manual》和《Nucleus PLUS Internals》，这两本书分别对Nucleus PLUS内核的操作和实现细节进行了详细讲解。 9. **商标信息**：书中指出了一些知名商标，如MS-DOS、UNIX和IBM PC，这些商标可能与Nucleus NET的兼容性或应用场景有关。 10. **技术支持**：手册最后提供了Accelerated Technology的联系方式，用户在遇到问题时可以寻求他们的专业帮助。通过这份手册，开发者可以获得全面的技术支持，有效地在Nucleus PLUS平台上构建和优化网络应用程序，从而提升嵌入式系统的网络性能和可靠性。

Nucleus NET Reference Manual

The following sections describe the use of Nucleus NET in general. Nucleus NET

provides a series of enhancements over the commonly available interfaces to typical

TCP/IP networking software implementations. These enhancements provide for more

compact network processing. By providing memory allocation facilities, Nucleus NET

can greatly reduce the amount of time spent processing network requests on an embedded

host. However, the overall throughput of the network traffic is dictated by the slowest

host involved in the network communication (notwithstanding the network traffic in

general).

Application Development Overview

Nucleus NET applications are written within the context of a Nucleus PLUS system. This

means that full multi-tasking mechanisms are expected and required. Nucleus NET itself

uses two tasks. One task is responsible for processing all events generated by the stack.

An example of such an event would be the retransmission of a TCP packet. The second

task processes received packets. See Chapter 6 for more on the configuration of the

Nucleus PLUS setup.

Users of the Nucleus NET protocol stack access network services from a task. That is,

when a Nucleus NET service is requested, it executes in the context of the requesting

task.

Nucleus NET provides for both blocking and non-blocking services. Some services block

by default, others do not. If non-blocking services are required, Nucleus NET provides

the

NU_Fcntl service. Non-blocking services return immediately whether the request is

completed or not. Therefore, it is possible in a non-blocking read request that no bytes

will be returned.

Write services only block when there are not enough resources (buffer space) available to

send the data. The task is resumed when resources become available and the write

request can be satisfied. Note that write services always block when resources are not

available. The

NU_Fcntl cannot be used to make a write request non-blocking.

Active connection requests are always blocked. A client performs an active connection

request. Passive connection requests made by a TCP server can be either blocking or

non-blocking. Except for the passive connection request of a TCP server, control will

never return if a connection is not established. When a write request is made, the task

may assume that the data will be transferred to the specified recipient (unless a parameter

error was detected by the protocol stack, e.g., an incorrect socket identifier was

specified).

Details describing the use of the various Nucleus NET capabilities are described in

Chapter 3, Functional Description and Chapter 4, Nucleus NET Services.

Installing Nucleus NET

The installation of Nucleus NET varies with the target platform. Please refer to the

Target Specific Notes that you received with Nucleus NET for complete installation

instructions.

Chapter 2 - Getting Started

Network Initialization

Before using any of the network services the stack and the physical layer devices

(ethernet controllers, UARTS, etc.) must be initialized. Network Initialization should be

performed from within a task, i.e., not in the Nucleus PLUS

Application_Initialize

routine. Preferably, network initialization should be

performed in the first task to execute. All network applications must call

NU_Init_Net

and

NU_Init_Devices. Additionally if a host is going to discover it’s IP address

dynamically it may have to call one or more of the following functions:

NU_Rarp,

NU_Dhcp, or NU_Bootp. All of the aforementioned function calls should occur after the

NU_Init_Devices call. When Nucleus NET initialization is requested, data structures

for the protocol stack are initialized and control returns to the requestor. Nucleus NET

initialization is performed by simply calling

NU_Init_Net.

Nucleus NET handles multiple network interfaces and before calling

NU_Init_Devices

the

NU_Device

structure should be filled out for each device that is to be used in the

physical layer. Once the device structure is filled with the appropriate values, the

NU_Init_Devices function is called. This function initializes the data structures, adds

each device to the list of devices, calls the devices initialization function, and attaches IP

addresses to the device. Data structures for connections, data transfers, etc., are not

allocated until subsequent connection, read, and write requests are made.

Transferring Data Using Nucleus NET

Nucleus NET can be used in a number of ways. A TCP connection or connections can be

made and data transferred in the standard socket-like manner permitted by Nucleus NET.

The standard UDP interface can be used, or the Raw IP interface can be used.

In the following paragraphs you will note that in order to begin communications you

must “open a socket”. This process is preceded by building an address structure to

specify the address of the node you wish to connect or send data to, and an address

indicating your node on the network (in certain cases). The next paragraph describes the

data structures and process necessary to build an address.

Building an Address Structure

An address structure is built using the predefined structure

addr_struct

The

addr_struct

contains information about a node on the network including its family

type, port number, IP number, and name.

Chapter 2 - Getting Started

Server

 Create a socket (NU_Socket)

 Bind the Server port and IP address (

NU_Bind)

 Perform a Listen call to establish the number of simultaneous requests that can be

queued (

NU_Listen

)

 Perform an Accept service call to “wait” for client connections (

NU_Accept)

 After the Accept service call returns (i.e., a connection has been established) data

can be transferred (control returns from

NU_Accept)

 Transfer data (

NU_Send and NU_Recv)

 Close the connection (

NU_Close)

Client

 Create a socket (NU_Socket)

 Perform a Connect service call (

NU_Connect)

 After the Connect service call returns (i.e., a connection has been established) data

can be transferred (control returns from

NU_Connect)

 Transfer data (

NU_Send and NU_Recv)

 Close the connection (

NU_Close)

Standard UDP Usage

UDP is inherently connectionless. However, it is expected that in general, both sides of a

data transfer are aware of the transfer, and port numbers have been predefined. The

operation for a sender and receiver only differ in the service calls that are made. That is,

both the sending and receiving of data require a full address specification of the recipient

and sender respectively. Data transfer over UDP is simply performed by using the

appropriate interfaces specified in Chapter 4.

UDP can operate in both server and client mode. Additionally, it can be used to simply

communicate from one machine to another without the notion of a server. However, in

order to receive a Datagram, a port must be specified, and the application must have

issued a

NU_Recv_From service call before the sender actually sends the packet in

order for the UDP to process the Datagram.

The steps involved in transferring data via UDP are:

Server

 Create a socket

(NU_Socket)

 Bind the local server address to the socket

(NU_Bind)

 Wait on client’s data

(NU_Recv_From)

 Send data — optional

(NU_Send_To)

 Close the socket (

NU_Close

)

Nucleus NET Reference Manual

Client

 Create a socket (NU_Socket)

 Send data to the server

(NU_Send_To)

 Receive data — optional

(NU_Recv_From)

 Close the socket

(NU_Close)

Raw IP Usage

Raw IP is connectionless. However, it is expected that in general, both sides of a data

transfer are aware of the transfer, and that the protocol being used has been established.

The operation for a sender and receiver only differ in the service calls that are made. Data

transfer over Raw IP is simply performed by using the appropriate interfaces specified in

Chapter 4.

Raw IP can operate in both server and client mode. Additionally, it can be used to simply

communicate from one machine to another without the notion of a server. However, in

order to receive a Datagram, a protocol must be specified, and the application must have

issued a

NU_Recv_From_Raw service call before the sender actually sends the packet in

order for Raw IP to process the datagram.

The necessary steps involved in transferring data via Raw IP are:

Server

 Create a socket (NU_Socket)

 Wait on client’s data (

NU_Recv_From_Raw)

 Send data — optional (

NU_Send_To_Raw)

 Close the socket (

NU_Close_Socket)

Client

 Create a socket (NU_Socket)

 Send data to the server (

NU_Send_To_Raw)

 Receive data — optional (

NU_Recv_From_Raw)

 Close the socket (

NU_Close_Socket)

Configuration Options

Target environments as well as the TCP/IP protocol stack require certain configuration

information in order to function properly. Configuration options are conveniently isolated

in separate include files for easy modification. The files and their associated

configuration items are provided in the following section.

Network Configuration

The structure

NU_DEVICES

is used to add multiple interfaces into the Nucleus NET

physical Layer. Parameters for setting up the Nucleus NET interfaces are specified in

the structure

NU_DEVICES.

The following is a discussion of this data structure.

剩余127页未读，继续阅读

yangzhao0001

粉丝: 232
资源: 39

Nucleus PLUS 网络手册：TCP/IP 实现与使用指南

Nucleus NET Reference Manual

nucleus 源代码

Nucleus FILE Manual(文件手册)

Nucleus PLUS中文参考手册.pdf

中文Nucleus PLUS Reference Manual

Nucleus-file-manual

Nucleus PLUS 参考手册 源码分析

NUCLEUS_PLUS_Reference_Manual.rar_nucleus_plus

Nucleus NET Extended Protocol.pdf

Nucleus Plus 源码分析与参考手册

最新资源

Nucleus PLUS 参考手册源码分析