template: Template Application

This is a template application.  This application is a simple
hello world application that can be used as the base of other
applications.  It does the following:

1.  The development board is initialized and the POST tests
    are executed.
2.  The ThreadX kernel is loaded.
3.  The device drivers are loaded.
4.  The TCP/IP stack is loaded.
5.  The function applicationStart() is called.

Code to start the user application should be placed in the function
applicationStart().  This function is called after the TCP/IP stack
has loaded and is ready to be used.  Generally, you will create and 
start whatever threads your application needs in this function.  

One GNU make file is provided.  Build the target 'image' to
generate an image that can be debugged with gdb, and the file 
image.bin which can be written to flash if the bootloader is used.
Build the target 'rom.bin' to create the file rom.bin which 
can be written to ROM if the bootloader is not used.

The following files are provided in this template.

appconf.h         sets application configuration settings
makefile          Make file for the GNU toolset.
readme            this file
root.c            contains applicationStart() function


In addition, the following files in the BSP directory are built
as part of this application.

reset.s         contains the reset code
appconf_api.c   contains code used to read settings in appconf.h


The application build file links in the following libraries.  Most of these
libraries are not actually used by the "Hello World" application.  They are
included because this application is meant to be used as a template for
other applications that may use these libraries.  The linker only includes
the code in libraries that is actually used.  For example, none of the code
in the email client library will be linked into the "Hello World" application
since "Hello World" does not call any email APIs.

The library names are different for the GNU and Green Hills version of the
development kits.  All GNU libraries are prefixed with "lib".  For example,
the BSP library is named "bsp.a" in the Green Hills kit, and "libbsp.a" in
the GNU kit.  The names below are for the Green Hills version of the kit.

libbsp.a           		contains the BSP code
libtcpip.a         		contains the Net+Works TCP/IP stack
libtx.a            		contains the ThreadX kernel
libfilesys.a       		contains the file system libraries
libposix.a         		contains the POSIX layer libraries
libflash.a         		contains the Flash driver API library
libftpsvr.a        		contains the FTP server library
libtelnsvr.a       		contains the Telnet server library
libaddp.a		   		contains the ADDP Library
libssh.a		   		contains the SSH Library
libdnsclnt.a            contains the DNS Client library

The application uses the following files located in the
netos\src\linkerScripts directory.  These files are generated
when the BSP is built.

bootldr.dat     bootloader configuration file used to generate the
                file image.bin.  It controls the information placed
                in the bootloader header of the image.

image.ldr       GNU linker script used to build an image that can
                be debugged and used with the bootloader.
                
customize.ldr   Customizable GNU linker script

