readme.txt

CodeWarrior for HCS12 V4.7 BDIK Target Interface

# HC12 BDIK Target Interface - Fibonacci application for RAM memory
###################################################################

Overview
========

This project is an HC12 BDIK Target Interface ANSI-C project.
This example is running the Fibonacci application on 
M68HC812A4 derivatives debugged with an Abatron BDIK.

The Fibonacci application calculates the Fibonacci numbers with the Fibonacci
suite: U(n+1) = U(n) + U(n-1)   with U(0) = 0 and U(1) = 1

NOTE: As there is no onchip flash memory for the M68HC812A4, no flash programming is 
obviously available.

NOTE: As the M68HC812A4 derivative has no hardware breakpoint module, hardware 
breakpoints and watchpoints are not available while debugging. 

The project
===========
The "Fibo - RAM" CodeWarrior target is available within this project.

Using this target, the code of generated application 'fibo_ram.abs' 
is located in the onchip RAM memory of the M68HC812A4.

NOTE: For this target, all the local variables in the debugger 
Data component are visible, because some Compiler optimizations have been disabled.
To allow compiler optimizations, please suppress the -ol0 compiler option in 
the Compiler for HC12 Panel (Target Settings Panels -<ALT-F7>-).

This project example contains the following Groups of files:
- Sources: This Group contains your source files:
  -'fibo.c' file, the Fibonacci core program.
  This file is physically stored in the 'sources' sub-directory.

- Debugger Cmd Files: This Group contains debugger command files:
  -'startup.cmd'. This command file is executed to set up the target system right 
   after the connection has been established.
  -'reset.cmd'. This command file is executed after a user enforce reset has been 
   performed (the Reset button, menu entry or command line command has been used).
  -'preload.cmd'. This command file is executed before an application (code or symbols) 
   is loaded in the debugger.
  -'postload.cmd'. This command file is executed after an application (code or symbols) 
   has been loaded in the debugger. 

- Prm: This Group contains the linker parameter file:
  The linker parameter file is used to build the application (memory location specification...). 
  This file is/must be set up in the Linker for HC12 Panel (Target Settings Panels -<ALT-F7>-).
  The .prm file physically stored in the 'prm' sub-directory.

- Debugger Project File: This Group contains the debugger initialization file:
  The .ini file contains configuration informations for the debugger:
  Target interface settings, path information, etc. 
  Paths and environment information can be set within the debugger when choosing 
  the menu entry File | Configuration.
  The .ini file is physically stored in the project directory.

- Startup Code: This Group contains the application startup code:
  The application startup code performs several program initializations.
  You may adapt it to your own needs, but in such a case, make sure that 
  you are using a local copy.
  The current start*.c file is physically stored in the 'sources' sub-directory.
  This file is a copy of the one located in the HC12 compiler library directory.

- Libs: This Group contains the ANSI library (binary) to be linked with your application.
  The *.lib file is physically stored in the HC12 compiler library directory.

This project includes a burner command file (.bbl) in order to generate an 
SRecord file (.s19). Remove this file from 'Prm' group if no SRecord is needed.


Metrowerks