#****************************************************************************
#
#       Project         : Server/Loader V3.1
#       Component       : Server example.
#       File            : README
#       Author          : 
#       Description     : 
#       History         : 
#
#****************************************************************************

This example program will work as-is with a 40Mhz HEQUAD in slot 1 of a HEPC3,
HEPC4 or HECPCI1. If you have any other configuration, please first edit the
network configuration file ("hequad"):

1.If you use a HEPC2E, please change "BD API hep3b 0 0" by "BD API hep2e 0 0"
2.If you have a 50 Mhz HEQUAD in slot 1: copy hequad50a hequad.
3.If you have a 60 Mhz HEQUAD in slot 1: copy hequad60a hequad.
4.For other configurations, please change the "BOOTLINK" statements. First,
  determine how your C4x processors are interconnected (use the manuals of
  the TIM-40 modules to help you: on the CD in the \manuals directory).
5.If your configuration has a C40 processor connected to the host, please
  change "HOSTLINK 4" by "HOSTLINK 3".

The example program is very simple, it simple sends a character from the
host to the root, hops from processor to processor, then echoes at the
last processor (D) then hops back and is returned to the host.

To run the example:

	w32

(If you use pure MSDOS or Windows 3.1 (DOS box), use

        dosrun

instead. This batch file will also work under Windows 95/98,
but not under Windows NT.)

To compile the example:

	make

(This runs a make.bat batch file.)

The Server/Loader makes use of a network configuration file. There are several
present in this directory. The w32.bat batch file uses "hequad", and this net-
work file is copied from one of "hequad40a", "hequad40b", "hequad50a", "hequad50b",
"hequad60a" or "hequad60b". The number in this filename refers to the processor
clock frequency of the C44's on the HEQUAD. The 'a' or 'b' character refers to
the booting sequence:

A) a "hequadxxa" network file boots the HEQUAD as follows:

   HEPC3/4 or HECPCI
    |           +---------+
    |           |         |
    |   +-C44-+ | +-C44-+ | +-C44-+   +-C44-+
    |   |    2+-+ |     | | |     |   |     |
    +---+4 A 1+---+4 B  | +-+4 C  | +-+1 D  |
    |   |    5+-+ |     |   |     | | |     |
    |   +-----+ | +-----+   +-----+ | +-----+
    |           |                   |
    |           +-------------------+

B) a "hequadxxb" network file boots the HEQUAD as follows:

   HEPC3/4 or HECPCI
    |                       
    |                      
    |   +-C44-+   +-C44-+   +-C44-+   +-C44-+
    |   |     +   |     |   |     |   |     |
    +---+4 A 1+---+4 B 5+---+1 C 2+---+5 D  |
    |   |     |   |     |   |     |   |     |
    |   +-----+   +-----+   +-----+   +-----+

It makes no difference whether you use scheme A or B. It simply tries to show
you that there are different ways you can boot a HEQUAD. To use the "hequadxxy"
of your choice, e.g. if you have a 50 Mhz HEQUAD and you want to use scheme B:

	copy hequad50b hequad

then you can run the example with:

	w32

26/01/2000
