Document Title Requirements on Debugging in AUTOSAR
Total Page:16
File Type:pdf, Size:1020Kb
Requirements on Debugging in AUTOSAR AUTOSAR Release 4.2.2 Document Title Requirements on Debugging in AUTOSAR Document Owner AUTOSAR Document Responsibility AUTOSAR Document Identification No 332 Document Classification Auxiliary Document Status Final Part of AUTOSAR Release 4.2.2 Document Change History Release Changed by Change Description 4.2.2 AUTOSAR Marked the document as obsolete Release Management 4.2.1 AUTOSAR Editorial changes Release Management 4.1.2 AUTOSAR Updated reference to RS feature document Release Editorial changes Management 4.1.1 AUTOSAR Updated the format of requirements according Administration to TPS_StandardizationTemplate Updated the chapters 2 and 5 Replaced Complex Device Driver by Complex Driver 3.1.5 AUTOSAR Initial release Administration 1 of 19 Document ID 332: AUTOSAR_SRS_Debugging - AUTOSAR confidential - Requirements on Debugging in AUTOSAR AUTOSAR Release 4.2.2 Disclaimer This specification and the material contained in it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the companies that have contributed to it shall not be liable for any use of the specification. The material contained in this specification is protected by copyright and other types of Intellectual Property Rights. The commercial exploitation of the material contained in this specification requires a license to such Intellectual Property Rights. This specification may be utilized or reproduced without any modification, in any form or by any means, for informational purposes only. For any other purpose, no part of the specification may be utilized or reproduced, in any form or by any means, without permission in writing from the publisher. The AUTOSAR specifications have been developed for automotive applications only. They have neither been developed, nor tested for non-automotive applications. The word AUTOSAR and the AUTOSAR logo are registered trademarks. Advice for users AUTOSAR specifications may contain exemplary items (exemplary reference models, "use cases", and/or references to exemplary technical solutions, devices, processes or software). Any such exemplary items are contained in the specifications for illustration purposes only, and they themselves are not part of the AUTOSAR Standard. Neither their presence in such specifications, nor any later documentation of AUTOSAR conformance of products actually implementing such exemplary items, imply that intellectual property rights covering such exemplary items are licensed under the same rules as applicable to the AUTOSAR Standard. 2 of 19 Document ID 332: AUTOSAR_SRS_Debugging - AUTOSAR confidential - Requirements on Debugging in AUTOSAR AUTOSAR Release 4.2.2 Table of Contents Table of Contents ..................................................................................................... 3 1 Scope of Document ............................................................................................. 5 2 Conventions to be used ....................................................................................... 6 3 Functional Overview ............................................................................................ 7 4 Requirements Specification ................................................................................. 8 4.1 Functional Requirements ............................................................................... 8 4.1.1 Configuration ........................................................................................... 8 4.1.1.1 [SRS_Dbg_00001] Description of semantics of data ........................ 8 4.1.1.2 [SRS_Dbg_00002] Inclusion of BSW header files ............................ 8 4.1.1.3 [SRS_Dbg_00003] Static configuration of data items to be debugged 8 4.1.1.4 [SRS_Dbg_00039] Symbolic and physical configuration of data items to be debugged ...................................................................................... 9 4.1.1.5 [SRS_Dbg_00004] Static configuration of behavior of the debugging module 9 4.1.1.6 [SRS_Dbg_00005] Behavior on internal buffer overflow .................. 9 4.1.1.7 [SRS_Dbg_00038] Support for post build configuration ................... 9 4.1.2 Initialization ........................................................................................... 10 4.1.2.1 [SRS_Dbg_00006] Debugging during system startup .................... 10 4.1.3 Normal Operation .................................................................................. 10 4.1.3.1 [SRS_Dbg_00007] Collect data on a running ECU ........................ 10 4.1.3.2 [SRS_Dbg_00008] Collect and store data for tracing purpose ....... 10 4.1.3.3 [SRS_Dbg_00009] Transmit stored data to host ............................ 10 4.1.3.4 [SRS_Dbg_00010] Collect and immediately transmit data to host . 11 4.1.3.5 [SRS_Dbg_00011] Enabling/disabling of data buffering ................. 11 4.1.3.6 [SRS_Dbg_00012] Collect data with automatic timestamp ........... 11 4.1.3.7 [SRS_Dbg_00013] Enabling/disabling of time stamping ................ 11 4.1.3.8 [SRS_Dbg_00015] Accept commands to change the behavior of the debugging module ......................................................................................... 12 4.1.3.9 [SRS_Dbg_00016] Selectable behavior on start of communication 12 4.1.3.10 [SRS_Dbg_00017] Offer a public API for BSW modules ............... 12 4.1.3.11 [SRS_Dbg_00018] Communication between debugging module and host 12 4.1.3.12 [SRS_Dbg_00019] Communication to one host only at a time ...... 13 4.1.3.13 [SRS_Dbg_00020] Support of post mortem analysis ..................... 13 4.1.3.14 [SRS_Dbg_00021] Debugging support for development phase only 13 4.1.3.15 [SRS_Dbg_00022] Tracing of global variables .............................. 13 4.1.3.16 [SRS_Dbg_00023] Enabling/disabling tracing of variables ............ 14 4.1.3.17 [SRS_Dbg_00024] Periodic tracing of variables ............................ 14 4.1.3.18 [SRS_Dbg_00025] Modify tracing period ....................................... 14 4.1.3.19 [SRS_Dbg_00026] Event based tracing of variables ..................... 14 4.1.3.20 [SRS_Dbg_00027] Tracing of functions ......................................... 14 4.1.3.21 [SRS_Dbg_00028] Tracing of software components behavior ...... 15 4.1.3.22 [SRS_Dbg_00029] Tracing of development errors ........................ 15 4.1.3.23 [SRS_Dbg_00030] Support for transparent memory access ......... 15 4.1.3.24 [SRS_Dbg_00031] Transmission of data items exceeding frame length 15 4.1.4 Shutdown Operation ............................................................................. 16 3 of 19 Document ID 332: AUTOSAR_SRS_Debugging - AUTOSAR confidential - Requirements on Debugging in AUTOSAR AUTOSAR Release 4.2.2 4.1.5 Fault Operation ..................................................................................... 16 4.1.5.1 [SRS_Dbg_00032] Handling of communication failure ................... 16 4.2 Non-Functional Requirements ..................................................................... 16 4.2.1 Timing Requirements ............................................................................ 16 4.2.1.1 [SRS_Dbg_00033] Minimize runtime of the debugging module ..... 16 4.2.2 Resource Usage ................................................................................... 17 4.2.2.1 [SRS_Dbg_00034] Minimize resource consumption of the debugging module 17 4.2.3 Integration in AUTOSAR architecture ................................................... 17 4.2.3.1 [SRS_Dbg_00035] Minimize dependency on other AUTOSAR BSW modules 17 4.2.3.2 [SRS_Dbg_00036] Integration in AUTOSAR communication stack 17 4.2.3.3 [SRS_Dbg_00037] Separation between Main Debugging Module and communication part ................................................................................. 17 4.3 Not Applicable Requirements ...................................................................... 18 4.3.1 [SRS_Dbg_99999] This requirement references all requirements which are not applicable for this SWS ......................................................................... 18 5 References ........................................................................................................ 19 4 of 19 Document ID 332: AUTOSAR_SRS_Debugging - AUTOSAR confidential - Requirements on Debugging in AUTOSAR AUTOSAR Release 4.2.2 1 Scope of Document This document describes the requirements for a debugging module in AUTOSAR, including the API configuration communication interactions to, and requirements on surrounding BSW modules This specification is obsolete and will be removed from the standard in an upcoming release. 5 of 19 Document ID 332: AUTOSAR_SRS_Debugging - AUTOSAR confidential - Requirements on Debugging in AUTOSAR AUTOSAR Release 4.2.2 2 Conventions to be used The representation of requirements in AUTOSAR documents follows the table specified in [8]. In requirements, the following specific semantics shall be used (based on the Internet Engineering Task Force IETF). The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as: SHALL: This word means that the definition is an absolute requirement of the specification. SHALL NOT: This phrase means that the definition is an absolute prohibition of the specification. MUST: This word means that the definition is an absolute requirement of the specification due to legal issues. MUST NOT: This phrase means that the definition is an absolute