readme.txt

摩托罗拉 ColdFire 5206E 在UCOSII上的移植代码

*********************************************************************
*     uC/OS-II port to Motorola MCF5206e ColdFire
*       Version 1.01
*
*
* Authors : Mark Medonis
*           Sekidenko Inc - An Advanced Energy Company
*           [e-mail]
*
*	    Paul S. Carpenter
*	    Northern Computers, Inc.
*	    [e-mail]
*
* Created : 05/20/2002
*
* Originally created by Mark Medonis for M5272C3 eval board, it has
* since been ported to the M5206EC3 eval board by Paul Carpenter.
*
* This port is offered as-is. There is no guarantee that it will
* work on your board, although it does indeed work on my board.
* Really, it does.  Mine, too! (Paul).
*********************************************************************

This project uses uC/OS-II version 2.52. It will probably
work with uC/OS-II version 2.0, but that has not been tested. 

This project was tested using Metrowerks CodeWarrior version 2.5 *and*
version 3.0, running on a Motorola M5206EC3 evaluation board. Hopefully, you 
may use other compilers without *too* much difficulty (the assembly 
language portions of the code may require modifications!).

Files included in port:

  Includes.h   - Master header
  mcf5206e.h   - Register definitions for part
  main.c       - Initialization and test tasks
  target.h     - Hardware target board specific information
  Os_cfg.h     - Configures uC/OS-II
  Os_cpu.h     - Definitions for interrupt enabling/disabling
  Os_cpu_a.s   - Low level interrupt handler, context switcher functions
  Os_cpu_c.c   - Stack initialization
  isr_stub.s   - example assembly language interrupt service routine (ISR) stub
  MCF5206EC3_PnE.cfg  - Metrowerks target configuration file for M5206eC3.  Use
		 this config. file, as it's register values match the code!
  readme.txt   - this file
 
Steps to run this project under CodeWarrior:

1. Create a new project using the M5206EC3 C stationery (C++ and EC++ not tested)
2. Copy the above files into the Source directory inside your
   new project directory location. This will replace the main.c file
   that the stationery created.
3. Back in Codewarrior, add the isr_stub.s, Os_cpu_a.s, Os_cpu_c.c, and main.c files 
   to your project. (Project menu, Add Files). NOTE: Do NOT add Ucos_ii.c from the
   uCOS v2.52 archive to your project build, as you will encounter "Multiple 
   Definition" linker errors! 

Make sure to select "Enable Debugger" from the Project menu in Codewarrior (for CW
v2.5 only), and make sure the Debug target is selected in the project window. 
Project should then compile without errors.  Unless you write your own "printf"
routine, you may use CodeWarrior's "Console" target for I/O.  If "LOGGING" is defined
in main.c, status output from the running tasks may be viewed in CodeWarrior's 
console window.

If you do not have the M5206EC3 evaluation board, this port will still work, and
you can still start with the M5206EC3 project stationery. For custom boards, the only
change needed is the BDM debugger initialization file.