Datasheet

54 PSoC Designer IDE Guide, Document # 001-42655 Rev *B
Chip-Level Editor
2.13.3 Renaming Configurations
To rename a loadable configuration in your PSoC project:
1. Right click the loadable configuration and click Rename.
2. Type the new name.
3. Press [Enter] or click your cursor somewhere outside the folder.
2.13.4 Employing Dynamic Reconfiguration
These sections discuss how global parameters, pin settings, and code generation are dynamically
reconfigured.
2.13.4.1 Global Parameters
When using Dynamic Reconfiguration, global parameters are set in the same manner as single con-
figurations. However, changes to the base configuration global parameters are propagated to all
additional configurations. Therefore, global parameter changes made to an additional configuration
are done locally to that particular configuration.
2.13.4.2 Port Pin Settings
When using Dynamic Reconfiguration, port pin settings are similar to global parameters in that all
settings in the base configuration are propagated to additional configurations. When manually set,
port pin settings become local to the configuration.
To set port pin interrupts:
1. Open the Interconnect View of Chip-Level Editor.
2. Click the pin you want to set and select the Interrupt type you want.
3. The default pin interrupt setting is Disable. If all pin interrupts are set to disable, there is no addi-
tional code generated for the pin interrupts. If at least one pin is set to a value other than disable,
code generation performs some additional operations.
In the boot.asm file, the vector table is modified so that the GPIO interrupt vector has an entry with
the name ProjectName_GPIO_ISR. Additional files being generated are:
PSoCGPIOINT.asm
PSoCGPIOINT.inc
PSoCGPIOINT.asm – This file contains an export and a placeholder so you can enter its pin interrupt
handling code. Enter user code between the user code markers where appropriate. This file is re-
generated for each code generation cycle, but the user code will be carried forward if it is within the
user code markers.
NOTE: When opening an old project that contains a PSoCGPIOINT.asm file where user code is
entered, the user code must be copied from the backup copy in the \Backup folder into the newly
generated PSoCGPIOINT.asm file.
PSoCGPIOINT.inc – This file contains equates that are useful in writing the pin interrupt handling
code. For each pin (with enabled interrupt or custom name), a set of equates are generated that
define symbols for the data address and bit, and for the interrupt mask address and bit associated
with the pin. The naming convention for the equates is:
CustomPinName_Data_ADDR
CustomPinName_MASK
CustomPinName_IntEn_ADDR
CustomPinName_Bypass_ADDR