Specification of CAN Interface V3.2.0 R3.0 Rev 7 Document Title Specification of CAN Interface Document Owner AUTOSAR Document Responsibility AUTOSAR Document Identification No 012 Document Classification Standard Document Version 3.2.0 Document Status Final Part of Release 3.0 Revision 7 Document Change History Date Version Changed by Change Description 15.09.2010 3.2.0 AUTOSAR Removed appearance of Administration CANIF733_Conf in the document. Links to CANIF733_Conf replaced by links to CANIF246 which is the global configuration container of CANIF_PUBLIC_TXCONFIRM_POLLIN G_SUPPORT Changed second parameter of <User_RxIndication> from SduDataPtr to PduInfoPtr within the whole document. Deleted SWS Items CANIF029, CANIF129 and CANIF130 [BSW01017] has been removed. Entered function CanIf_GetTxConfirmationState Entered description and SWSItemIds CANIF739 and CANIF740 Legal disclaimer revised 28.01.2010 3.1.0 AUTOSAR Added: CANIF300, CANIF301, Administration CANIF_HRHRANGE_CANIDTYPE Changed description of function parameter of <User_RxIndication> (CanNm) Changed CANIF038, 3rd and 4th paragraph of chapter 7.19.1, Figure 13, Figure 15. Deleted: CANIF_WAKEUP_EVENT_API, CANIF270, bullet point 4 of 2nd paragraph of chapter 7.24, bullet point 4 of CANIF126 Legal disclaimer revised 1 of 177 Document ID 012: AUTOSAR_SWS_CAN_Interface - AUTOSAR confidential - Specification of CAN Interface V3.2.0 R3.0 Rev 7 Document Change History Date Version Changed by Change Description 29.01.2008 3.0.1 AUTOSAR Replaced chapter 10 content with Administration generated tables from AUTOSAR MetaModel. 12.12.2007 3.0.0 AUTOSAR Interface abstraction: network related Administration interface changed into a controller related one Wakeup mechanism completely reworked, APIs added & changed for Wakeup Initialization changed (flat initialization) Scheduled main functions skipped due to changed BSW Scheduler responsibility Document meta information extended Small layout adaptations made 31.10.2007 2.1.0 AUTOSAR Header file structure changed Administration Support of mixed mode operation (StandardCAN & Extended CAN in parallel on one network) added Support of CAN Transceiver according AUTOSAR_WP1.1.2_SoftwareArchitect ure.ppt API <User>_DlcErrorNotification deleted Pre-compile/Link-Time/Post-Built definiton for configuration parameters partly changed Re-entrant interface call allowed for certain APIs Support of AUTOSAR BSW Scheduler added Support of memory mapping added Configuration container structure reworked Various of clarification extensions and corrections 26.06.2006 2.0.0 AUTOSAR Second Release Administration 31.06.2005 1.0.0 AUTOSAR Initial Release Administration 2 of 177 Document ID 012: AUTOSAR_SWS_CAN_Interface - AUTOSAR confidential - Specification of CAN Interface V3.2.0 R3.0 Rev 7 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 Specification Documents 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 Specification Documents for illustration purposes only, and they themselves are not part of the AUTOSAR Standard. Neither their presence in such Specification Documents, 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. 3 of 177 Document ID 012: AUTOSAR_SWS_CAN_Interface - AUTOSAR confidential - Specification of CAN Interface V3.2.0 R3.0 Rev 7 Table of Contents 1 Introduction and functional overview ................................................................. 10 2 Acronyms and Abbreviations............................................................................. 12 3 Related documentation...................................................................................... 14 3.1 Input documents......................................................................................... 14 3.2 Related standards and norms .................................................................... 15 4 Constraints and assumptions ............................................................................ 16 4.1 Limitations .................................................................................................. 16 4.2 Applicability to car domains........................................................................ 16 5 Dependencies to other modules........................................................................ 17 5.1 Upper Protocol Layers................................................................................ 18 5.2 Initialization: Ecu State Manager................................................................ 18 5.3 Mode Control: CAN State Manager............................................................ 18 5.4 Lower layers: CAN Driver........................................................................... 18 5.5 Lower layers: CAN Transceiver Driver ....................................................... 19 5.6 Configuration.............................................................................................. 20 5.7 File structure .............................................................................................. 21 5.7.1 Code file structure ............................................................................... 21 5.7.2 Header file structure............................................................................ 21 6 Requirements traceability .................................................................................. 24 7 Functional specification ..................................................................................... 30 7.1 General functionality................................................................................... 30 7.2 Hardware object handles............................................................................ 31 7.3 Static CAN L-PDU handles ........................................................................ 32 7.4 Dynamic CAN transmit L-PDU handles...................................................... 33 7.5 Physical channel view ................................................................................ 33 7.6 CAN hardware unit..................................................................................... 35 7.7 BasicCAN and FullCAN reception.............................................................. 36 7.8 Initialization ................................................................................................ 37 7.9 Transmit data flow...................................................................................... 39 7.10 Transmit request ........................................................................................ 40 7.11 Transmit confirmation................................................................................. 41 7.11.1 Confirmation after transmission........................................................... 41 7.11.2 Confirmation of transmit cancellation .................................................. 41 7.12 Transmit buffering ...................................................................................... 42 7.12.1 General behavior................................................................................. 42 7.12.2 Buffer characteristics........................................................................... 44 7.12.2.1 Storage of L-PDUs in the transmit buffer ..................................... 44 7.12.2.2 Storage of L-PDUs is prohibited................................................... 44 7.12.2.3 Get L-PDU with the highest priority.............................................. 44 7.12.2.4 Remove transmitted L-PDU ......................................................... 44 7.12.2.5 Initialization of transmit buffers..................................................... 44 7.12.3 Data integrity of transmit buffers ......................................................... 44 7.13 Transmit cancellation ................................................................................. 45 4 of 177 Document ID 012: AUTOSAR_SWS_CAN_Interface - AUTOSAR confidential - Specification of CAN Interface V3.2.0 R3.0 Rev 7 7.13.1 Hardware transmit cancellation not supported or not used ................. 45 7.13.2 Hardware transmit cancellation supported and used .......................... 45 7.14 Receive data flow......................................................................................
Details
-
File Typepdf
-
Upload Time-
-
Content LanguagesEnglish
-
Upload UserAnonymous/Not logged-in
-
File Pages177 Page
-
File Size-