
===================================================================
Stationery for the MCF5213 Freescale Board
===================================================================

Contents:

I)     Overview
II)    Files
III)   Memory maps
IV)    Initialization files
V)     Targets
VI)    Connecting to the board
VII)   Terminal Settings
VIII)  Test hardware

===================================================================
WARNING regarding Targets located code in RAM
===================================================================

Many possible ColdFire target processors have an external bus, 
so can use large external RAM devices for debugging applications 
during development. But M521x processors do not have an external 
bus, so must accommodate applications in on-chip memory. 
Although this on-chip RAM accommodates CodeWarrior stationery, 
it probably is too small for full development of your application. 
Accordingly, for an M521x processor, you should locate your 
applications in flash memory. (The Flash Programmer subsection of 
the Targeting Manual explains how to program a flash device.)

===================================================================
I)  Overview
===================================================================

This stationery is configured to run with the M5213EVB which contains
a MCF5213 product.  Since the MCF5213 is a superset of all the 
MCF521x family of chips, this code contains include files for
all features that exist.  This code initializes and utilizes
those features that ONLY exist on all the chips in the family.

For more details, refer to the MCF521x Reference Manual

===================================================================
II)  Files
===================================================================

CF_M5213_C.mcp - the project file

*.cfg - initialization files
*.mem - memory configuration file
*.lcf - linker configurations

Source - All source files and include files.

===================================================================
III)  Memory maps
===================================================================

The Target has the following memory map:

0x00000000-0x0003ffff 256 Kbytes of on-chip Flash memory
0x20000000-0x20007fff  32 Kbytes of internal SRAM

===================================================================
IV)  Initialization files
===================================================================

All initialization files setup the same memory map. The only
difference is the location of the VBR register at download time.

The P&E Protocol plugin allows the use of the "+-" panel
to capture various exceptions. After the code is downloaded, the
plugin attempts to overwrite the vector table entries and install its
own handler at locations VBR+0x408-0x40B to capture those selected
exceptions.  See descirption under Targets below.

M5213EVB_PnE.cfg - used in the M5213EVB Console Debug
M5213EVB_PnE.cfg - used in the M5213EVB UART Debug
M5213EVB_PnE.cfg - used in the M5213EVB UART Release
M5213EVB_PnE.cfg - used in the M5213EVB Internal ROM

===================================================================
V)  Targets
===================================================================

1) M5213EVB Console Debug

This is the very basic stationery that outputs to the CodeWarrior's
console window.  Due to the size limitation of SRAM, the user should be
aware of the size of CodeWarrior runtime library when running applications
in SRAM.

2) M5213EVB UART Debug

This is the very basic stationery that outputs to the UART.
User need to connect the terminal to see the output.  Due to the size
limitation of SRAM, the user should be aware of the size of CodeWarrior
runtime library when running applications in SRAM.

3) M5213EVB UART Release

This is the very basic stationery that outputs to the UART.
User need to connect the terminal to see the output.  Due to the size
limitation of SRAM, the user should be aware of the size of CodeWarrior
runtime library when running applications in SRAM.

4) M5213EVB Internal ROM

This program copies the data from ROM to SDRAM
This is the very basic stationery that outputs to the UART.
User need to connect the terminal to see the output.

===================================================================
VI)  Connection to the M5213EVB board
===================================================================

1) All jumper settings and switches are in their default locations
as outlined by the EVB user's manual.

2) The P&E cable is attached to the BDM connector.

3) An appropriate power supply is connected to the power jack as 
outlined in the EVB user's manual.

4) Check all the target Remote Connection panels to make sure the P&E
cable is selected.

===================================================================
VII)  Terminal Settings
===================================================================

In case the UART is handled, the terminal is using the following
settings

The baud rate to be : 19200
Data bits : 8
Parity : None
Stop Bits : 1
Flow Control : None

===================================================================
VIII)  Test Hardware
===================================================================

The following was used in testing:

P&E ColdFire Rev F cable
M5213EVB from Freescale
===================================================================