ADC Release 3.1 Bedienungsanleitung PDF herunterladen (Seite 15)

Freescale MQX Release Notes

Freescale Semiconductor

To build all MQX libraries at once, the special mass-build project may be used. The project is

located together with the user_config.h file in directory:

<install_dir>/config/<board>/build_libs.mcp

3.10.2 Debug and Release Builds

Each CodeWarrior project in Freescale MQX™ RTOS contains multiple compiler/linker

configurations (so called build „targets“). There are always three build targets in any MQX core

component:

‐ Debug – the compiler optimizations are turned off or set to low. The compiled code is easy

to debug but may be less effective than the Release build. All output libraries (or

executables) have _d postfix in the file name (e.g. rtcs_d.lib).

‐ Release – the compiler optimizations are set to maximum. The compiled code is very hard

to debug and should be used for final applications only. There is no postfix in the output file

name (e.g. rtcs.lib).

‐ Build all –this target contains all other targets for convenient mass-build.

The Debug/Release build targets exist also in all application projects. As application projects are

targeted always to specific board, there are also other build targets available:

‐ Int. Flash Release – this target is suitable for final application deployment. When

programmed to Flash, the application starts immediately after reset. Variables are allocated

in internal SRAM memory. Application executable need to be written to Flash memory using

the Flash Programmer tool.

‐ Int. Flash Debug – same as above, only the Debug-compiled libraries are used. This target

is suitable for debugging before deployment. On boards without external memory, this is the

only target suitable for debugging larger applications. Application executable need to be

written to Flash memory using the Flash Programmer tool.

‐ Int. SRAM Debug – solely for debugging purposes with both code and variables allocated in

the internal SRAM memory. This target is unusable with larger applications. Application

executable is loaded to RAM automatically by the debugger.

Note: in this target, the RAM area of is split to Code and Data parts in approximate ratio of

8:1. It may happen that this split does not suit well all applications and may need to be

changed in linker command file (intram.lcf). Remember that this target is only suitable

for tiny MQX-only applications. This target is not available in applications where the

application can not fit into memory (RTCS, MFS or USB applications).

‐ Ext. MRAM Debug – solely for debugging purposes with code located in external MRAM

memory (available e.g. on the M52259EVB). Variables are located in internal SRAM. Part of

the external MRAM memory may also be used for additional RAM memory pools.

Application executable is loaded to MRAM automatically by the debugger.

1 2 ... 10 11 12 13 14 15 16 17 18 19 20 ... 30 31

Keine Kommentare

ADC Release 3.1 Bedienungsanleitung Seite 15