
Specification of I/O Hardware Abstraction
AUTOSAR CP Release 4.4.0
1 of 58 Document ID 047: AUTOSAR_SWS_IOHardwareAbstraction
- AUTOSAR confidential -
Document Change History
Date
Release
Changed by
Change Description
2018-10-31
4.4.0
AUTOSAR
Release
Management
Debugging section removed
2016-11-30
4.3.0
AUTOSAR
Release
Management
minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
2015-07-31
4.2.2
AUTOSAR
Release
Management
Updated IoHwAb_Init function
prototype
2014-10-31
4.2.1
AUTOSAR
Release
Management
Editorial changes
2014-03-31
4.1.3
AUTOSAR
Release
Management
Adapted the requirement format.
2013-10-31
4.1.2
AUTOSAR
Release
Management
Editorial changes
Removed chapter(s) on change
documentation
2013-03-15
4.1.1
AUTOSAR
Administration
Modified GET and SET operations
Extended Production Errors
recommended by the Task Force
“Production Errors”
Define a notification function for
OCU driver
2011-12-22
4.0.3
AUTOSAR
Administration
Update Version Check requirement
Document Title
Specification of I/O Hardware
Abstraction
Document Owner
AUTOSAR
Document Responsibility
AUTOSAR
Document Identification No
047
Document Status
Final
Part of AUTOSAR Standard
Classic Platform
Part of Standard Release
4.4.0

Specification of I/O Hardware Abstraction
AUTOSAR CP Release 4.4.0
2 of 58 Document ID 047: AUTOSAR_SWS_IOHardwareAbstraction
- AUTOSAR confidential -
Document Change History
Date
Release
Changed by
Change Description
2018-10-31
4.4.0
AUTOSAR
Release
Management
Debugging section removed
2010-09-30
3.1.5
AUTOSAR
Administration
Names of callback notification APIs
have been corrected.
Exported files <ModuleName>.h of
underlying modules are used,
instead of <ModuleName>_Types.h
2010-02-02
3.1.4
AUTOSAR
Administration
I/O Hardware Abstraction
configuration has been removed
from the EcucParamDef
Functional Diagnostics' interface has
been added (DCM controls I/O
Signals)
Unnecessary classes, attributes and
types removed
Legal disclaimer revised
2008-08-13
3.1.1
AUTOSAR
Administration
Legal disclaimer revised
2007-12-21
3.0.1
AUTOSAR
Administration
Auto generation of chapters 8 and
10 with the Metamodel
Update of tables and some chapters
of the document to stay compliant
with correlated documents
Document meta information
extended
Small layout adaptations made
2007-01-24
2.1.15
AUTOSAR
Administration
Various images corrected in
PDFversion (printing problems)

Specification of I/O Hardware Abstraction
AUTOSAR CP Release 4.4.0
3 of 58 Document ID 047: AUTOSAR_SWS_IOHardwareAbstraction
- AUTOSAR confidential -
Document Change History
Date
Release
Changed by
Change Description
2018-10-31
4.4.0
AUTOSAR
Release
Management
Debugging section removed
2006-11-28
2.1.14
AUTOSAR
Administration
File structure updated
Traceability matrix corrected
Restriction for the usage of the SWC
template
Chapter about IOHWAB Runnable
concept reworked
Chapter about IOHWAB description
reworked
Adjustments in the configuration
chapter
Legal disclaimer revised
Release Notes added
“Advice for users” revised
“Revision Information” added
2006-05-16
2.0
AUTOSAR
Administration
Initial Release

Specification of I/O Hardware Abstraction
AUTOSAR CP Release 4.4.0
4 of 58 Document ID 047: AUTOSAR_SWS_IOHardwareAbstraction
- AUTOSAR confidential -
Disclaimer
This work (specification and/or software implementation) 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
work.
The material contained in this work is protected by copyright and other types of
intellectual property rights. The commercial exploitation of the material contained in
this work requires a license to such intellectual property rights.
This work 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
work may be utilized or reproduced, in any form or by any means, without permission
in writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.

Specification of I/O Hardware Abstraction
AUTOSAR CP Release 4.4.0
5 of 58 Document ID 047: AUTOSAR_SWS_IOHardwareAbstraction
- AUTOSAR confidential -
Table of Contents
1 Introduction and functional overview .................................................................. 7
2 Acronyms and abbreviations .............................................................................. 8
3 Related documentation .................................................................................... 10
3.1 Input documents ......................................................................................... 10
3.2 Related standards and norms .................................................................... 11
3.3 Related specification .................................................................................. 11
4 Constraints and assumptions ........................................................................... 12
4.1 Limitations .................................................................................................. 12
4.2 Applicability to car domains ........................................................................ 12
5 Dependencies to other modules ....................................................................... 13
5.1 Interface with MCAL drivers ....................................................................... 13
5.1.1 Overview ................................................................................................. 13
5.1.2 Summary of interfaces with MCAL drivers .............................................. 14
5.2 Interface with the communication drivers ................................................... 14
5.3 Interface with System Services .................................................................. 15
5.4 Interface with DCM ..................................................................................... 16
5.5 File structure ............................................................................................... 17
5.5.1 Code file structure ................................................................................... 17
5.5.2 Header file structure ................................................................................ 17
6 Requirements traceability ................................................................................. 18
7 Functional specification .................................................................................... 22
7.1 Integration code .......................................................................................... 22
7.1.1 Background & Rationale ......................................................................... 22
7.1.2 Requirements for integration code implementation ................................. 22
7.2 ECU Signals Concept ................................................................................. 23
7.2.1 Background & Rationale ......................................................................... 23
7.2.2 Requirements about ECU signals ........................................................... 24
7.3 Attributes .................................................................................................... 25
7.3.1 Background & Rationale ......................................................................... 25
7.3.2 Requirements about ECU signal attributes ............................................. 25
7.4 I/O Hardware Abstraction and Software Component Template .................. 25
7.4.1 Background & Rationale ......................................................................... 26
7.4.2 Requirements about the usage of Software Component template .......... 26
7.5 Scheduling concept for I/O Hardware Abstraction ...................................... 27
7.5.1 Background & Rationale ......................................................................... 27
7.5.2 Requirements about I/O Hardware Abstraction Scheduling concept ...... 28
7.6 Error Classification ..................................................................................... 31
7.6.1 Development Errors ................................................................................. 31
7.6.2 Runtime Errors ........................................................................................ 32
7.6.3 Transient Faults ....................................................................................... 32
7.6.4 Production Errors .................................................................................... 32
7.6.5 Extended Production Errors ..................................................................... 32
7.7 Other requirements..................................................................................... 32