Datasheet
PSoC Designer IDE Guide, Document # 001-42655 Rev *B 89
Code Editor
4.1.2 Project File System
The project file system (workspace explorer) setup is like a standard file system. To access and edit
files simply double-click the target file. Open files appear in the main window to the right of the
source tree. The maximum number of characters allowed per line is 2,048.
Figure 4-2. Source Tree
The source tree contains these file folders:
Chip View Folder – Contains the Loadable Configurations folder that contains one or more configu-
rations. Each of the loadable configurations contains the user modules for the configuration. For
more information see “Dynamic Reconfiguration” on page 52.
Source Files Folder – Contains assembly language code and C Compiler files generated by the
system and user modules.
Headers and Library Headers Folders – Contains include files added by device configurations and
user modules.
Library Source Folder – Contains the project configuration .asm as well other project-specific refer-
ence files generated by device configuration.
If you view the source tree in the Debugger subsystem, you see an Output tab. In the Output tab you
have access to the project .lst and .mp files. Because these files are generated output from your
ROM File
.rom
…\output folder under
project directory
This file is a legacy (M8A M8B) program image
output file.
Template
.tpl
Project directory Editable template file.
Template
a
.tpl
Installation directory under
…\Templates then copied
to project directory
Template files used to generate project files
(
boot.tpl > boot.asm).
Text
Document
.txt
Project directory
Text document that contains system informa-
tion.
WNP File
.wnp
Project directory
Persistence file unique to PSoC Designer.
Contains project information restored each
time the project is opened.
XML
Document
a
.xml
Project directory Device resource file.
a. If you are using a version control system to track project process, copy the above checked files including m8c.inc (as the only .inc file) and
not including boot.asm (as it is recreated during the device configuration process). Also include any *INT.asm files that have been modified.
All other project files will be regenerated during the device application configuration process.
Table 4-1. File Types and Extensions<Italic> (continued)
Type Extension Location Description