Datasheet

56 PSoC Designer IDE Guide, Document # 001-42655 Rev *B
Chip-Level Editor
restore the base configuration user modules. The ReloadConfig_xxx function ensures the integ-
rity of the write only shadow registers. Respective load tables are generated for these functions in
the PSoCConfigTBL.asm file.
An additional unload function is generated as UnloadConfig_Total. The
UnloadConfig_Total function loads these tables:
 UnloadConfigTBL_Total_Bank0
 UnloadConfigTBL_Total_Bank1
These tables include the unload registers and values for all PSoC blocks. The active configuration
status variable is also set to ‘0’. The global registers are not set by this function.
The name of the base configuration matches the name of the project. The project name is changed
to match the base configuration name if you change the name of the base configuration (from the
project name).
A C callable version of each function is defined and exported so that these functions are called from
a C program.
PSoCConfigTBL.asm
The PSoCConfigTBL.asm file contains the personalization data tables used by the functions defined
in PSoCConfig.asm. For static configurations, there are only two tables defined;
LoadConfigTBL_projectname_Bank0 and LoadConfigTBL_projectname_Bank1, which
support the LoadConfig_projectname function. These tables personalize the entire global regis-
ter set and all registers associated with PSoC blocks that are used by user modules placed in the
project.
For projects with additional configurations, a pair of tables are generated for each
LoadConfig_xxx function generated in PSoCConfig.asm. The naming convention follows the
same pattern as LoadConfig_xxx and uses two tables: LoadConfigTBL_xxx_Bank0 and
LoadConfigTBL_xxx_Bank1. These tables are used by UnloadConfig_xxx. The labels for
these tables are exported at the top of the file.
Loading – The tables for the additional configurations’ loading function differ from the base configu-
ration load table. The additional configuration tables only include those registers associated with
PSoC blocks that are used by user modules placed in the project, and only those global registers
with settings that differ from the base configuration. If the additional configuration has no changes to
the global parameters or pin settings, only the placed user module registers are included in the
tables.
Unloading – The tables for additional configurations’ unloading functions include registers that de-
activate any PSoC blocks that were used by placed user modules, and all global registers which
were modified when the configuration was loaded. The registers and the values for the PSoC blocks
are determined by a list in the device description for bit fields to set when unloading a user module,
and are set according to the type of PSoC block. The exceptions are the
UnloadConfigTBL_Total_Bankn tables, which include the registers for unloading all PSoC
blocks.
boot.asm
The boot.asm file is generated similarly to a project that has no additional configurations, unless
there are one or more configurations that have user modules placed in such a way that common
interrupt vectors are used between configurations. In this case, the vector entry in the interrupt vec-
tor table will show the line ljmp Dispatch_INTERRUPT_n instead of a user module defined ISR.