ReadV0_3.txt
=============

  This file contains an overall description of the files you
should receive with this release of the M68360 QUADS software. The
release was prepared under UNIX, so if your environment is either
DOS (or you have taken the files from the bulletin board), the tar-files 
mentioned below will already be unpacked.  In any event, you should, 
after copying the files to you computer, have a set of directories which 
exactly corresponds to the tar files.

  The top directory contains tar files which together constitute
an entire QUADS-360 software system. Each of the tar files
(drvrs, psend, exs, sun, ibmpc, mods, init_exs) should be unpacked,  
directories of the same names as the tar files will be created.

  Unpack the tar files by typing

        tar xvf XXXXX.tar

CAUTION: Do not try to unpack all of the tar files with one
command (such as tar xvf *.tar). Each file must be unpacked with
a seperate command.

 The contents of each of the directories created is explained below.

"doc" contains the version numbers for the QUADS software modules
(quads_vn.txt) in this release.  Also, there is a test file which 
discusses getting started with the current release.  

"drvs" the drivers directory contains the source files for the software 
modules on the M68360 QUADS board, consult the readme file in the drvs 
directory for details on compiling the sources.  Note that include files 
are contained here as well as library routines, which are available to all 
(not only source) customers.

"examples" contain an example set of g-files and history files
for use in running the "host" program. The g-files contain 
initialization information that is loaded by the s/w running 
on the board. These g-files serve as examples and may be
edited for different environments.

The history files are lapd.tut, x25b.tut and x25d.tut: they may both
be run using either the "History run" or "Tutorial" options.

"ibmpc" contains the host programs versions for the IBM/PC. On the
IBM/PC you have two host programs, one has a command line driven user
interface and the other is a graphical user interface.  The graphical
user interface runs with its own graphics library so it is independent 
of MS/Windows. 

"inc" contains files that are common to all the modules.  These files
are essential and are included for all software.

"init_exs" contains sample code that sets up the serial channel for 
either UART, HDLC, or Ethernet mode.  These are simple examples that 
are there to help you get started.  These examples are also
included in the MC68360 User's Manual.

"init_ex2" contains a demonstration of using an interrupt driven 
receive routine with threee protocols:  UART, HDLC, and Transparent.

"lib" contatins library routines that are called by all of the modules.

"mods" the module directory contains two S-record format files of the 
M68360 QUADS software modules, one for flash EPROM and one for RAM.
The mods directory also contains the S-record format file for the
CPU32bug Debug Monitor which runs on the M68360 (also known as QUICCbug
and 360bug).  Information on how to download the S-records is contained
in the file start.txt in the doc directory.

"psend" contains the source for the example psend program.
It may be compiled on any of the hosts (SUN, IBM/PC)
The source code is not the code of a product supported by Motorola.
While no know bugs exist, it has not been thoroughly tested in all
configurations. Refer to the psend ReadPsnd.txt file for more details.

"src" contains the source code to the example tasks. The same tasks
are included in the M68360 Software Programmer's Manual.

"sun" contains kernel configuration files for SUN4 computer,
and a host program that may be run on it.

"qstart" contains the g-files which set the registers correctly for
the programming examples in the QUICC-Start tutorial.  You would 
execute your host program from this directory when using an ADI card.
