没有合适的资源？快使用搜索试试~ 我知道了~

首页汽车编程- TASKING RTOS for TriCore 使用指南

汽车编程- TASKING RTOS for TriCore 使用指南

汽车编程

需积分: 0 10 下载量 105 浏览量更新于2024-03-21 收藏 1.62MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

试读

140页

The document "Using the TASKING RTOS for TriCore" provides a comprehensive guide on how to effectively utilize the TASKING Real-Time Operating System (RTOS) for TriCore microcontrollers in automotive programming. This document, dated November 13, 2017, is copyrighted by TASKING BV and emphasizes the importance of adhering to copyright regulations. The TASKING RTOS for TriCore is designed to meet the stringent requirements of real-time embedded systems in the automotive industry, offering features such as task management, interrupt handling, synchronization mechanisms, and memory management. By leveraging the capabilities of the TASKING RTOS, developers can streamline the development process, optimize performance, and ensure the reliability of automotive applications. Key topics covered in this document include an introduction to the TASKING RTOS for TriCore, an overview of the RTOS architecture, task scheduling and prioritization, inter-task communication, memory management, and debugging techniques. The document also provides practical examples and code snippets to illustrate the implementation of various RTOS functionalities in automotive programming. It is important to note that while users are permitted to print the document for personal use, restrictions apply to copying, posting on network computers, broadcasting in any media, and making modifications to the document without authorization from TASKING BV. Unauthorized duplication of the document, whether in part or in whole, is strictly prohibited. In conclusion, the "Using the TASKING RTOS for TriCore" document serves as a valuable resource for automotive developers seeking to enhance their programming skills with the TASKING RTOS. By following the guidelines and best practices outlined in this document, developers can effectively leverage the capabilities of the TASKING RTOS to create robust and efficient automotive applications.

资源详情

资源推荐

DescriptionExtension

These configuration files are intermediate files (ISO C) generated by the

TOC compiler after processing the OIL file. The files (g_*) are compiled

together with the RTOS source files to build the RTOS objects of the

project. The file flag.h is an extra interface for the application software.

The file oil.orti is the run-time debug interface. They are rebuilt when

you change your OIL file.

g_conf.c

g_conf.h

g_conf_indep.h

flag.h

oil.orti

RTOS source files

The source code files of the RTOS are located in

$(PRODDIR)/ctc/rtos/ They are used by all the RTOS projects to

build their RTOS libraries.They should never be removed or modified.

When you generate RTOS code for your application, these files are copied

to the rtos directory in your project.

c_*.c

c_*.h

t_*.c

t_*.h

The RTOS application interface rtos.h is located in

$(PRODDIR)/ctc/rtos and constitutes the only interface for your code

as an RTOS user. It is copied to your the rtos directory in your project.

rtos.h

Implementation OIL file

The implementation OIL file, which is present in the RTOS Eclipse plugin,

is used by the TASKING OIL compiler for all RTOS applications. It imposes

how and what can be configured in this current RTOS release. It should

never be removed or modified.

rtos_impl.oil

Using the TASKING RTOS for TriCore

The following figure shows the relation between the files in an RTOS project and the development process.

2.2. Creating an RTOS Project

1. First make sure you have an existing project. This is explained in the Getting Started manual of the

toolset. In this example we assume you have a project called myproject.

2. From the File menu, select New » TASKING RTOS Configuration.

The New TASKING RTOS Configuration wizard appears.

3. Select the Project folder for the RTOS configuration file: type the name of your project (myproject)

or click the Browse button to select a project.

Getting Started

4. In the File name field, enter a name for the RTOS configuration file, for example myproject.tskoil

and click Finish.

A new RTOS configuration file is added to the project with extension .tskoil, and it is opened

automatically in the TASKING RTOS Configurator.

Note that if you right-click on a project name and select New » TASKING RTOS Configuration the project

name and file name are already filled in.

2.3. Configuring the RTOS Objects and Attributes

When you have added a new RTOS configuration file, the TASKING RTOS Configurator initially looks

similar to this:

You use the TASKING RTOS Configurator to add and/or change RTOS objects and attributes.You can

add tasks, events, resources, alarms, interrupts, messages and counters.

As an example, make changes to this RTOS configuration as follows:

1. From the RTOS menu, select New » TASK.

The New TASK Object dialog appears.

Using the TASKING RTOS for TriCore

2. In the Name field enter task0 and click OK.

TASK task0 is added to the configuration.

3. Repeat steps 1 and 2 to add tasks task1 and task2.

4. From the RTOS menu, select New » EVENT.

The New EVENT Object dialog appears.

5. In the Name field enter E1 and click OK.

EVENT E1 is added to the configuration.

6. Repeat steps 4 and 5 to add event E2.

7. Click on the New_CPU value and change it to MyRTOS.

8. Click on the New_OS value and change it to StdOS.

9. Expand the OS object and change the ORTI attribute from FALSE to TRUE.

This will provide the debugger with as much RTOS debug information as possible via the ORIT

interface.

10. Click on the APPMODE1 value and change it to AP1.

11. Expand TASK task0 and change AUTOSTART to TRUE.

The APPMODE[0] attribute appears.

12.

Click in the Value field of APPMODE[0] and click on the Browse button .

The Select APPMODE Objects dialog appears.

13. Select AP1 and click OK.

APPMODE[0] is changed into APPMODE[1] indicating it contains 1 APPMODE object.

14.

Click in the Value field of EVENT[0] and click on the Browse button .

The Select EVENT Objects dialog appears.

15. Select E1 and E2 and click OK.

EVENT[0] is changed into EVENT[2] indicating it contains 2 EVENT objects.

16. Repeat steps 13 and 14 to add EVENT E1 to task1, and add EVENT E2 to task2

Getting Started

The TASKING RTOS Configurator view now looks similar to this:

17.

From the File menu, select Save (Ctrl+S) or click .

The file will be saved and a question appears if you want to generate the RTOS code.

18. Click Yes to generate the RTOS code.

An rtos directory with the RTOS code is generated in your project directory.

2.4. Generate RTOS Code

Once you have changed the RTOS configuration file, you can generate the RTOS code. As seen in the

previous example, this can be done automatically each time you save the configuration. At any time you

can also click the Generate Code button ( ).

Using the TASKING RTOS for TriCore

剩余139页未读，继续阅读

粉丝: 161
资源: 382

上传资源快速赚钱

我的内容管理展开

我的资源快来上传第一个资源

我的收益

登录查看自己的收益

我的积分登录查看自己的积分

我的C币登录后查看C币余额

我的收藏

我的下载

下载帮助

汽车编程- TASKING RTOS for TriCore 使用指南

汽车编程-TASKING for TriCore 安装.pdf

汽车编程-Tasking for TriCore 安装（官方正版教程）.pdf

汽车编程-英飞凌单片机编译器TASKING TriCore Eclipse IDE.pdf

汽车编程-Using the TASKING Software Platform for AURIX.pdf

汽车编程-Using the TASKING Pin Mapper for AURIX.pdf

汽车编程-TASKING VX-toolset for TriCore User Guide.pdf

汽车编程-Getting Started with the TASKING VX-toolset for TriCore.pdf

linker-script-language-lsl-tips-tricks-for-tasking-tricore-toolset.pdf

汽车编程-TASKING VX-toolset for PCP User Guide.pdf

汽车编程-TASKING VX-toolset for 8051 User Guide.pdf

汽车编程-TASKING VX-toolset for ARM User Guide.pdf

汽车编程-TASKING VX-toolset for MCS User Guide.pdf

汽车编程-TASKING Script Debugger User Guide.pdf

TASKING-WP-AURIX-Multicore-Tricore-Programming.pdf

gcc-to-tasking-migration-guide-for-infineon-aurix.pdf

LSL-using-Control-Program.pdf

infineon_TASKING Tricore Oveylay for Calibration TASKING Tricore标定用覆盖.pdf

TASKING TriCore tools Linker tips - tricks-WEB.pdf

最新资源