This project is a generic base for an ANSI-C project for the MC9S08GB60. This project is prepared to be designed with Processor Expert. The CPU MC9S08GB60 is inserted into the Processor Expert project panel, in the Debug and Release configurations. Change of the configuration is possible by the mouse double-click on it. All the installed Embedded Components are accessible in the Component library window, grouped into folders according to their function. The mouse double-click on selected Embedded Component in the Component library window adds the Component to the project. The mouse double-click on the Component icon in the Project panel opens the Component Inspector window, which is used to set the Component properties. Source code is generated after selecting the Code Design 'Project_name.mcp' menu command from the CodeWarrior main window (Processor Expert | Code design 'Project_name.mcp'). Use the Component methods and events to write your code in the main module 'Project_name'.c and the event module Events.c. For more help please read Processor Expert help (Processor Expert | Help | 'Topic'). Available CodeWarrior Targets: # HCS08 BDM_HCS08 Target Interface - HCS908GB60 ANSI-C Application Template ########################################################################### The project =========== This project conatins two Codewarrior target: 1- "Ram Application" CodeWarrior target Using this target, the code of generated application 'Appli_Ram.abs' is located in the Internal RAM memory of the M68HCS908GB60. NOTE: When starting the debugger, the derivative flash can be automatically erased and the project application programmed to the onchip flash memory. The onchip flash memory will be erased and written each time you perform a load. Please check "preload.cmd" and "postload.cmd" command files execution to enable/disable this process. The execution of these command files is monitored with the BDM_HCS08 | Command Files dialog. WARNING: In order to Flash, please make sure the correct programming voltage is supplied to the microcontroller. 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 HCS08 Panel (Target Settings Panels --). 2- "Flash Application" CodeWarrior target Using this target, the code of generated application 'Appli_Flash.abs' is located in the on-chid flash memory of the M68HCS908GB60. WARNING: The onchip flash memory will be erased and written each time you perform a load. Please check "preload.cmd" and "postload.cmd" command files execution to enable/disable this process. The execution of these command files is monitored with the BDM_HCS08 | Command Files dialog. WARNING: In order to Flash, please make sure the correct programming voltage is supplied to the microcontroller and the correct MCUID has been used. NOTE: For this target, all the local variables in the debugger Data component are not visible due to Compiler optimizations. To disable compiler optimizations in order to be able to see all the local variables in the debugger Data component, please add the -ol0 compiler option in the Compiler for HC08 Panel (Target Settings Panels --). The following folders are used in CodeWarrior project window: - User modules: contains your sources. The main module 'Project_name'.c and event module Events.c are located here after the Processor Expert code generation. - Secure\Unsecure: This Group contains debugger command files which can be used in order to secure or unsecure the HCS908GB60: -'p&e_secure_hcs08.cmd'. This command file can be executed to secure the HCS908GB60. -'p&e_erase_unsecure_hcs08.cmd'. This command file can be executed to unsecure the HCS908GB60. These files are physically stored in the 'cmd' sub-directory. To use them, use the BDM_HCS08 | Secure/Unsecure menu entry. - 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. Currently, this file contains debugger commands to erase and program the onchip flash memory with the application. -'postload.cmd'. This command file is executed after an application (code or symbols) has been loaded in the debugger. Currently, this file contains debugger commands to halt the programming process. -'vppon.cmd'. This command file is executed before Non Volatile Memory is erased or programmed using the NVMC dialog or the corresponding debugger command. -'vppoff.cmd'. The Vppoff command file is executed after Non Volatile Memory has been erased or programmed using the NVMC dialog or the corresponding debugger command. These files are physically stored in the 'cmd' sub-directory. - 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 HC08 Panel (Target Settings Panels --). The .prm file physically stored in the 'prm' sub-directory. Here two .prm files are available, one for each Codewarrior target. - 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. Here two .ini files are available, one for each Codewarrior target. This allows to have separates debugger settings for each Codewariior target. - 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 curent start*.c file is physically stored in the 'sources' sub-directory. This file is a copy of the one locatated in the HC08 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 HC08 compiler library directory. - Generated code: this folder appears after the Processor Expert code generation and contains generated code from Processor Expert. - Doc: other files generated from the Processor Expert (documentation) 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.