NetBind Source Code

Figure 1: Hardware Environment for running NetBind

library name	description	library file
ni	NetBind interpreter library	libni.a
dconstructor	data path constructor library	libdconstructor.a
uac	microengine admission controller library	libuac.a
binder	binder library	libbinder.a
ustore	microstore library	libustore.a
ixpconfig	configures the IXBus, microengines and MAC ports	libixpconfig.a
tmd	microassembler extensions library	libtmd.a
cmo	code morphing library	libcmo.a
verifier	verifies data path components before binding	libverifier.a
structures	data structure management library	libstructures.a

library name	description	library file
uclo	microcode loader library	libuclo.a
ueng	microengine control library	libueng.a
octalmac_21440	octal Mac driver library	liboctalmac_21440.a
hal_1200	hardware abstracton layer library	libhal_1200.a
core_utils	miscelleous functions	libcore_utils.a
osApi	miscelleous functions	libosApi.a
utils	miscelleous functions	libutils.a

application name	description
ni	NetBind interpreter
uof2tmd	UOF to TMD conversion utility

Two packages are included with this release: the NetBind libraries (source code and binaries) and the Intel IX libraries for Arm-Linux (binaries).

Download and uncompress the netbind.tar.gz file and extract it to a directory. Type "make all" from the datapath directory to compile and link the ni and uof2tmd utilies. The executable files for these utilities are placed in the bin directory once the code is successfully compiled. The make file assumes that the Arm-Linux tool chain has been installed in the /usr/local/armbe directory.

Copy the ni and uof2tmd executable files to a directory that is accessible from your IXP1200 Evaluation Kit. Complile the transport module microcode files on the Windows NT/2000 PC. Create a separate project for each microcode file as described in the NetBind Software Developer's Guide. Once you have compiled the transport module files, copy their associated images (.uof files) to the directory where the ni and uof2tmd utilities are located. When compiling the transport modules it is preferable not to use the "optimize" option.

To run netbind you need to login to your IXP1200 evaluation board and go to the directory where the ni and uof2tmd utilities are located. Use the uof2tmd utility to convert the UOF files to the TMD format. Before running ni make sure that the ni sample programs, which are included with this release, are also copied into the same directory. The ni sample programs are located in the examples directory.

7. How to Compile Applications for Arm-Linux

A shell script (ixpenv) is provided for setting up the compilation environment. The script makes some assumptions about the environment. It assumes that the Arm-Linux tool chain has been installed in the /usr/local/armbe directory. The compilation environment script has to be changed if the software setup is different.

To compile a program with armv4b-unknown-linux-gcc or armv4b-unknown-linux-g++, set following flags:

• -mbig-endian
• -fwritable-strings
• -DIOSTYLE=HARDWARE -DLINUX -DMAC_21440 -D__unix

To enable the printing of debugging information in the standard output during the execution of the ni and uof2tmd utilities, compile these utilities and the NetBind tool libraries using the following flags:

• -DDEBUG
• -DVERBOSE

8. Download Area

Before downloading NetBind Software, please read the following:

This is unpublished proprietary software developed as part of the Genesis Project by the COMET Group, Columbia University; it may not be disclosed to third parties, copied or duplicated in any form, in whole or in part without the prior written permission of the COMET Group at Columbia University.

All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the COMET Group at Columbia University. It is distributed as is, with absolutely no warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. The entire risk as to the quality and performance of the programs is with you. Should the programs prove defective, or cause any damage, you assume the cost of all necessary servicing, repair or correction.

netbind.tar.gz