db_stationery _readme.txt

一个linux下的usb接口源代码

//________________________________________________________________________
//                       DragonBall VZ Specific Information
//________________________________________________________________________

Ports and Debugger:
    The DragonBall boards generally use MetroTRK for both stdio and debugger
communication.  Input and output are done through the MetroTRK Console.
The UART libraries used in the TRK are available in the E68k_Tools\MetroTRK 
directory if the user wishes to use the second serial port for IO.  The
stationery contains the libraries necessary for a basic functioning setup.
For DragonBall these include:

1)  Runtime library (includes init code and other runtime necessities)
2)  MSL library - Metrowerks Standard C/C++/EC++ libary, including
      the MetroTRK Console
3)  Floating point library if needed

For example, the stardard C stationery for the VZ board includes:

1) C_4i_68000_Runtime.a - for init and exit code
2) C_TRK_4i_68000_MSL.a - for C libaries and MetroTRK
3) fp_68000.o - for floating point support

    Most DragonBall boards come with MetroTRK pre-burned on one port.
This should be noted in the board documentation.  MetroTRK can be
re-flashed or flashed to a different port using the included tools.
Instructions for doing this are in this directory:

   <CodeWarrior Install>\E68k_Tools\MetroTRK\Processor\M68K\Board\<myboard>

The BBUG tools necessary to do the flash are in this directory:

   <CodeWarrior Install>\E68k_Tools\Motorola_EZ_and_VZ_tools\<myboard>

This allows the user to custom configure MetroTRK on any desired port,
and re-flash MetroTRK if it has been replaced by another ROM target.

*=========================================================================
*  Flashing the ROM target
*=========================================================================
The ROM targets are new with this release.

To install the ROM target refer to ROM_readme.txt included with this 
stationery. 

//------------------------------------------------------------------------
//	General Overview
//------------------------------------------------------------------------

This project stationery is designed to get you up and running
quickly with CodeWarrior for Embedded 68k/Coldfire.  It is set up
for a particular evaluation board, but can be easily modified
to target custom hardware.  The hardware specific changes that
you may need to make include hardware initialization code, 
UART driver, flash programing code, and possibly the linker
command file for memory map issues.

The project has the following three targets:

Debug Version
-------------
This is the default target.  It doesn't do any hardware
initialization or generate ROMable code.  It is designed to get
you started coding fast and debugging your code in RAM.
 
Release Version
---------------
This is the release version that is compiled with full optimizations
turned on and A6 stack frames turned off. It is designed to be used
as a guideline in generating optimized release code.

ROM Version
-----------

This target is set up to make a ROMable image. DragonBall ROM examples
include exception vectors and are linked in such a way that they 
will boot from reset and copy the data sections from ROM to RAM.
This target contain reset vector, initial stack pointer location,
board/hardware initialization code, and flash utility in additional
to sources and libraries in RAM targets. This target generates an 
S-record which can be flashed onto the board using BBUG. See 
ROM_readme.txt for more details.

A DragonBall ROM target cannot be debugged with CodeWarrior once
it is flashed onto the board because the ROM image overwrites MetroTRK,
making further debugging with CodeWarrior impossible until MetroTRK
is restored. Please refer to "Ports and Debugger" of this document for
details on restoring MetroTRK.

//------------------------------------------------------------------------
//	Getting Started
//------------------------------------------------------------------------

Most of the target settings are already configured for you, but you
will need to configure the debugger settings.  From the Edit menu,
select Debug Version Settings... (Alt+F7). Select the E68k Target
Settings pref panel from left column.  Select the protocol and related
options that you want to use for debugging.  We recommend that you make
sure the project is working properly on your hardware before you begin
adding your own code.  Make sure your target has power and is connected
with the selected debug protocol.  Select Enable Debugger from the 
Project menu and then select Debug.  If everything is working properly,
the debugger window should come up and be stopped at main().  If there
is a problem, please consult Targeting_Embedded_68k.pdf for more
information on your selected debug protocol.  

//------------------------------------------------------------------------
//	Adding your own code
//------------------------------------------------------------------------

Once everything is working as expected, you can begin adding your own code
to the project.  Keep in mind that we provide this as an example of how to
get up and running quickly with CodeWarrior.  There are certainly other 
ways to handle interrupts and set up your linker command file.  Feel free
to modify any of the source provided. 


//------------------------------------------------------------------------
//	Contacting Metrowerks
//------------------------------------------------------------------------

For bug reports, technical questions, and suggestions, please use the
forms in the Release Notes folder on the CD, and send them to:

[e-mail]        : For bug reports.
[e-mail] : For suggestions.