Datasheet

90 PSoC Designer IDE Guide, Document # 001-42655 Rev *B
Code Editor
assembled and linked source, they are read only. You can also access the Output tab on the source
tree in the Code Editor by selecting Tools > Options > Code Editor tab and unchecking Enable Out-
put.
4.1.3 boot.asm
This startup file resides in the source tree under Source Files and is important because it defines the
boot sequence. The components of the boot sequence are:
■ Defines and allocates the reset and interrupt vectors.
■ Initializes device configuration.
■ Initializes C environment if using the C Compiler.
■ Calls main to begin executing the application code.
When a project is created, the template file, boot.tpl, is copied into the project directory. Each time
the project is generated, the boot.asm file is generated from the local boot.tpl file.
boot.asm is re-generated every time device configurations change and application files are gener-
ated. This is done to make certain that interrupt handlers are consistent with the configuration. If you
make changes to boot.asm that you do not want overwritten, modify the local project boot.tpl file and
then re-generate file.
4.1.4 main.asm/main.c
If the C complier is not enabled, then the main.asm file is generated for applications written in
Assembly language. If the C Compiler is enabled, the main.c file is generated for a C program. This
file resides in the source tree under Source Files and is important because it holds the _main label
that is referenced from the boot sequence.
4.1.5 PSoCConfig.asm
This is a required Library Source file because it contains the configuration that is loaded at system
power-up.
PSoC Designer overwrites PSocConfig.asm when a device configuration changes and application
files are regenerated, with no exceptions. To manipulate bits, all part register values reside in this file
for your reference.
4.1.6 Additional Generated Files
Additional files are generated in association with user modules and Dynamic Reconfiguration.
Psocgpioint.inc – This file contains additional information pertaining to pin GPIO write only register
shadows. If a pin group is defined in a register set for which register shadows are allocated, then a
set of three macros are defined for each register shadow to read, set, or clear the particular bit within
the register associated with the pin. The names of the macros are keyed to the custom name
assigned to the pin and are:
■ GetCustomName_registerName
■ SetCustomName_registerName
■ ClearCustomName_registerName
CustomName is the custom name set for the pin, and registerName is the associated register
name for which a register shadow is allocated.