|
|
|
Compiler CodeWarriorColdFireV1
CodeWarrior ColdFireV1 C Compiler
Settings:
(Parameters of the compiler-specific code generation and compilation.)
-
Compiler - Compiler identification.
-
Unhandled vectors - This property allows you to specify generation of ISR for interrupts unused by Processor expert beans.
Value 'One handler for all' will generate one ISR for all interrupts not used by PE beans and value 'Own handler for every' allows you to have one ISR for each unused interrupt.
There are 2 modes:
-
Generate macros - Generate macros to the project modules. If intention and implementation of some beans' methods allow effective representation of methods as macros, these methods will be generated as macros by setting of this property to "yes". Generating methods as macros can reduce code size. Disabling macros can facilitate debugging of the application code.
-
FLASH registers initialization - Generate initialization of registers placed in FLASH memory. It may be necessary to disable this option e.g. when a serial monitor is used.
-
User initialization - In this group user can specify his own initialization code that will be executed after reset (see also the Reset Scenario).
-
User data declarations - In this property user can specify own data declarations. Lines from this list will be generated before function __initialize_hardware located in the CPU module.
-
User code before PE initialization - In this property user can specify own initialization code. Lines from this list will be generated before any code generated by PE to the function __initialize_hardware located in the CPU module.
-
User code after PE initialization - In this property user can specify own initialization code. Lines from this list will be generated after the PE initialization code in the function __initialize_hardware located in the CPU module.
-
Generate LCF file - Rewrite LINKFILE during code generation. If you would like to add some parts to the link file you should set this property to 'no'. In the first time this property should be set to 'yes' to create linker parameter file.
The following items are available only if the group is enabled (the value is "yes"):
-
Stack size - Size of the system stack in bytes.
-
Heap size - Size of the system heap in bytes.
-
Memory segments - This group contains definition of memory segments (areas) on the target board for linker parameter file.
-
Set default memory segments - Click to set default memory segments according to current CPU bean settings (memory mapping and memory model). See CPU memory map window for detail about current memory mapping and available sizes.
-
ROM/RAM segments - List of available memories. For each memory you must specify: start address, length in bytes and type: ROM or RAM. You must define at least two memories: for code and for data.
One Item of the list looks like:
Segment0 - Definition of ROM/RAM memory segment (area) for data or code.
The following items are available only if the group is enabled (the value is "Enabled"):
-
Name - Segment name (for segment identification within placement).
-
Access permissions - Definition of access permitions.
-
Read - The memory segment has READ permission
-
Write - The memory segment has WRITE permission
-
Execute - The memory segment has EXECUTE permission
-
Address - Start address of the memory segment (area). This address must be in internal or external memory (if an external bus is supported by the selected derivative). Addresses greater then 0xFFFF are considered to be a global addresses.
-
Size - Size of the memory segment (area).
|
|