sdk7a404_examples.txt

含t h r e a d x,u c o s 的b s p

Sharp SDK7A404 Example code readme

************************************************************************
* Example introduction
************************************************************************
This area contains example code on how to use and configure the drivers
and interfaces of the LH7A404 chip and SDK7A404 EVB. Example code cannot
be programmed into FLASH to automatically start when the EVB is powered
on - they must be loaded and executed through JTAG using a debugger or
loaded and executed through the Logic Loader (LOLO).

************************************************************************
* Basic example requirements for execution
************************************************************************
To execute an example, the EVB must be pre-initialized to a known state.
This pre-initialized state includes initialized SDRAM, cache and write
buffer(s), MMU tables, interface wait state configurations, etc. When
executing examples with a debugger, the example will need to have any
necessary stacks and environment setup. When executing examples with
LOLO, it is assummed that the stacks are setup when the example code
is executed.

************************************************************************
* Example requirements for execution with LOLO
************************************************************************
If the built-in BOLO code is executed and LOLO is used to load and
execute the examples, the board will be preconfigured to an initialized
state. In addition, the stacks required for the examples will be
preconfigured by LOLO. Examples loaded through LOLO have basic startup
code that simply saves the register set on the stack and starts the
example. When the example is complete, the register set is restored and
execution is returned to LOLO. LOLO works good for most examples, but
doesn't have the capabilities of a JTAG debugger. Also, LOLO may not
work correctly after an example is executed, as the examples may change
peripheral states used by LOLO.

To build an image that is loaded through LOLO, type the following at
the command prompt in the example directory (requires libraries to be
pre-built):
    make lolo

Note: LOLO will load and execute both elf images and Motorola S-record
files. To reduce load times, elf files are stripped of their symbol
information with the makefile and renamed to filename.lolo.elf. Use
this image to load with LOLO. Elf files generate with GHS and IAR may
not load correctly with LOLO. If the elf file doesn't load correctly,
load and execute the corresponding S-record file instead.

************************************************************************
* Example requirements for execution with JTAG debuggers
************************************************************************
If a JTAG debugger is used to load and execute the code. The board must
be pre-initialized. This can be performed by executing the built-in
BOLO code before loading and executing the example, or loading and
executing a startup code example (in the startup directory) prior to
loading and executing the example. Examples built to load through a
JTAG debugger will have some startup and exit code that gets executed
before the actual example code. This code sets up stacks and provides
a safe exit when the example is complete.

To build an image that is loaded through a debugger, type the following
at the command prompt in the example directory (requires libraries to
be pre-built):
    make

Note: Unlike examples built for LOLO, no S-record is generated for
examples built for a JTAG debugger. Debugger examples also maintain
all symbolic debugging information. GHS, IAR, and GNU toolsets create
elf files, while ARM ADS creates AXF files.