SNIP_CLASSIC_LAYEREDSOFTWAREARCHITECTURE_SECTION_4_CAN_Flexray

4 CAN / Flexray / Ethernet / Serial R22-11 AUTOSAR_EXP_LayeredSoftwareArchitecture 169 of 193 Integration and Runtime Aspects - Error Handling, Reporting and Diagnostic Diagnostic Log and Trace (3) API The Diagnostic Log and Trace has syntactically the following API: Dlt_SendLogMessage(Dlt_SessionIDType session_id, Dlt_MessageLogInfoType log_info, uint8 *log_data, uint16 log_data_length) Log message identification : session_id Session ID is the identification number of a log or trace session. A session is the logical entity of the source of log or trace messages. If a SW-C is instantiated several times or opens several ports to Dlt, a new session with a new Session ID for every instance is used. A SW-C additionally can have several log or trace sessions if it has several ports opened to Dlt. log_info contains: Application ID / Context ID Application ID is a short name of the SW-C. It identifies the SW-C in the log and trace message. Context ID is a user defined ID to group log and trace messages produced by a SW-C to distinguish functionality. Each Application ID can own several Context IDs. Context ID’s are grouped by Application ID’s. Both are composed by four 8 bit ASCII characters. Message ID Messaged ID is the ID to characterize the information, which is transported by the message itself. It can be used for identifying the source (in source code) of a message and shall be used for characterizing the payload of a message. A message ID is statically fixed at development or configuration time. log_data Contain the log or trace data it self. The content and the structure of this provided buffer is specified by the Dlt transmission protocol. Description File Normally the log_data contains only contents of not fixed variables or information (e.g. no static strings are transmitted). Additionally a description file shall be provided. Within this file the same information for a log messages associated with the Message ID are posted. These are information how to interpret the log_data buffer and what fixed entries belonging to a log message. page id: k387z R22-11 AUTOSAR_EXP_LayeredSoftwareArchitecture 170 of 193 Table of contents 1. Architecture 2. Configuration 3. Integration and Runtime Aspects 1. Mapping of Runnables 2. Partitioning 3. Scheduling 4. Mode Management 5. Error Handling, Reporting and Diagnostic 6. Measurement and Calibration 7. Functional Safety 8. Security 9. Energy Management 10. Global Time Synchronization page id: toc03 R22-11 AUTOSAR_EXP_LayeredSoftwareArchitecture 171 of 193 Integration and Runtime Aspects - Measurement and Calibration XCP XCP is an ASAM standard for calibration purpose of an ECU. page id: y0099 AUTOSAR COM Communication HW Abstraction Bus Interface(s) (or Socket Adaptor on ethernet) PDU Router RTE N-PDU Signals Communication Drivers Bus Driver(s) AUTOSAR Tp I-PDU Diagnostic Communication Manager I-PDU1 I-PDU I-PDU L-PDU IPDU Multiplexer I-PDU NM Module Diagnostic Log and Trace I-PDU XCP Protocol XCPonFr / XCPonCAN/ XCPonTCP/IP / Interfaces XCP within AUTOSAR provides the following basic features: ➢Synchronous data acquisition ➢Synchronous data stimulation ➢Online memory calibration (read / write access) ➢Calibration data page initialization and switching ➢Flash Programming for ECU development purposes N-PDU R22-11 AUTOSAR_EXP_LayeredSoftwareArchitecture 172 of 193