Datasheet

PSoC Designer IDE Guide, Document # 001-42655 Rev *B 55
Chip-Level Editor
 CustomPinName_DriveMode_0_ADDR
 CustomPinName_DriveMode_1_ADDR
 CustomPinName_IntCtrl_0_ADDR
 CustomPinName_IntCtrl_1_ADDR
The CustomPinName used in the substitution is replaced by the name entered for the pin during
code generation. Custom pin naming allows you to change the name of the pin. The name field is
included in the pin parameter area of the pinout diagram.
The Name column in the Pin Parameter Grid shows the names assigned to each of the pins. The
default name shows the port and bit number. To rename the pin, double-click the name field and type
the custom name. Note that the name must not include any embedded spaces.
The effect of the name is primarily used in code generation when the pin interrupt is enabled. The pin
name is appended to the equates that are used to represent the address and bit position associated
with the pin for interrupt enabling and disabling, as well as testing the state of the port data.
2.13.4.3 Code Editor
There are no direct changes in Code Editor with regards to Dynamic Reconfiguration. The additional
files generated are placed in the Library Source and Library Headers folders of the source tree.
Library source files that are associated with an additional configuration are shown under a folder with
the name of the configuration. This partitions the files so that the source tree view is not excessively
long.
2.13.4.4 Code Generation
When configurations are present, additional code is generated to enable the application to load or
operate with the configurations. PSoCConfig.asm is generated.
PSoCConfig.asm
The static file PSoCConfig.asm contains:
Exports and code for:
 LoadConfigInit – Configuration initialization function
 LoadConfig_projectname – Configuration loading function
Code only for:
 LoadConfig – General load registers from a table
For projects with additional configurations, a variable is added to the project that tracks the loaded
configurations. The LoadConfig_projectname function sets the appropriate bit in the active con-
figuration status variable.
Additional functions named LoadConfig_ConfigurationName are generated with exports that
load the respective configuration.
For each LoadConfig_xxx function, an UnloadConfig_xxx function is generated and exported
to unload each configuration, including the base configuration. The UnloadConfig_xxx_Bankn
functions are similar to the LoadConfig_xxx functions except that they load an
UnloadConfigTBL_xxx_Bankn and clear a bit in the active configuration status variable. In these
functions, the global registers are restored to a state that depends on the currently active configura-
tion.
With regard to the base configuration, UnloadConfig_xxx and ReloadConfig_xxx functions are
also generated. These functions load and unload only user modules contained in the base configura-
tion. When the base configuration is unloaded, the ReloadConfig_xxx function must be used to