Datasheet

48 PSoC Designer IDE Guide, Document # 001-42655 Rev *B
Chip-Level Editor
strings if you safely define the interrupt vector and install your own handler. If there is no interrupt
handler for a particular interrupt vector, the comment string “// call void_handler” is inserted
in place of the substitution string.
NOTE: If you install an interrupt handler and make changes directly to boot.asm, the changes are
not preserved if application generation is executed after you make the changes. If you make
changes to boot.asm that you do not want overwritten, hard code the change in boot.tpl (template for
boot.asm).
2.11 Configuration Data Sheets
Once you have configured your device and generated application files, you can produce, view, or
print a data sheet based upon how you configured your project device. The configuration data sheet
is self-contained in its own folder in the project directory and can be viewed independently of PSoC
Designer by opening configreport.xml in Internet Explorer. (If you need to move or send someone
the file, you must move/send the entire directory of \ConfigDataSheet.)
To produce and view a data sheet:
1. Select View > Configuration Data Sheet. This opens an independent browser window that shows
the current configuration data sheet.
NOTE: If changes were made in the Device Editor and a “Generate Application” was not per-
formed, then PSoC Designer shows a dialog box asking for verification before performing Gener-
ate Application. If you select No, then the data sheet reflects the configuration before the
changes were made.
2. To print the data sheet click the standard Print icon or File > Print.
2.12 APIs and ISRs
APIs (Application Programming Interfaces) and ISRs (Interrupt Service Routines) are also generated
during the device configuration process in the form of *INT.asm, .h, and .inc files. These files provide
the device interface and interrupt activity framework for source programming. Figure 2-40, illustrates