0,0 → 1,105 |
//------------------------------------------------------------------------ |
// Readme.txt |
//------------------------------------------------------------------------ |
This project stationery is designed to get you up and running |
quickly with CodeWarrior for MC9S08QG8. |
It is set up for the selected CPU and target connection, |
but can be easily modified. |
|
Sample code for the following language(s) is at your disposal: |
- C |
|
The wizard has prepared CodeWarrior target(s) with the connection methods of |
your choice: |
- P&E FCS: |
This interface/target is prepared to use the FCS (Full Chip Simulation) |
from P&E. Note that you can switch to hardware debugging in a seamless way, |
using the menu PEDebug > Mode in the debugger. |
|
- P&E ICD: |
This interface/target is prepared to use the ICD (In-Circuit |
Debugging/Programming) from P&E. Note that you can switch to simulation in |
a seamless way, using the menu PEDebug > Mode in the debugger. Depending on |
your hardware type, you will need to configure the communication settings |
(class of device, baud rate, etc). |
Please consult your hardware documentation for additional details. |
|
- Freescale Serial Monitor: |
This interface/target connects to the on-chip Freescale serial monitor. |
This monitor uses on-chip resources and the SCI. See Freescale application |
note AN2140 for details. |
The debugger is using GDI (Generic Debugging Interface) to connect to the |
serial monitor. Using the on-chip DBG module of HCS08 devices, |
trace is supported as well. You can load the trace component |
using the menu Component > Open in the debugger. |
|
- SofTec: |
This target interface connects to any of the USB-based SofTec Microsystems tools for HC(S)08. |
|
For the HC08 derivatives, when using inDART-HC08 (MON08 protocol based connection): |
----------------------------------------------------------------------------------- |
If your hardware supports stopping the application while running, |
an additional interrupt service routine is required for the IRQ vector. |
Please see "Stop Command Handling" section in inDART-HC08 In-Circuit Debugger/Programmer |
for Freescale HC08 Family FLASH Devices User Manual from SofTec for further details. |
|
|
Additional connections can be chosen in the simulator/debugger, |
use the menu Component > Set Target. |
|
//------------------------------------------------------------------------ |
// Getting Started |
//------------------------------------------------------------------------ |
To build/debug your project, use the menu Project > Debug or press F5. |
This will open the simulator/debugger. |
Press again F5 in the debugger (or menu Run > Start/Continue) to start |
the application. The menu Run > Halt or F6 stops the application. |
In the debugger menu Component > Open you can load additional components. |
|
//------------------------------------------------------------------------ |
// Project structure |
//------------------------------------------------------------------------ |
The project generated contains various files/folders: |
- readme.txt: this file |
- Sources: folder with the application source code |
- Startup Code: C/C++ startup code (initializing stack pointer and doing |
global variable initialization). If you want to only do stack pointer |
initialization, add -D__ONLY_INIT_SP to the compiler command line.- Prm: |
- burner.bbl file to generate S-Records |
- the linker .prm file |
- the .map file generated by the linker |
- Libs: needed library files (ANSI, derivative header/implementation files) |
- Debugger Project File: contains a .ini file for the debugger for each |
connection |
- Debugger Cmd Files: contains sub-folders for each connection with command |
files |
|
//------------------------------------------------------------------------ |
// 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. |
|
//------------------------------------------------------------------------ |
// Simulator/Debugger: Additional components |
//------------------------------------------------------------------------ |
In the simulator/debugger, you can load additional components. Try the menu |
Component > Open. |
|
//------------------------------------------------------------------------ |
// Additional documentation |
//------------------------------------------------------------------------ |
Check out the online documentation provided. Use in CodeWarrior IDE the |
menu Help > CodeWarrior Help. |
|
//------------------------------------------------------------------------ |
// Contacting Metrowerks |
//------------------------------------------------------------------------ |
For bug reports, technical questions, and suggestions, please use the |
forms in the Release Notes folder installed, and send them to: |
USA: support@metrowerks.com |
EUROPE: support_europe@metrowerks.com |
ASIA/PACIFIC: j-emb-sup@metrowerks.com |