README for HEGD9 example with  the HUNT ENGINEERING server/loader
=================================================================

In this directory there are the following files

README         This file
GD9      C     The .C file that has some useful functions defined and uses them in the demo.
MAKE     BAT   A batch file to compile the demo for use with TI C compiler
GD9      CMD   The TI C compiler commane dile for this demo.           
HUNT     CMD   The command file that defines the memory map of the processing module used.
NETWORK        The server/loader network file
W32      BAT   A batch file to runn this demo using the win32 versio of the server/loader     

COMPILING
---------

Check your system configuration to find out which comport of the DSP
is connected to the HEGD9. In the .C file there is a line  

#define ANALOGUE_IN     5       /* Comport for the HEGD9 */

which must be changed to reflect the correct comport connection. The
file HUNT.CMD must be changed to reflect the memory configuration of
your processing module that the HEGD9 is connected to.

The file MAKE.BAT must have the TICC and TILIB variables edited to
show the location of your TI compiler. Also you will  need to correct
the paths to the server/loader files.

The demo can then be built using the make batch file or by setting the
options in the Code Composer Project Build options.

The network file must be edited to reflect your host board type and
the comport connections to the host machine. The demo can be run using
the w32.bat batch file.

The program prints some data using the server mode of the server/loader

FOR USE WITH CODE COMPOSER 
--------------------------

When you are going to use the Server/loader and Code Composer you should
compile the demo useing the maked batch file.

If you have copied your demo into the directory c:\hegd9\c4x\sl then
you can start Code Composer and simply open the workspace provided
(gd9.wks). You may have some problems with the paths of the various
files, so you might need to set up some of the workspace yourself.

Load the symbols using the file menu's load symbols option.

Use the debug menu's run free option.

Go to a DOS window and use the dosrun batch file. If the demo has
been compiled using the maked batch file then you should  get  

	"OK, ready" 

printed in the DOS window and then the program appears to hang.

In the Code Composer window use the Debug menu's halt option.
Use the Edit menu's "edit variable" option to set the variable
r to be zero.

Then you may step or run to get out of the waiting loop. 
 
Set a breakpoint at the line below the comment

	"Heres where we would..." 
	
and use the view menu to select graph and time/frequency options.

In the options given select start address and set it to ch1_data,
set aquisition buffer size and display data size to 100, and set
the maximum Y-value to be 4096, DC value to 0x800 and DSP data
type to unsigned 32bit integer then click OK.

You can add watch points to some variables, the no_of_channels
and LowIsFirst are interesting ones.

Now every time the breakpoint triggers, the graph and watchpoints
will be updated with the values from channel 1 of the A/D.
Animating will give a continuously updating graph.

NOTICE !
--------
Every time a breakpoint happens the whole of the DSP stops. This
means that the reading from  the comport will stop causing the FIFOs
in the data path to overflow. This example uses a flush function to
ensure that all stale data is removed from those FIFOs before taking
real data.  


V 1.0 10-03-2000
