ETAS ASCET V6.4 AUTOSAR 使用指南

autosar

用户手册

需积分: 47 31 浏览量更新于2024-07-09 8 收藏 3.09MB PDF 举报

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

30元优惠券

"ETAS autosar 用户手册.pdf 是一份关于如何使用 ETAS 在 AUTOSAR (AUTomotive Open System ARchitecture) 环境中进行开发的指南。这份用户手册适用于那些希望掌握 ETAS 工具集在AUTOSAR平台应用的用户。手册可能包含了详细的操作步骤、功能介绍以及安全须知等内容。" ETAS autosar 用户手册是学习和理解如何有效利用 ETAS 工具集进行AUTOSAR系统开发的重要参考资料。AUTOSAR 是一种汽车行业广泛采用的开放标准，旨在标准化汽车软件的架构，以便于不同供应商之间的合作和软件复用。手册的介绍部分强调了使用文档的注意事项和法律条款。数据未经ETAS GmbH的特别许可不得修改或复制，并且只有在拥有相应许可证的情况下才能使用相关软件。此外，文档的版权受法律保护，未经授权，禁止任何形式的复制、分发、传输或翻译。手册中包含的安全建议部分对正确使用ETAS工具给出了指导。例如，它提到了正确使用的方法，安全指示的标记方式，以及对产品技术状态的要求，这些都是确保用户安全和系统稳定运行的重要准则。用户信息部分可能涵盖用户界面、用户配置以及可能的故障排查等内容。 1.1.1 正确使用部分详细阐述了如何按照正确的操作流程来使用ETAS工具，以避免误操作导致的问题。 1.1.2 标签安全指示部分可能涉及到如何理解和遵循各种安全警示标签，这些标签用于提示潜在的风险和操作限制。 1.1.3 对产品技术状态的需求部分可能列出了使用ETAS工具前需要确保的硬件和软件环境，以确保兼容性和稳定性。 1.2 系统信息可能涵盖了ETAS工具集与AUTOSAR系统的集成情况，包括支持的AUTOSAR版本、系统配置要求等。 1.3 用户信息可能提供有关用户界面、定制选项、用户手册的更新和维护等方面的指导，帮助用户更好地适应和操作ETAS软件。由于提供的内容有限，完整的用户手册将详细解释每个功能模块的使用方法，包括创建和管理AUTOSAR组件、建立通信接口、调试和测试等环节。对于在AUTOSAR环境下工作的软件工程师来说，这是一份不可或缺的参考资料。

资源详情

资源推荐

ETAS Introduction

ASCET V6.4 AUTOSAR User’s Guide 16

 "AUTOSAR Overview"

This chapter contains a brief introduction to AUTOSAR.

 "Developing Software Components in ASCET"

This chapter describes how to configure ASCET for developing AUTOSAR software

components, approaches for creating software components, and working with the RTE

Generator.

 "Data Types (AUTOSAR R3.1.5 or Lower)" and "Data Types (AUTOSAR R4.*)"

These chapters introduce data types used in AUTOSAR, and explain how to use them

in ASCET.

 "Interfaces"

This chapter introduces the AUTOSAR interfaces supported by ASCET.

 "Software Component Types"

This chapter introduces software component types and ports, and explains how to use

them in ASCET.

 "Internal Behavior"

This chapter first outlines the basic framework for EVENTS and runnable entities

before showing how to configure the RTE to achieve different types of runnable

entity/interface interaction.

 "Modes"

This chapter explains how to define application modes that can be used by software

components to control the execution of runnable entities.

 "Implementing Software Components"

This chapter explains how to model software components in ASCET so that the

objects required by the RTE are declared and how to use the RTE API generated by

the RTE generator.

 "ETAS Contact Addresses"

1.3.3 How to use this Manual

The user’s guide is available electronically and can be viewed on the screen at any time.

Using the index, full-text search, and hypertext links, you can find references fast and

conveniently (see ASCET V6.4 AUTOSAR_UG.pdf).

The database AUTOSAR_UG_Tutorial is provided with the ASCET installation. The

examples depicted in this document are modeled in the Solutions folder. The

corresponding ASCET-generated code can be found on the Windows file system, in the

subdirectory generated code_Solutions contained in the database.

Documentation Conventions

Instructions are phrased in a task-oriented format as shown in the following example:

To reach a goal:

 Execute operation 1.

Explanations are given below an operation.

 Execute operation 2.

 Execute operation 3.

In this manual, an

action

is a sequence of operations that need to be executed in order to

reach a certain goal. The title of an action usually expresses the result of the operations,

such as "To create a new component" or "To rename an item". The action descriptions often

include screenshots of the corresponding ASCET window or dialog window related to the

action.

ETAS Introduction

ASCET V6.4 AUTOSAR User’s Guide 17

Typographic Conventions

The following typographical conventions are used in this document:

OCI_CANTxMessage msg0 =

Code snippets are presented on a gray background and in

the Courier font.

Meaning and usage of each command are explained by

means of comments. The comments are enclosed by the

usual syntax for comments.

Select File  Open.

Menu options are shown in blue boldface.

Click OK.

Buttons are shown in blue boldface.

Press <ENTER>.

Keyboard commands are shown in angled brackets and

SMALL CAPS.

The "Open File" dialog window

is displayed.

Names of program windows, dialog windows, fields, etc.

are shown in quotation marks.

Select the file setup.exe

Text in drop-down lists on the screen, program code, as

well as path- and file names are shown in the Courier

font.

distribution

is always a one-

dimensional table of sample

points.

General emphasis and new terms are set in

italics

The OSEK group (see

http://www.osekvdx.org) has

developed certain standards.

Links to internet documents are set in blue underlined font.

Important notes for the users are presented as follows:

Tip

Important note for the users...

1.3.4 Related Documents

More detailed information on the AUTOSAR features of ASCET is given in the ASCET online

help, sections "Software Component Editor" and "AUTOSAR Interfaces".

The following related documents are installed with the respective software:

 ASCET Getting Started manual (ASCET V6.4 Getting Started.pdf)

 ASCET-SE User's Guide (ASCET-SE V6.4 Users Guide.pdf)

 RTA-RTE User's Guide and other RTA-RTE documentation (available via the Windows

Start menu, ETAS program group, RTA-RTE

<x.y>

 Documents 

)

These documents are also available in the Download Center of the ETAS website.

1.4 Definitions and Abbreviations

ASCET

Development tool for control unit software

ASCET-MD

ASCET Modeling and Design

AUTOSAR

Automotive Open System Architecture; see http://www.autosar.org/

ETAS AUTOSAR Overview

ASCET V6.4 AUTOSAR User’s Guide 19

2 AUTOSAR Overview

Today, special effort is needed when integrating software components from different

suppliers in a vehicle project comprising networks, electronic control units (ECUs), and

dissimilar software architectures. While clearly limiting the reusability of automotive

embedded software in different projects, this effort also calls for extra work in order to

provide the required fully functional, tested, and qualified software.

By standardizing, inter alia, basic system functions and functional interfaces, the AUTOSAR

partnership aims to simplify the joint development of software for automotive electronics,

reduce its costs and time-to-market, enhance its quality, and provides mechanisms required

for the design of safety relevant systems.

To reach these goals, AUTOSAR defines an architecture for automotive embedded software.

It provides for the easy reuse, exchange, scaling, and integration of those ECU-independent

software components that implement the functions of the respective application.

The next sections briefly describe the AUTOSAR process for the development of application

software components. For more detailed information the reader can refer to the AUTOSAR

documents at the AUTOSAR website: http://www.autosar.org/.

2.1 AUTOSAR Basic Approach

Application software is the name given in AUTOSAR to vehicle functions. Each application is

decomposed into one or more

software components

(SWCs), which are designed to be both

CPU- and location-neutral. An AUTOSAR application software component can be mapped to

any available ECU during system configuration.

The abstraction of the SWC environment is called the

virtual function bus

(VFB). In each real

AUTOSAR ECU, the VFB is mapped by a specific, ECU-dependent implementation of the

platform software. The AUTOSAR platform software is split into two major areas of

functionality: the runtime environment (RTE) and the

basic software

(BSW).

The BSW provides communications, I/O, and other functionality that all software

components are likely to require, e.g., diagnostics and error reporting, or non-volatile

memory management.

Application SWCs have no direct access to the BSW. This means that components cannot,

for example, directly access operating system or communication services. The

runtime

environment

provides the interface between software components, BSW modules, and

operating systems (OS). Concerning the interconnection of SWCs, the RTE acts like a

telephone switchboard. This is similarly true of components that reside either on single ECUs

or networked ECUs interconnected by vehicle buses.

In AUTOSAR, the OS calls the runnable entities of the SWCs through the RTE. RTE and OS

are the key modules of the basic software with respect to controlling application software

execution.

ETAS has been supplying the auto industry with automotive operating systems for more

than a decade: ERCOS

and RTA-OSEK. The RTA-RTE AUTOSAR Runtime Environment and

RTA-OS AUTOSAR Operating System extend the RTA product portfolio with support for the

key AUTOSAR software modules. Based on their AUTOSAR interfaces, basic software

modules from third-party suppliers can be seamlessly integrated with RTA-RTE and RTA-

OSEK.

剩余201页未读，继续阅读

HYongshun

粉丝: 3
资源: 38

ETAS ASCET V6.4 AUTOSAR 使用指南

autosar中文指导手册

Autosar BSW模块的培训资料

Autosar中文详细简介

ETAS autosar培训

etas autosar手册

etas autosar安装

ETAS autosar静态arp表配置

etas es582.1驱动下载

etas cp autosar rta-car工具使用教程

有什么软件可以用于AUTOSAR开发

ETAS ES582.1

autosar ETAS工具

Python通过ETAS64.dll使用J2534

etas-os(rta-os)用户手册

AUTOSAR vector ETAS

怎么学习autosar

autosar免费工具在哪里下载

etas rtaos手册

etas 581.4使用方法

autosar AP的工具

最新资源