Post Page Advertisement [Top]

continuing with the list of APIs from the previous article,

11.Rte_DReadPerforms an “explicit” read on a sender-receiver communication data

Syntax: <return> Rte_DRead_<p>_<o>(Rte_Instance <instance>)

12.Rte_ReceivePerforms an “explicit” read on a sender-receiver communication data

Syntax: Std_ReturnType Rte_Receive_<p>_<o>(Rte_Instance <instance>,<data>)

Where <p> is the port name and <o> the data element within the sender-receiver interface categorizing the port and <data> is the read data

Components communicate events to other components using the Rte_Send call. The
call is defined per port and interface data item for each component type. Similarly, component prototypes receive events that are communicated from other
components using the Rte_Receive call

The behavior of the Rte_Receive API depends on how you configured the
RECEIVE_MODE interface attributes:

  • Data Read Access: Rte_Receive is non-blocking even if no data is present to read. If no data is present, the return value from the call is RTE_E_NO_DATA.
  • Activation of runnable entity: The RTE activates the specified runnable entity and generates a non-blocking Rte_Receive.
  • Wake up of wait point: Rte_Receive blocks if no data is available. If no data is received within the specified timeout value, the return value from the call is RTE_E_TIMEOUT.


13.Rte_CallInitiate a client-server communication. The Rte_Result API is used by a client to collect the result of an asynchronous client-server communication. The Rte_Result API includes zero or more IN/OUT and OUT parameters to pass back results.

Syntax: 
Std_ReturnType Rte_Call_<p>_<o>(Rte_Instance <instance>, <data_1>... <data_n>)

Where <p> is the port name and <o> the operation within the client-server interface categorizing the port.The signature can include zero or more IN/OUT and OUT parameters depending on the signature of the operation in the client-server interface.

Client-server communication is initiated using the Rte_Call API call. There are two
forms that the call can take depending on the configuration of the CLIENT_MODE attribute.

If CLIENT_MODE is set to synchronous then Rte_Call returns after the operation has
been completed by the server. This means that your code will not continue to execute
until the server returns the result. Once the result has been computed it is passed back

to the component by the return value of the Rte_Call

If CLIENT_MODE is asynchronous, the result of the server operation is accessed using the asynchronous client result runnable entity that you define or the Rte_Result_<port>_<operation> API call.

14.Rte_ResultGet the result of an asynchronous client-server call.

Syntax: 
Std_ReturnType Rte_Result_<p>_<o>(Rte_Instance <instance>, <param 1>...<param n>)

Where <p> is the port name and <o> the operation within the client-server interface categorizing the port.


15.Rte_PimProvide access to the defined per-instance memory (section) of a
software component.

Syntax: <type>/<return reference> Rte_Pim_<name>(Rte_Instance <instance>)
Where <name> is the (short) name of the per-instance name.

The Rte_Pim API is used to access the component state. The function returns a handle to a per-instance memory section. The type of the return value depends on the per-instance memory declaration

16.Rte_CDataProvide access to the calibration parameter an AUTOSAR software component defined internally. Access is read-only. It can be configured for each calibration parameter individually if it is shared by all instances of an AUTOSAR software-component or if each instance has an own data value associated with it.

Syntax: <return> Rte_CData_<name>(Rte_Instance <instance>)
Where <name> is the calibration parameter name.

17.Rte_PrmProvide access to the parameters defined by an AUTOSAR ParameterSwComponentType. Access is read-only

Syntax: <return> Rte_Prm_<p>_<o>(Rte_Instance <instance>)
Where <p> is the port name and <o> is the name of the ParameterDataPrototype within the ParameterInterface categorizing the port.

18.Rte_IReadProvide read access to the VariableDataPrototype referenced
by VariableAccess in the dataReadAccess role.

Syntax: <return> Rte_IRead_<re>_<p>_<o>(Rte_Instance)
Where <re> is the runnable entity name, <p> the port name and <o> the VariableDataPrototype name

The implicit API uses a locally cached copy of data to preserve consistency over a
calling runnable entity invocation. Data is read into a global cache before the runnable
entity starts executing and is written from the global cache after the runnable entity
terminates. Data writes are done once, no matter how many times it is written.
The RTE guarantees cached data does not change during the execution of the runnable
entity. The implicit API includes a reference to the runnable entity that is declared as accessing the data in the API name.

19.Rte_IWriteProvide write access to the VariableDataPrototypes referenced
by VariableAccesses in the dataWriteAccess role

Syntax: void Rte_IWrite_<re>_<p>_<o>(RTE_Instance,<data>)
Where <re> is the runnable entity name, <p> the port name and <o> the VariableDataPrototype name

20.Rte_IWriteRefProvide a reference to the VariableDataPrototype referenced by a VariableAccess in the dataWriteAccess role.

Syntax: <return reference> Rte_IWriteRef_<re>_<p>_<o>(RTE_Instance)

Where <re> is the runnable entity name, <p> the port name and <o> the VariableDataPrototype name.

No comments:

Post a Comment

Bottom Ad [Post Page]