A Build Tool, such as the Assembler, requires information from the configuration files. There are two types of configuration data:
This data is common to all Build Tools and projects. There may be common data for each Build Tool, such as listing the most recent projects, etc. All tools may store some global data into the mcutools.ini file. The tool first searches for this file in the directory of the tool itself (path of the executable). If there is no mcutools.ini file in this directory, the tool looks for an mcutools.ini file located in the MS WINDOWS installation directory (for example, C:\WINDOWS), as the following listing shows.
\<CWInstallDir>\MCU\prog\mcutools.ini - #1 priority C:\WINDOWS\mcutools.ini - used if there is no mcutools.ini file above
If a tool is started in the default location <CWInstallDir>\CW MCU V10.x\MCU\prog directory, the initialization file in the same directory as the tool is used:
<CWInstallDir>\MCU\prog\mcutools.ini
But if the tool is started outside the CodeWarrior installation directory, the initialization file in the Windows directory is used. For example, C:\WINDOWS\mcutools.ini.
For information about entries for the global configuration file, refer to the section Global Configuration File Entries in the Appendices.
This file could be used by any Build Tool for a particular project. For information about entries for the local configuration file, refer to the section Local Configuration File Entries in the Appendices.
After opening the Assembler, you would load the configuration file for your project if it already had one. However, you will create a new configuration file for the project in this tutorial and save it so that when the project is reopened, its previously saved configuration state is used.
Now let's save this configuration in a newly created folder that will become the project directory.
The Saving Configuration as dialog box appears.
In this case, ModelT becomes the project directory in the Projects folder.
The project.ini file is created in the ModelT folder and becomes the local configuration file for this project.
The current directory for the Microcontroller Assembler is changed to your project directory.
The following image shows the assembler window displaying the current directory.
If you were to examine the project directory with the Windows Explorer at this point, it would only contain the project.ini configuration file that the Assembler just created.
The following image displays the project.ini configuration file that the Assembler just created.
If you further examined the contents of the project.ini configuration file, you would see that it contains Assembler options in the [AHC08_Assembler] portion of the file. The project.ini file for this project only has an [AHC08_Assembler] section, as the following listing displays.
[AHC08_Assembler] StatusbarEnabled=1 ToolbarEnabled=1 WindowPos=0,1,-1,-1,-1,-1,680,151,1148,491 EditorType=4
The AHC08_Assembler options are described in detail in [XXX_Assembler] Section in the Appendices.
Next, you have to set the object-file format that you will use (HIWARE or ELF/DWARF).
The HC08 Assembler Option Settings dialog box (refer to the figure listed below) appears.
Save the changes to the configuration by:
The assembler is now set with the object-file format that you have selected.
The following listing shows the project.ini file's contents, after the changes to the configuration are saved.
[AHC08_Assembler] StatusbarEnabled=1 ToolbarEnabled=1 WindowPos=0,1,-1,-1,-1,-1,680,151,1148,491 EditorType=4 Options=-F2 -L=%(TEXTPATH)\%n.lst -Li