Datasheet

PSoC Designer IDE Guide, Document # 001-42655 Rev *B 47
Chip-Level Editor
2.10 Source Files Generated by Generate Project Operation
Table 2-1 lists and describes the source files generated by the Generate Project operation.
NOTE: If you undo placement of a user module but leave it in your selected collection and generate
application files, associated .asm files remain (just not be updated). If you undo placement and
delete a user module from your collection then generate application files, all associated .asm files
are deleted (removed from source tree project files).
2.10.1 About the boot.asm File
When device configuration files are generated, the boot.asm file is updated. Among other things, this
file includes a jump table for interrupt handlers. (Additional details regarding this file are found in “File
Definitions and Recommendations” on page 87.)
The entries in the interrupt table are handled automatically for interrupts employed by user modules.
For example, a Timer8 User Module uses an interrupt. The interrupt-vector number depends on
which PSoC block is assigned to the Timer8 instance; vector 2 for PSoC digital block 0, vector 3 for
block 1, and so on.
During the device configuration process, the ISR name is added to the appropriate interrupt-vector
number. The interrupt handler is included in a file that is named instance_nameint.asm, where
instance_name is the name given to the user module. For example, if the user module is named
Timer8_1, then the ISR source file is named Timer8_1INT.asm. All API files generated during the
device configuration process follow this naming convention. The following are the API files that
would be generated for a user module named Timer8_1:
 Timer8_1.inc
 Timer8_1.h
 Timer8_1.asm
 Timer8_1INT.asm
The boot.asm file is based on a file named boot.tpl. You can make changes to boot.tpl and those
changes are reflected in boot.asm whenever the application is generated. Do not change any strings
with the form `@INTERRUPT_nn` where nn = 0 to 15. These substitution strings are used
when device configuration application files are generated. However, you can replace substitution
Table 2-1. Source Files Generated by Generate Application
Name Overwritten Description
…/lib/PSoCConfig.asm
Yes Configuration loaded upon system access
…/lib/PSoCCOnfigTBL.asm
Yes Contains chip configuration
Boot.asm
Yes Boot code and initial interrupt table
…/lib/<User module name>.asm
Yes User module API source
…/lib/<User module name>.h
Yes User module API C include header
…/lib/<User module name>.inc
Yes User module API assembly include
…/lib/<User module name>INT.asm
Yes
*
* User code markers can be used to preserve sections in the file.
User module interrupt .asm file (if needed)
…/lib/<Project name>API.h
Yes Project API include header
…/lib/<Project
Name>_GlobalParameters.inc
Yes Project parameters include
main.asm
No Main code