C6000 DSP NDK开发入门指南

需积分: 10 4 浏览量更新于2024-07-30 收藏 1.69MB PDF 举报

"NDK_userguide - 基于TIc6455DSP芯片的网络通信开发指南" 这篇文档是针对C6000 Network Development Kit (NDK)的入门指南，主要面向初学者和有一定经验的用户。NDK是一个用于在TI C6000 DSP系列芯片上进行网络通信开发的工具包。作者包括来自技术培训组织的Eric Wilbur、软件开发组织的Rafael de Souza以及数字现场应用部门的Mohsen Khayami。文档首先介绍了NDK的基本概念，并提供了下载评估版或购买NDK后新用户应遵循的步骤。通过阅读该指南和完成相应的实验，用户可以熟悉NDK的目录结构、文件组成以及工作代码示例，以解决初次使用时可能遇到的问题。文档的第二部分深入到网络基础知识，包括客户端-服务器模式的介绍，对网络通信的整体概述，以及OSI模型的解释。OSI模型是一个七层框架，用于标准化网络通信的不同层面。接着，文档详细阐述了TCP/IP协议栈如何实现OSI模型，并列出了网络通信中常见的术语和定义。此外，还讲解了以太网帧的结构，这是数据在网络中传输的基础。第三部分则探讨了EMAC（Ethemet MAC，以太网媒体访问控制）架构的概览。EMAC是主外围设备，它负责在物理层处理以太网通信，包括与物理介质交互、帧的接收和发送等。 NDK提供的项目辅助材料和源代码可以在指定的URL（http://www-s.ti.com/sc/techlit/spraax4.zip）上下载。这些资源对于深入理解和实践NDK中的网络开发至关重要，涵盖了从基本概念到实际操作的完整过程。 "NDK_userguide"是TI C6000 DSP用户进入网络通信开发领域的宝贵教程，通过学习，开发者能够掌握利用NDK进行高效网络编程所需的技能和知识，为基于TIc6455DSP芯片的项目奠定坚实基础。

SPRAAX4

3.4 EMAC Data Layer – Example (TX)

Here is a brief look into how a packet might be transmitted to the PHY. The EMAC uses buffer

descriptors to contain the proper information needed for a transfer – kind of like a DMA

configuration specifies source, destination and length information. There is a total of 8K bytes of

descriptor memory for both Rx and TX (512 descriptors at 16 bytes each). A single buffer

descriptor is 16 bytes long and contains the following:

Next Buf points to the next descriptor if you have one. Buf Ptr contains pBuf (the source of the

transfer). bufOff is the offset from Buf Ptr to the first piece of valid data (if necessary). bufLen is

the length of the buffer (256 bytes). pktLen is the length of the entire packet (multiple

descriptors).

Flags contain information/status about the packet and transfer.

The CPU has to fill in the descriptors before the HDP (head descriptor pointer) is written to. The

HDP is the “Head” (as opposed to the tail) of a linked list of descriptors. When the “head” is

written to, this initiates the transfer (via the EMAC’s DMA) from the L2 memory to the transmit

FIFO (and eventually to the PHY).

When the TXnHDP is written to, this initiates the transfer from L2 (in this case) to the EMAC

FIFOs. The EMAC then processes it (adding CRC, etc) and then sends it to the PHY. This

EMAC processing is automatic – no user intervention is required.

Again, the point here is that the NDK can perform all of this configuration and processing for you

vs. doing it manually. For most users, this is a huge time savings in their application

development.

EMAC Data Layer – Example (TX)

 Goal: send a 256-byte packet from L2 to the PHY

DST SRC LEN DATA

256 bytes

L2 SRAM

pBuf

 The EMAC has its own DMA controller.

What does it need to know to transfer pBuf to the PHY?

 Buffer Location (pBuf), Buffer Len (256 bytes), Next Bfr ptr, some flags (SOP, EOP)

 All transfer information is contained in the XMT Buffer Descriptor

PHY

Next Buf Desc

Buf Ptr

bufOff bufLen

Flags pktLen

Buffer

Descriptor

Memory (8K)

511

16 bytes

TXnHDP

TX DMA

EMAC

 When CPU writes TXnHDP (TX Head Descriptor Pointer, n = 0-7), this initiates the transfer

32-bit

So, how do you program this peripheral ?

14 Getting Started With the C6000 Network Development Kit (NDK)

SPRAAX4

4.2 Network Development Kit (NDK) Contents

The NDK is a set of libraries and example code that properly initializes and configures the

EMAC peripheral to perform whatever service is required by your application.

When installing the NDK, it is important to note that two separate downloads are required: (1)

the stack (platform-independent set of libraries, code); (2) the examples (platform-dependent

NDK support package). Many customers just download the stack and wonder “where did

client.pjt go?”. Well, client.pjt and many other examples are contained in the 2nd download that

is specific to the board/processor you are using.

The platform-dependent NDK support package is the software set that contains the example

projects and all the hardware libraries for each development kit supported by NDK. The user

should refer to

www.ti.com for latest support for each device/development board.

In other words, when you install NDK, you get all the core stack libraries, the documentation, the

main files for the examples (client.c, cfgdemo.c, helloWorld.c), the server files located at

<examples\tools\common\servers>, all the other nettools (webpage.c, console, hdlc, cgi) and the

winapps folder (used to test communications). However, the main board-specific client example

is NOT installed. The examples only get installed with the 2

download – the platform-

dependent NDK support package.

Network Development Kit (NDK)

 NDK is a set of libraries + example code that properly initialize/configure/operate

the hardware (EMAC) and perform all of the TCP/IP functionality through a set of

“socket” programming APIs (e.g. socket, bind, send, recv, etc.)

 $5K one-time licensing fee

 Provides a seamless interface to the physical layer (EMAC/PHY)

• HTTP

• TFTP

• Telnet

• DHCP

• Sockets Programming Services

• Internal stack functions

• Configures stack/services

and configures the EMAC

App

NDK/EMAC

Physical

NDK Model

• PPP

• DNS

• PPPoE

• many others

What does the user touch?

• Configuration

Do you know all of the details

of what is going on underneath ?

• Nope

Do you care ?

• Maybe…

Would you like to load an

example and play with it ?

• Of course…we’ll do that

in the upcoming lab…

Where can you purchase the NDK?

16 Getting Started With the C6000 Network Development Kit (NDK)

剩余84页未读，继续阅读

litao1973

粉丝: 0
资源: 1

C6000 DSP NDK开发入门指南

i_MX51_Android_R7_User_Guide.zip_andriod_android_imx51

c6000 Network Developer's Kit (NDK) Software user guide

NDK与Java_ Kotlin的互操作实践

NDK_PROJECT_PATH

Android NDK: Could not find application project directory ! Android NDK: Please define the NDK_PROJECT_PATH variable to point to it. /work4/lixinqi/lixinqi/ijkplayer/android-ndk-r10e/build/core/build-local.mk:143: *** Android NDK: Aborting . Stop.

if you are not using ndk, unset the ndk variable from android_ndk_home or lo

Project ERROR: You need to set the ANDROID_NDK_ROOT environment variable to point to your Android NDK. Could not read qmake configuration file D:/Qt/Qt5.14.2/5.14.2/android/mkspecs/android-clang/qmake.conf.

Android NDK: Could not find application project directory Android NDK: Please define the NDK_PROJET_PATH variable to point to it /home/android/ndk/android-ndk-r21/build/core/build-local.mk:151 ***Android NDK :Aborting . stop

export NDK_GCC

android.hardware.emvco-V1-ndk_platform

最新资源