#****************************************************************************
#
#       Project         : Server/Loader V4.07
#       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.

To run the example, simply type

	my32 v

There is also a my32_pc8 batchfile for use with a HEPC8. It uses a
network file called network.pc8, this assumes a HECP8 with the board
switch set to 0, and a HERON4 in slot 1. To run:

	my32_pc8 v

The 'v' selects verbose option and is optional.

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 plug-in. If you name the project
'test.pjt', then 'test.c' will be automatically included in the 
project.

This example is to show you how you can use the Server/Loader to boot
and run the DSP system, while a second program (written by you) can
then take over and communicate with the root processor. Essentially,
the second program acts as the Server.

The my32 script first boots the DSP network using the standard Server/
Loader using the -r (reset), and -l (load network) options. The -s
(serve) switch is not specified, which means that the Server/Loader
quits after having booted the DSP system. Then the my32 script starts
up the "mysl" program. This communicates with the DSP system using the
Hunt Engineering API. To compile & link this program:

	make

This will use the "Makefile" present in this directory. If you intend
to write one program that both boots the DSP network and serves it, 
please have a look at the ../exe 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" and "networkspec.pdf" in the
/web/pdfs/manuals directory on the Hunt Engineering CD).

13/05/2003

