AUTOSAR学习之RTE - 可运行实体
本文介绍RTE的运行体(runnable)。
An AUTOSAR component defines one or more "runnable entities". A runnable entity is a piece of code with a single entry point and an associate set of data. A softwarecomponent description provides definitions for each runnable entity within the softwarecomponent.
For components implemented using C or C++ the entry point of a runnable entity is implemented by a function with global scope defined within a software-component's source code. The following sections consider the function signature and prototype.
组件内部可以定义一组运行体。每个运行体内部有一个入口和与之关联的数据。
例如:

构件运行体为:
/* Model step function */
void Runnable_Component1 ( void )
{
/* local block i/o variables */
real_T rtb_BufferInput_InsertedFor_Dat;
{
uint8_T rtb_BufferInput_InsertedFor_Eve;
/* SignalConversion: '<Root>/BufferInput_InsertedFor_DataIN_at_outport_0' incorporates:
* Inport: '<Root>/DataIN'
*/
rtb_BufferInput_InsertedFor_Dat = Rte_IRead_Runnable_Component1_DataINPort_Data();
/* SignalConversion: '<Root>/BufferInput_InsertedFor_Event_at_outport_0' incorporates:
* Inport: '<Root>/Event'
*/
Rte_Read_EventPort_Event ( &rtb_BufferInput_InsertedFor_Eve );
/* Outputs for enable SubSystem: '<Root>/Runable1' incorporates:
* EnablePort: '<S1>/Enable'
*/
if ( rtb_BufferInput_InsertedFor_Eve > )
{
/* S-Function (sfun_autosar_clientop): '<S1>/BSW_ADD' incorporates:
* Constant: '<Root>/1'
*/
Rte_Call_AddPort_Add ( rtb_BufferInput_InsertedFor_Dat, Component1_P._Value, &Component1_B.BSW_ADD );
}
/* end of Outputs for SubSystem: '<Root>/Runable1' */
/* SignalConversion: '<Root>/BufferOutput_InsertedFor_DataOUT_at_inport_0' */
Rte_Write_DataOutPort_Data ( Component1_B.BSW_ADD );
}
}
使用一个xml描述这个运行体(可以看作是定义阶段所扫描生成的),结构如下:
<RUNNABLE-ENTITY>
<SHORT-NAME>Runnable_Component1</SHORT-NAME>
<CAN-BE-INVOKED-CONCURRENTLY>false</CAN-BE-INVOKED-CONCURRENTLY>
<DATA-READ-ACCESSS>
<DATA-READ-ACCESS>
<SHORT-NAME>IN_DataINPort_Data</SHORT-NAME>
<DATA-ELEMENT-IREF>
<R-PORT-PROTOTYPE-REF DEST="R-PORT-PROTOTYPE">/SWC/Component1/DataINPort</R-PORT-PROTOTYPE-REF>
<DATA-ELEMENT-PROTOTYPE-REF DEST="DATA-ELEMENT-PROTOTYPE">/Component1/if/MathDataInterface/Data</DATA-ELEMENT-PROTOTYPE-REF>
</DATA-ELEMENT-IREF>
</DATA-READ-ACCESS>
</DATA-READ-ACCESSS>
<DATA-RECEIVE-POINTS>
<DATA-RECEIVE-POINT>
<SHORT-NAME>IN_EventPort_Event</SHORT-NAME>
<DATA-ELEMENT-IREF>
<R-PORT-PROTOTYPE-REF DEST="R-PORT-PROTOTYPE">/SWC/Component1/EventPort</R-PORT-PROTOTYPE-REF>
<DATA-ELEMENT-PROTOTYPE-REF DEST="DATA-ELEMENT-PROTOTYPE">/Component1/if/EventInterface/Event</DATA-ELEMENT-PROTOTYPE-REF>
</DATA-ELEMENT-IREF>
</DATA-RECEIVE-POINT>
</DATA-RECEIVE-POINTS>
<DATA-SEND-POINTS>
<DATA-SEND-POINT>
<SHORT-NAME>OUT_DataOutPort_Data</SHORT-NAME>
<DATA-ELEMENT-IREF>
<P-PORT-PROTOTYPE-REF DEST="P-PORT-PROTOTYPE">/SWC/Component1/DataOutPort</P-PORT-PROTOTYPE-REF>
<DATA-ELEMENT-PROTOTYPE-REF DEST="DATA-ELEMENT-PROTOTYPE">/Component1/if/MathDataInterface/Data</DATA-ELEMENT-PROTOTYPE-REF>
</DATA-ELEMENT-IREF>
</DATA-SEND-POINT>
</DATA-SEND-POINTS>
<SERVER-CALL-POINTS>
<SYNCHRONOUS-SERVER-CALL-POINT>
<SHORT-NAME>SC_AddPort_Add</SHORT-NAME>
<OPERATION-IREFS>
<OPERATION-IREF>
<R-PORT-PROTOTYPE-REF DEST="R-PORT-PROTOTYPE">/SWC/Component1/AddPort</R-PORT-PROTOTYPE-REF>
<OPERATION-PROTOTYPE-REF DEST="OPERATION-PROTOTYPE">/BSW/if/BSW_ADD/Add</OPERATION-PROTOTYPE-REF>
</OPERATION-IREF>
</OPERATION-IREFS>
<TIMEOUT>0.000001</TIMEOUT>
</SYNCHRONOUS-SERVER-CALL-POINT>
</SERVER-CALL-POINTS>
<SYMBOL>Runnable_Component1</SYMBOL>
</RUNNABLE-ENTITY>
上面的<SYMBOL>Runnable_Component1</SYMBOL> 提示链接器连接这个符号。
1. 签名(Signature)
The definition of all runnable entities, whatever the RTEEvent that triggers their execution, follows the same basic form. [rte sws 1126]
<void|Std_ReturnType> <name>([IN Rte_Instance <instance>], [role parameters])
Where <name> 3 is the symbol describing the runnable's entry point rte sws in 0053. The definition of the role parameters is defined in Section 5.7.3.
所有运行体,不管是怎样触发,函数定义都是下面这个格式:
<void|Std_ReturnType> <name>([IN Rte_Instance <instance>], [role parameters])
如前面的例子:
void Runnable_Component1(void)
参数的意义为:
IN Rte_Instance <instance> - 本实体的指针,因为一个构件可以多重实例化,所以有时候必须要判断一下自己是哪个实体。
role parameters - 指明是谁触发的这个运行体,有时候一个运行体可以被多个事件触发,需要确定一下自己是哪个事件出发的。
Section 5.2.6.4 contains details on a recommended naming conventions for runnable entities based on the RTEEvent that triggers the runnable entity. The recommended naming convention makes explicit the functions that implement runnable entities as well as clearly associating the runnable entity and the applicable data element or operation.
2. 入口点原型(Entry Point Prototype)

The RTE determines the required role parameters, and hence the prototype of the entry point, for a runnable entity based on information in the input information (see Appendix B). The entry point defined in the component source must be compatible with the parameters passed by the RTE when the runnable entity is triggered by the RTE and therefore the RTE generator is required to emit a prototype for the function. [rte sws 1132] The RTE generator shall emit a prototype for the runnable entity's entry point in the application header file.
RTE通过角色参数判断入口点类型,所以运行体入口必须要定义得复合参数类型,以便于RTE生成函数的触发。
The prototype for a function implementing the entry point of a runnable entity is emitted for both "RTE Contract" and "RTE Generation" phases. The function name for the prototype is the runnable entity's entry point. The prototype of the entry point function includes the runnable entity's instance handle and its role parameters, see Figure 5.2.

[rte sws 1016] The function implementing the entry point of a runnable entity shall define an instance handle as the first formal parameter.
第一个参数必须是组件实例。
The RTE will ensure that when the runnable entity is triggered the instance handle parameter indicates the correct component instance. The remaining parameters passed to the runnable entity depend on the RTEEvent that triggers execution of the runnable entity.
[rte sws 1130] A function implementing a runnable entity entry point shall only have the return type Std_ReturnType, if the runnable entity represents a server operation and the AUTOSAR interface description of that client server communication lists potential application errors. All other functions implementing a runnable entity entry point shall have a return type of void.
如果运行体是一个server operation,则返回正确与否,否则返回void。
[rte sws ext 2704] Only the least significant six bit of the return value of a server runnable shall be used by the application to indicate an error. The upper two bit shall be zero. See also rte sws 2573.
返回值的最高2位必须是0。
AUTOSAR学习之RTE - 可运行实体的更多相关文章
- AUTOSAR学习之RTE - 基本概念
1.什么是RTE? The Run-Time Environment (RTE) is at the heart of the AUTOSAR ECU architecture. The RTE is ...
- Adaptive AUTOSAR 学习笔记 8 - 干货小结:背景、技术、特征、架构、方法论和 Manifest
官方文档下载方式及介绍情参见 Adaptive AUTOSAR 学习笔记 2 - 官方文档下载及阅读建议. 这是 Adaptive AUTOSAR 学习笔记的第 8 篇,学习笔记 3 - 7 翻译了 ...
- python学习笔记-python程序运行
小白初学python,写下自己的一些想法.大神请忽略. 安装python编辑器,并配置环境(见http://www.cnblogs.com/lynn-li/p/5885001.html中 python ...
- Adaptive AUTOSAR 学习笔记 3 - AP 背景、技术及特征(中文翻译)
本系列学习笔记基于 AUTOSAR Adaptive Platform 官方文档 R20-11 版本.本文从AUTOSAR_EXP_PlatformDesign.pdf开始,一边学习,一边顺带着翻译一 ...
- Adaptive AUTOSAR 学习笔记 1 - Overview
缩写 AP: AUTOSAR Adaptive Platform CP: AUTOSAR Classic Platform AA: Adaptive Application ARA: AUTOSAR ...
- Adaptive AUTOSAR 学习笔记 6 - 架构 - 方法论和 Manifest
本系列学习笔记基于 AUTOSAR Adaptive Platform 官方文档 R20-11 版本 AUTOSAR_EXP_PlatformDesign.pdf 缩写 AP:AUTOSAR Adap ...
- Adaptive AUTOSAR 学习笔记 10 - 执行管理
本系列学习笔记基于 AUTOSAR Adaptive Platform 官方文档 R20-11 版本 AUTOSAR_EXP_PlatformDesign.pdf 缩写 EM:Execution Ma ...
- Adaptive AUTOSAR 学习笔记 16 - 时间同步和网络管理
本系列学习笔记基于 AUTOSAR Adaptive Platform 官方文档 R20-11 版本 AUTOSAR_EXP_PlatformDesign.pdf.作者:Zijian/TENG 原文地 ...
- MFC学习-第一课 MFC运行机制
最近由于兴趣爱好,学习了孙鑫的MFC教程的第一课.看完视频了,自己便用visual studio 2010尝试了MFC编程,其中遇到了一些问题. 1.vs2010不像vs6.0那样可以新建一个空的MF ...
随机推荐
- 浅入深出Vue:组件
组件在 vue开发中是必不可少的一环,用好组件这把屠龙刀,就能解决不少问题. 组件是什么 官方的定义: 组件是可复用的 Vue 实例,并且可带有一个名字. 官方的定义已经非常简明了,组件就是一个实例. ...
- 使用SSH+SFTP操作终端全解析,告别XShell
1.前言 在Windows系统下操作远程服务器的方式很多,比如XShell+XFTP组合,亦或是PuTTY+WinSCP组合,但在Mac系统下登陆远程服务器,并没有这些工具供我们使用.相比较而言,在M ...
- HDU 6019:MG loves gold(暴力set)
http://acm.hdu.edu.cn/showproblem.php?pid=6019 题意:给出n个颜色的物品,你每次取只能取连续的不同颜色的物品,问最少要取多少次. 思路:从头往后扫,用se ...
- HDU 4283:You Are the One(区间DP)
http://acm.hdu.edu.cn/showproblem.php?pid=4283 题意:有n个数字,不操作的情况下从左到右按顺序输出,但是可以先让前面的数字进栈,让后面的数字输出,然后栈里 ...
- UVa 10480:Sabotage (最小割集)
https://uva.onlinejudge.org/index.php?option=com_onlinejudge&Itemid=8&page=show_problem& ...
- Vue技术点整理-Vue Router
路由 Vue Router 对于单页面应用来说,如果涉及到多个页面的话,就必须要使用到路由,一般使用官方支持的 vue-router 库 一,Vue Router 在项目中的安装引用 1,在页面中使用 ...
- 《An Attentive Survey of Attention Models》阅读笔记
本文是对文献 <An Attentive Survey of Attention Models> 的总结,详细内容请参照原文. 引言 注意力模型现在已经成为神经网络中的一个重要概念,并已经 ...
- py+selenium 老是定位不到文本内容【已解决】
问题:定位不到文本内容,路径也正确,该加frame也有加,等待时间也够长 测试: 上图看不出差异,但是测试1就定位得到,测试2就定位不到,为什么? 看下图就知道了 区别就在于,测试2后面多了个空格!! ...
- s := time.Now().Format("20060102") go格式化
s := time.Now().Format("20060102") t := time.Unix(1362984425, 0) nt := t.Format("2006 ...
- RabbitMQ 从入门到精通(二)
目录 1. 消息如何保障百分之百的投递成功? 1.1 方案一:消息落库,对消息状态进行打标 1.2 方案二:消息的延迟投递,做二次确认,回调检查 2. 幂等性 2.1 幂等性是什么? 2.2 消息端幂 ...