Specification of Debugging in AUTOSAR

Specification of Debugging in AUTOSAR

Specification of Debugging in AUTOSAR V1.2.0 R4.0 Rev 3 Document Title Specification of Debugging in AUTOSAR Document Owner AUTOSAR Document Responsibility AUTOSAR Document Identification No 315 Document Classification Standard Document Version 1.2.0 Document Status Final Part of Release 4.0 Revision 3 Document Change History Date Version Changed by Change Description 09.12.2011 1.2.0 AUTOSAR Clarify interface toward "to be Administration debugged" modules Configuration for debugging variables (DbgStaticDID) is corrected and extended 18.10.2010 1.1.0 AUTOSAR NULL pointer check for development Administration mode defined. 30.11.2009 1.0.0 AUTOSAR Initial Release Administration 1 of 106 Document ID 315: AUTOSAR_SWS_Debugging - AUTOSAR confidential - Specification of Debugging in AUTOSAR V1.2.0 R4.0 Rev 3 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 106 Document ID 315: AUTOSAR_SWS_Debugging - AUTOSAR confidential - Specification of Debugging in AUTOSAR V1.2.0 R4.0 Rev 3 Table of Contents 1 Introduction and functional overview ................................................................... 7 1.1 Architectural overview .................................................................................. 7 1.1.1 Architectural view within the BSW......................................................... 7 1.1.2 External architectural view .................................................................... 7 1.2 Functional overview...................................................................................... 8 2 Acronyms and abbreviations ............................................................................... 9 3 Related documentation...................................................................................... 11 3.1 Input documents......................................................................................... 11 3.2 Related standards and norms .................................................................... 11 4 Constraints and assumptions ............................................................................ 12 4.1 Limitations .................................................................................................. 12 4.1.1 Single Host Access ............................................................................. 12 4.1.2 Static configuration.............................................................................. 12 4.1.3 Security ............................................................................................... 12 4.1.4 Support for Object Code Modules....................................................... 12 4.1.5 Impact on the basic software............................................................... 12 4.1.6 Multi core support................................................................................ 13 4.2 Assumptions............................................................................................... 13 4.2.1 Assumptions on the host..................................................................... 13 4.2.2 Assumptions on the communication.................................................... 13 4.3 Applicability to car domains........................................................................ 13 5 Dependencies to other modules........................................................................ 14 5.1 File structure .............................................................................................. 14 5.1.1 Code file structure ............................................................................... 14 5.1.2 Header file structure............................................................................ 14 5.2 Requirements on the host .......................................................................... 17 5.3 Assumptions on other BSW Modules......................................................... 17 5.4 Information of the BSW modules for the debugger..................................... 18 6 Requirements traceability .................................................................................. 20 7 Functional specification ..................................................................................... 26 7.1 General Strategy to identify data................................................................ 26 7.1.1 Standard DIDs..................................................................................... 26 7.1.2 Predefined DIDs.................................................................................. 27 7.2 Buffering strategy ....................................................................................... 27 7.2.1 Static DID management ...................................................................... 28 7.2.2 Dynamic DID management ................................................................. 29 7.2.3 Data record ......................................................................................... 30 7.2.4 Data storage........................................................................................ 32 7.3 Direct transmission..................................................................................... 33 7.4 Information required for DIDs ..................................................................... 34 7.5 Cyclic Tracing and Tracing on Event.......................................................... 34 7.5.1 Cyclic tracing....................................................................................... 34 7.5.2 Tracing on event ................................................................................. 35 3 of 106 Document ID 315: AUTOSAR_SWS_Debugging - AUTOSAR confidential - Specification of Debugging in AUTOSAR V1.2.0 R4.0 Rev 3 7.5.3 Tracing on command .......................................................................... 35 7.6 Supported predefined DIDs........................................................................ 35 7.6.1 Tracing of functions............................................................................. 35 7.6.2 Tracing of Task switches..................................................................... 35 7.6.3 Tracing of RTE events ........................................................................ 36 7.6.4 Transparent access to target memory................................................. 36 7.6.5 Assignment of predefined DIDs........................................................... 37 7.7 Timer, buffer, and buffering management .................................................. 38 7.7.1 DID collection on/off ............................................................................ 38 7.7.2 Individual DID activation on/off............................................................ 38 7.7.3 Global timestamp on/off ...................................................................... 38 7.7.4 DID timestamp on/off .......................................................................... 39 7.7.5 DID buffering on/off ............................................................................. 39 7.7.6 Clear buffer ......................................................................................... 39 7.7.7 Send next n buffer entries ................................................................... 40 7.7.8 Start to send continuously................................................................... 40 7.7.9 Stop to send........................................................................................ 40 7.7.10 Set cycle time to new value................................................................. 40 7.8 Communication with the host ..................................................................... 41 7.8.1 Data transfer to the host...................................................................... 41 7.8.2 Data reception from the host............................................................... 41 7.9 Format of data of the predefined DIDs in the ring buffer

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    106 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us