NSP 1.00.00.09 GA Release Notes

This NSP Release contains ethernet driver support for the evmOMAPL138 ARM9 and and the evm6748 C674X DSP. It also provides network examples for both DSP/BIOS 5.x and SYS/BIOS 6.x for the evm6748 C674X DSP, as well as SYS/BIOS 6.x examples which run on the evmOMAPL138 ARM9 processor.

Introduction, Documentation, What's New, Upgrade Info, Compatibility Information, Device Support, Validation Info, Known Issues, Examples, Rebuilding The Driver Library, Version Information, Technical Support.

Introduction

The Network Development Kit Support Package (NSP) contains ethernet driver code, libraries and network examples for various TI platforms. It is meant to supplement the Network Development Kit (NDK), which consists of the platform independent networking code.

The NSP includes demonstration software which showcases the OMAPL138 DSP's capabilities across a range of network enabled applications, including both DSP/BIOS 5.x and SYS/BIOS 6.x.

The NDK examples found in this NSP can serve as a rapid prototype platform for the development of network and packet processing applications, or to add network connectivity to existing applications for communications, configuration, and control. Using the components provided in the NDK and NSP, developers can quickly move from development concepts to working implementations attached to the network..

Documentation

The following documents provide an overview of the NDK, the networking programming API, and how to port the software to other platforms (The following documents have not been updated to reflect changes in this release).

NDK User's Guide: Documents the NDK basics, and describes how to develop or port a network-enabled application. It also describes how to customize the network environment to fit your embedded environment.
NDK Programmer's Reference Guide: Describes the NDK library API calls in detail. It also includes a description of the stack's internal object based API functions.
NDK Support Package Ethernet Driver Design Guide: Describes the NIMU based architecture of the Ethernet Drivers packaged in the NSPs.

In addition, users are encouraged to monitor (and contribute to!) the TI Embedded Processors Wiki.

Release notes from previous releases are also available in the release website.

What's New

New Features

Initial release
Driver is now compatible with both SYS/BIOS 6.x and DSP/BIOS 5.x (see Compatibility Information for exact versions)
Added support for the ARM9 processor
All example files are now included in this NSP
CCSv4 example projects

Bug Fixes

SDOCM00075002 - cfgdemo - web activity causes timeout and stack reboot. Program crashes due to driver init failures
SDOCM00075001 - Client example crashes upon stack reboot for BIOS 6 - cannot delete Task in BLOCKED or RUNNING state
SDOCM00074898 - cfgdemo example app crashes when changing the default password

Upgrade Information

None.

Compatibility Information

This release must be used with following component versions (or higher):

BIOS

DSP/BIOS 5.41.05.20
OR

SYS/BIOS 6.30.02.42

CCS 4.2
XDCtools 3.20.03.63
C674X: C6000 Code Generation Tools 7.0.0
ARM9: TMS470 Code Generation Tools 4.6.1

Device Support

This release supports the following devices:

C674x: big and little endian, COFF only
ARM9: ELF format only

Validation

This release was built and validated against using the following software components:

DSP/BIOS 5.41.05.20
SYS/BIOS 6.30.02.42
NDK 2.20.00.10
CCS 4.2
XDCtools 3.20.03.63
Red Hat Enterprise Linux 4 (SMP)
Pre-built binaries were built with the following toolchains:

C674X: C6000 Code Generation Tools 7.0.0
ARM9: TMS470 Code Generation Tools 4.6.1

This release was validated using the following hardware platforms:

OMAP-L138 EVM

Known Issues

None.

Examples

NDK examples may be found in the "packages/ti/ndk/examples" directory . The examples are stored as CCSv4 archive files that are meant to be imported into CCSv4.

The following set up examples archives are currently shipped with the NSP. You should choose one of the following archives depending on your hardware platform (evmOMAPL138 or evm6748) and version of BIOS (DSP/BIOS 5.x or SYS/BIOS 6.x) you are using:

ndk_evm6748_bios5_examples.zip - C674X DSP examples which build using DSP/BIOS 5.x

ndk_evm6748_bios6_examples.zip - C674X DSP examples which build using SYS/BIOS 6.x

ndk_omapl138_arm9_examples.zip - ARM9 examples which build using SYS/BIOS 6.x

Importing The NDK Example Projects Into CCS 4.2

Before following the steps in this section, please ensure that all dependent software that is listed in the section Compatibility Information has been installed.

If you will be using DSP/BIOS 5.x, you must define environment variables called "NDK_INSTALL_DIR" and "NSP_INSTALL_DIR" (NOTE: this step does not apply to SYS/BIOS 6.x users!). These variables must point to where the NDK 2.20 and nsp_1_00_00_09 releases were installed, and are referenced in the NDK examples which build using DSP/BIOS 5.x.

For example, if your NDK installation is located at:

C:\Program Files\Texas Instruments\ndk_2_20_00_19

Then you should set this variable to be:

NDK_INSTALL_DIR = C:\Program Files\Texas Instruments\ndk_2_20_00_19

Similarly, if your nsp_1_00_00_09 is located at:

C:\Program Files\Texas Instruments\nsp_1_00_00_09

Then you should set this variable to be:

NSP_INSTALL_DIR = C:\Program Files\Texas Instruments\nsp_1_00_00_09

Open CCSv4 and create a new workspace.

From within the C/C++ View, select the menu option "Project -> Import Existing CCS/CCE Eclipse Project"

In the window that appears, click "Select Archive File", then click the "browse" button.

Navigate to the location where you installed the nsp_1_00_00_09. If you installed the NSP into C:\Program Files\Texas Instruments, then navigate to:

C:\Program Files\Texas Instruments\nsp_1_00_00_09\packages\ti\ndk\examples

Once in the examples directory, you will see the set of examples archives:

ndk_evm6748_bios5_examples.zip

ndk_evm6748_bios6_examples.zip

ndk_omapl138_arm9_examples.zip

Choose the archive file which correpsonds to your setup and click open

Under "Discovered Projects" you should see the examples listed that come from the archive(s) you selected. Click "Finish" to import the examples.

You may now build the NDK examples within CCS 4.2

NOTE: if a project with the same name as the NDK examples already exists in the workspace, then it will not be found in the above steps. Therefore, it is recommended that a new workspace is used for the above steps.

Rebuilding The Driver Library

The NDK Support Package includes the EMAC driver source files and a RTSC build files that allow you to modify the driver sources and rebuild the EMAC library. You can rebuild the EMAC driver sources in order to modify, update or add functionality. If you edit any of the driver source code and/or RTSC build files, you must rebuild the EMAC library in order to incorporate these changes into it.

The instructions on this page are intended for rebuilding the EMAC driver library on Microsoft Windows in a DOS shell using the xdc command. However, this library may also be re-built on Linux using the xdc command that comes packaged with XDCtools. Linux users should substitute any Windows specific copy, explorer, or DOS shell instructions or commands with the Linux equivalents in the steps that follow.

Warning: This section provides details about rebuilding the EMAC driver source code. We strongly recommend that you copy the NSP installation to a directory with a different name and update and rebuild that copy, rather than rebuilding the original installation.

Making A Backup Copy Of The NSP Installation

Create a new directory on your computer. You will use this directory to store a copy of the NSP installation. This directory will act as a container for your NSP modifications. The full path to this directory cannot contain any spaces.

For example, we recommend creating a directory called "C:/MYNSPBUILDS" rather than using a location in the "My Documents" directory tree.

Using Windows Explorer, copy the entire NSP installation to the directory you just created. For example, if you installed the NSP in the default installation location, then you should copy the C:/PROGRAM FILES\TEXAS INSTRUMENTS\nsp_1_00_00_09 folder and all of its contents to the C:/MYNSPBUILDS folder. After this step, the C:/MYNSPBUILDS folder should contain the nsp_1_00_00_09 folder, which is a copy of your NSP installation.

Rename the folder that contains the copy of the NSP installation. For example, rename the C:/MYNSPBUILDS\nsp_1_00_00_09 directory to C:/MYNSPBUILDS\CUSTOM_nsp_1_00_00_09

Updating The config.bld File

Using Windows Explorer, move to the C:/MYNSPBUILDS\CUSTOM_nsp_1_00_00_09/packages/ti/drv/omapl138 directory.

In this directory, find the file called "config.bld.default". Rename this file to be "config.bld".

Open the config.bld file for text editing.

Make sure that the paths to the NDK 2.20 installation, XDCtools, and Code Generation Tools are correct. For example, if you have installed NDK 2.20 and CCS 4.2 into the default locations, then the default values of the following variables in config.bld should be correct. If you have installed these components into different locations, then you must update these variables to point to the correct installation locations:

var xdctoolsInstallDir = "C:/Program Files/Texas Instruments/xdctools_3_20_03_63";
var ndkInstallDir = "C:/Program Files/Texas Instruments/ndk_2_20_00_19";
C674.rootDir = "C:/Program\ Files/Texas\ Instruments/ccsv4/tools/compiler/c6000"
armElfTargets.Arm9.rootDir = "C:/Program\ Files/Texas\ Instruments/ccsv4/tools/compiler/tms470";

Near the end of the file, look for the array called Build.targets. This array contains the list of targets for which the EMAC driver should be built. Make sure that the target for which you want the driver built is uncommented. To build for all targets, this array should look like the following:


                  Build.targets = [

                            C674,

                            C674_big_endian,

                            armElfTargets.Arm9,

                  ];

Save and exit the file.

Re-building The EMAC Driver

In a DOS shell, navigate to the location of the copy of the NSP installation:

cd C:\MYNSPBUILDS\CUSTOM_nsp_1_00_00_09\packages\ti\drv\omapl138

Run the XDC command to rebuild the driver library

xdc

Or, if your XDCtools installation location is not on your path, type:

"C:\Program Files\Texas Instruments\xdctools_3_20_03_63"\xdc

The driver rebuild should begin

Version Information

This product's version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and b is an unrestricted set of digits used as an incrementing build counter.

To support multiple side-by-side installations of the product, the product version is encoded in the top level directory, ex. nsp_1_00_00_09.

Subsequent releases of patch upgrades will be identified by the patch number, ex. NSP 1.00.01 with directory nsp_1_00_01. Typically, these patches only include critical bug fixes.

Technical Support

Technical support resources
Forum-based technical support is available through the TI E2E Community in the BIOS forum
Wiki-based documentation
Getting Started with the C6000 Network Developer's Kit (NDK)

Check the NDK website for updates.

Last updated: Build Ver: nsp_1_00_00_09 Rev: