#****************************************************************************
#
#       Project         : Server/Loader V4.10
#       Component       : Server example.
#       File            : README
#       Author          : 
#       Description     : 
#       History         : 
#
#****************************************************************************

This example program as-is works with a HEPC9 with one HERON4 module
in slot 1. The board ID must be 0 (board ID is the red switch in the
upper left corner of the HEPC9).

If your configuration is different, please edit the "network" file.

Note that this example cannot run with HEPC8, HEPC6 and legacy
boards (C4x boards). 

To run the example, simply type

	./threads

To compile the C6x example, you need access to Code Composer Studio.
At the time of writing this, Code Composer Studio is only available
for Windows. Using Code Composer Studio, create a new project with
the Create New HERON-API Project plugin. If you create a project
named 'test', the 'test.c' C6x file will be automatically included.

This example is to show you how to use the Server/Loader library to
boot and serve a DSP system. After booting, the same C/C++ program
then uses the API to communicate with the DSP system in a separate
thread. The example runs in parallel the Server/Loader's Server
and a thread communicating with a DSP node via another FIFO.

To compile and link this program:

	make

This will use the "Makefile" present in this directory. If you would
prefer to have the standard Server/Loader to boot and serve the DSP
system, while in a seperate program you wish to communicate with the
DSP system, have a look in the ../parallel directory.

The Server/Loader uses a network description file (called "network")
to decide what nodes need to be loaded via what links. This is further
described in the manual ("svloader.pdf" in the manuals directory on the
Hunt Engineering CD).

There are 2 variations of threads.cpp in this example directory. They
do the same thing (running the S/L and an API thread in parallel, each
communicating with the DSP in slot 1 over different fifo's). But the
ex1.cpp and ex2.cpp use different parts of the hesl class, just to
show the use of some other functions (in the hesl class). They can
be run as follows:-

	./ex1
	./ex2

The Makefile can be used to compile/build these examples:-

	make ex1
	make ex2

16/12/2003



