Datasheet
PSoC Designer IDE Guide, Document # 001-42655 Rev *B 57
Chip-Level Editor
2.13.4.5 PSoCDynamic Files
Three files are generated when additional configurations are present in a project:
PSoCDynamic.inc
PSoCDynamic.asm
PSoCDynamicINT.asm
PSoCDynamic.inc
The PSoCDynamic.inc file is always generated. It contains a set of equates that represent the bit
position in the active configuration status variable, and the offset to index the byte in which the status
bit resides, if the number of configurations exceeds eight. A third equate for each configuration indi-
cates an integer index representing the ordinal value of the configuration.
PSocDynamic.asm
The PSoCDynamic.asm file is always generated. It contains exports and functions that test whether
or not a configuration is loaded. The naming convention for these functions is IsOverlayName-
Loaded.
PSoCDynamicINT.asm
The PSoCDynamicINT.asm file is generated only when the user module placement between config-
urations results in both configurations using a common interrupt vector. The reference to the
Dispatch_INTERRUPT_n function is resolved in this file. For each conflicting interrupt vector, one
of these ISR dispatch sets is generated. The ISR dispatch has a code section that tests the active
configuration and loads the appropriate table offset into a jump table immediately following the code.
The length of the jump table and the number of tests depends on the number of user modules that
need the common vector, rather than the total number of configurations. The number of conflicts can
equal the number of configurations, if each configuration utilizes the common interrupt vector. Gen-
erally, there will be fewer interrupt conflicts on a per-vector basis.
2.13.4.6 Active Configurations Display
The set of currently active configurations is displayed in the Config tab of the memory map during
Debugger halts. The display lists all project configurations with the status for each currently loaded
configuration marked Active.
Note: The display is not valid immediately after a reset. The PSoC initialization code must run before
the Config tab display is valid.
2.13.4.7 IO Register Labels
The Debugger IO register bank labels (Bank 0, Bank 1) are updated to match the user modules
defined in the currently active configurations.
2.13.4.8 Limitations
The new displays are based on a bitmap of loaded configurations maintained by the LoadConfig
and UnloadConfig routines, which are generated by the Chip-Level Editor. This bitmap can get out
of synchronization with the actual device configuration in several ways:
The bitmap’s RAM area can be accidentally overwritten.
If overlapping (conflicting) configurations are loaded at the same time, the register labels will be
scrambled.