Freescale Semiconductor Microcontrollers - Manual (Page 190)

Real Time Kernel Awareness
OSEK Kernel Awareness
190 Microcontrollers Debugger Manual
END
PLACEMENT
...
OS_DATA INTO RTK_SEC;
...
END
The source file (for example: rtk.c) has to be compiled and listed in the NAMES
section of the linker parameter file. To force linking, the name of the object file has to be
immediately followed by a '+'. In this example the variable is linked to the address
0x1040.
If an application is prepared in this way, all declared variables may be inspected in the
data windows of the Debugger. There is no restriction in the complexity of the structures
to describe the global data of the kernel.
NOTE Do not open the terminal window during testing. Errors detected during
reading of a PRM file are written to this window.
OSEK Kernel Awareness
OSEK Kernel provides a framework for building real-time applications.
OSEK Kernel awareness within the debugger allows you to debug your application from
the operating system perspective.
The CodeWarrior Debugger supports OSEK ORTI compliant real-time operating systems
and offers dedicated kernel awareness, using the information stored in your application's
ORTI file.
With CodeWarrior OSEK kernel awareness, you can monitor kernel task information,
semaphores, messages, queues, resources allocations, synchronization, communicating
between tasks, etc.
ORTI describes the applications in any OSEK implementation:
• A set of attributes for system objects.
• A method for interpreting the data obtained.