| 6 |
kaklik |
1 |
//------------------------------------------------------------------------
|
|
|
2 |
// Readme.txt
|
|
|
3 |
//------------------------------------------------------------------------
|
|
|
4 |
This project stationery is designed to get you up and running
|
|
|
5 |
quickly with CodeWarrior for MC9S08QG8.
|
|
|
6 |
It is set up for the selected CPU and target connection,
|
|
|
7 |
but can be easily modified.
|
|
|
8 |
|
|
|
9 |
Sample code for the following language(s) is at your disposal:
|
|
|
10 |
- C
|
|
|
11 |
|
|
|
12 |
The wizard has prepared CodeWarrior target(s) with the connection methods of
|
|
|
13 |
your choice:
|
|
|
14 |
- P&E FCS:
|
|
|
15 |
This interface/target is prepared to use the FCS (Full Chip Simulation)
|
|
|
16 |
from P&E. Note that you can switch to hardware debugging in a seamless way,
|
|
|
17 |
using the menu PEDebug > Mode in the debugger.
|
|
|
18 |
|
|
|
19 |
- P&E ICD:
|
|
|
20 |
This interface/target is prepared to use the ICD (In-Circuit
|
|
|
21 |
Debugging/Programming) from P&E. Note that you can switch to simulation in
|
|
|
22 |
a seamless way, using the menu PEDebug > Mode in the debugger. Depending on
|
|
|
23 |
your hardware type, you will need to configure the communication settings
|
|
|
24 |
(class of device, baud rate, etc).
|
|
|
25 |
Please consult your hardware documentation for additional details.
|
|
|
26 |
|
|
|
27 |
- Freescale Serial Monitor:
|
|
|
28 |
This interface/target connects to the on-chip Freescale serial monitor.
|
|
|
29 |
This monitor uses on-chip resources and the SCI. See Freescale application
|
|
|
30 |
note AN2140 for details.
|
|
|
31 |
The debugger is using GDI (Generic Debugging Interface) to connect to the
|
|
|
32 |
serial monitor. Using the on-chip DBG module of HCS08 devices,
|
|
|
33 |
trace is supported as well. You can load the trace component
|
|
|
34 |
using the menu Component > Open in the debugger.
|
|
|
35 |
|
|
|
36 |
- SofTec:
|
|
|
37 |
This target interface connects to any of the USB-based SofTec Microsystems tools for HC(S)08.
|
|
|
38 |
|
|
|
39 |
For the HC08 derivatives, when using inDART-HC08 (MON08 protocol based connection):
|
|
|
40 |
-----------------------------------------------------------------------------------
|
|
|
41 |
If your hardware supports stopping the application while running,
|
|
|
42 |
an additional interrupt service routine is required for the IRQ vector.
|
|
|
43 |
Please see "Stop Command Handling" section in inDART-HC08 In-Circuit Debugger/Programmer
|
|
|
44 |
for Freescale HC08 Family FLASH Devices User Manual from SofTec for further details.
|
|
|
45 |
|
|
|
46 |
|
|
|
47 |
Additional connections can be chosen in the simulator/debugger,
|
|
|
48 |
use the menu Component > Set Target.
|
|
|
49 |
|
|
|
50 |
//------------------------------------------------------------------------
|
|
|
51 |
// Getting Started
|
|
|
52 |
//------------------------------------------------------------------------
|
|
|
53 |
To build/debug your project, use the menu Project > Debug or press F5.
|
|
|
54 |
This will open the simulator/debugger.
|
|
|
55 |
Press again F5 in the debugger (or menu Run > Start/Continue) to start
|
|
|
56 |
the application. The menu Run > Halt or F6 stops the application.
|
|
|
57 |
In the debugger menu Component > Open you can load additional components.
|
|
|
58 |
|
|
|
59 |
//------------------------------------------------------------------------
|
|
|
60 |
// Project structure
|
|
|
61 |
//------------------------------------------------------------------------
|
|
|
62 |
The project generated contains various files/folders:
|
|
|
63 |
- readme.txt: this file
|
|
|
64 |
- Sources: folder with the application source code
|
|
|
65 |
- Startup Code: C/C++ startup code (initializing stack pointer and doing
|
|
|
66 |
global variable initialization). If you want to only do stack pointer
|
|
|
67 |
initialization, add -D__ONLY_INIT_SP to the compiler command line.- Prm:
|
|
|
68 |
- burner.bbl file to generate S-Records
|
|
|
69 |
- the linker .prm file
|
|
|
70 |
- the .map file generated by the linker
|
|
|
71 |
- Libs: needed library files (ANSI, derivative header/implementation files)
|
|
|
72 |
- Debugger Project File: contains a .ini file for the debugger for each
|
|
|
73 |
connection
|
|
|
74 |
- Debugger Cmd Files: contains sub-folders for each connection with command
|
|
|
75 |
files
|
|
|
76 |
|
|
|
77 |
//------------------------------------------------------------------------
|
|
|
78 |
// Adding your own code
|
|
|
79 |
//------------------------------------------------------------------------
|
|
|
80 |
Once everything is working as expected, you can begin adding your own code
|
|
|
81 |
to the project. Keep in mind that we provide this as an example of how to
|
|
|
82 |
get up and running quickly with CodeWarrior. There are certainly other
|
|
|
83 |
ways to handle interrupts and set up your linker command file. Feel free
|
|
|
84 |
to modify any of the source provided.
|
|
|
85 |
|
|
|
86 |
//------------------------------------------------------------------------
|
|
|
87 |
// Simulator/Debugger: Additional components
|
|
|
88 |
//------------------------------------------------------------------------
|
|
|
89 |
In the simulator/debugger, you can load additional components. Try the menu
|
|
|
90 |
Component > Open.
|
|
|
91 |
|
|
|
92 |
//------------------------------------------------------------------------
|
|
|
93 |
// Additional documentation
|
|
|
94 |
//------------------------------------------------------------------------
|
|
|
95 |
Check out the online documentation provided. Use in CodeWarrior IDE the
|
|
|
96 |
menu Help > CodeWarrior Help.
|
|
|
97 |
|
|
|
98 |
//------------------------------------------------------------------------
|
|
|
99 |
// Contacting Metrowerks
|
|
|
100 |
//------------------------------------------------------------------------
|
|
|
101 |
For bug reports, technical questions, and suggestions, please use the
|
|
|
102 |
forms in the Release Notes folder installed, and send them to:
|
|
|
103 |
USA: support@metrowerks.com
|
|
|
104 |
EUROPE: support_europe@metrowerks.com
|
|
|
105 |
ASIA/PACIFIC: j-emb-sup@metrowerks.com
|