Table of Contents
Advertisement
•
Preserve user comments check-box, when checked assures the user comments placed after the
individual macro values are not lost when re-generating the "appconfig.h" file. This option is rarely
used as there is typically no need for the user to manually edit any comments in the "appconfig.h"
file.
•
Generate all register values check-box enables saving of all register values of the selected
peripheral modules into the "appconfig.h" file. When this option is not enabled (which is the
default state), only the registers with non-reset values are saved. Omitting the reset-value registers
in the "appconfig.h" file typically reduces a size of the module initialization code as those values
not defined in the file are not written to the peripheral registers. On the other side, this approach
requires all the modules being initialized to be in post-reset state, otherwise the result may be a
most probably a mix of previous registers state and a GCT-defined configuration.
This is a project-specific option, which is saved to the "appconfig.h" file as a macro constant named
APPCFG_DFLTS_OMITTED. This constant is set to non-zero value when the Generate all
register values option is turned off.
•
Set as default check-box to save the selected options as default ones for the GCT and the current
project.
7.2.2
Application Configuration File Structure
The application configuration header file is a common ANSI C-language header file, which
mostly contains register initialization values, but may contain other application global
declarations or macros. The GCT parses and re-generates the register-values part of the file, while
the other parts are ignored and left untouched.
In the Quick_Start projects, the application configuration file is named "appconfig.h" and resides
in the "ApplicationConfig" project folder subdirectory. This file is included by all Quick_Start
low-level driver source files where a configuration information is required.
However, the GCT can be used independently on the Quick_Start and its low-level drivers. The
GCT is capable of loading and saving the configuration file under any name.
The configuration file can be logically divided into four parts:
•
Heading is an arbitrary text before the first #define statement. Typically, the heading contains the
application or user-specific file header or commentary. This part is not modified by the GCT. The
first #define is typically a macro used to protect the file from multiple inclusion during compilation
(i.e. standard #ifndef/#define sequence).
FREESCALE SEMICONDUCTOR
Figure 7-7. Options dialog
Targeting 56F8xxx Platform
Introduction
7-7
Advertisement
Chapters
Table of Contents
