Use the OS Awareness tab to specify the operating system (OS) that resides on the target device.
Use the Target OS list box to specify the OS that runs on the target device, or specify None to have the debugger use the bareboard.
If you select OSEK as the target OS, you are required to specify the path of the OSEK Run Time Interface (ORTI) description file. You can click any of the following to navigate and browse to the ORTI file.
- Workspace - Click to open the Folder Selection dialog box and select a workspace location for the project. This is the directory that will contain the plug-ins and features to build, including any generated artifacts.
- File system - Click to open the Browse For Folder dialog box and select a folder.
- Variables - Click to open the Select build variable dialog box and select a variable to specify as an argument for the build directory, or create and configure simple build variables which you can reference in build configurations that support variables.
Selecting OSEK visualizes the RTOS's internal objects, like tasks, alarms, counters, and resources. Other objectives are:
- contains basic trace implementation that records and displays the last N values of the traceable attributes.
- enables multiple debuggers and handle multiple OSEK applications.
- enables components reuse.
Once the ORTI file is specified, click Apply and Debug. The ORTI file is automatically loaded at process creation time. Check the OSEK console to ensure whether the file was loaded or not. Any I/O exceptions or parse errors will be spilled out in the console. Once the ORTI file is successfully loaded, the System Browser view appears.
The three tabs in the System Browser view are: Tasks, Implementation, and Trace.