R20UT3640EJ0102-AUTOSARs

AUTOSAR MCAL R4.0.3
User’s Manual

DIO Driver Component Ver.1.0.4

Generation Tool User’s Manual

Target Device:
RH850/P1x-C

All information contained in these materials, including products and product specifications,
represents information on the product at the time of publication and is subject to change by
Renesas Electronics Corp. without notice. Please review the latest information published by
Renesas Electronics Corp. through various means, including the Renesas Electronics Corp.
website (http://www.renesas.com).

www.renesas.com
Rev.1.02 Jun 2017

Notice
1.
Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor
products and application examples. You are fully responsible for the incorporation or any other use of the circuits, software, and information in
the design of your product or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third
parties arising from the use of these circuits, software, or information.
2.
Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other disputes involving patents,
copyrights, or other intellectual property rights of third parties, by or arising from the use of Renesas Electronics products or technical
information described in this document, including but not limited to, the product data, drawing, chart, program, algorithm, application examples.
3.
No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas
Electronics or others.
4.
You shall not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas Electronics
disclaims any and all liability for any losses or damages incurred by you or third parties arising from such alteration, modification, copy or
otherwise misappropriation of Renesas Electronics products.
5.
Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The intended
applications for each Renesas Electronics product depends on the product’s quality grade, as indicated below.
"Standard":          Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment;
home electronic appliances; machine tools; personal electronic equipment; and industrial robots etc.
"High Quality":   Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale communication
equipment; key financial terminal systems; safety control equipment; etc.
Renesas Electronics products are neither intended nor authorized for use in products or systems that may pose a direct threat to human life or
bodily injury (artificial life support devices or systems, surgical implantations etc.), or may cause serious property damages (space and undersea
repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims
any and all liability for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for which
the product is not intended by Renesas Electronics.
6.
When using the Renesas Electronics products, refer to the latest product information (data sheets, user’s manuals, application notes, "General
Notes for Handling and Using Semiconductor Devices" in the reliability handbook, etc.), and ensure that usage conditions are within the ranges
specified by Renesas Electronics with respect to maximum ratings, operating power supply voltage range, heat radiation characteristics,
installation, etc. Renesas Electronics disclaims any and all liability for any malfunctions or failure or accident arising out of the use of Renesas
Electronics products beyond such specified ranges.
7.
Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor products have
specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further, Renesas
Electronics products are not subject to radiation resistance design. Please ensure to implement safety measures to guard them against the
possibility of bodily injury, injury or damage caused by fire, and social damage in the event of failure or malfunction of Renesas Electronics
products, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention,
appropriate treatment for aging degradation or any other appropriate measures by your own responsibility as warranty for your products/system.
Because the evaluation of microcomputer software alone is very difficult and not practical, please evaluate the safety of the final products or
systems manufactured by you.
8.
Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas
Electronics product. Please investigate applicable laws and regulations that regulate the inclusion or use of controlled substances, including
without limitation, the EU RoHS Directive carefully and sufficiently and use Renesas Electronics products in compliance with all these
applicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses occurring as a result of your
noncompliance with applicable laws and regulations.
9.
Renesas Electronics products and technologies shall not be used for or incorporated into any products or systems whose manufacture, use, or
sale is prohibited under any applicable domestic or foreign laws or regulations. You shall not use Renesas Electronics products or technologies
for (1) any purpose relating to the development, design, manufacture, use, stockpiling, etc., of weapons of mass destruction, such as nuclear
weapons, chemical weapons, or biological weapons, or missiles (including unmanned aerial vehicles (UAVs)) for delivering such weapons, (2)
any purpose relating to the development, design, manufacture, or use of conventional weapons, or (3) any other purpose of disturbing
international peace and security, and you shall not sell, export, lease, transfer, or release Renesas Electronics products or technologies to any
third party whether directly or indirectly with knowledge or reason to know that the third party or any other party will engage in the activities
described above. When exporting, selling, transferring, etc., Renesas Electronics products or technologies, you shall comply with any applicable
export control laws and regulations promulgated and administered by the governments of the countries asserting jurisdiction over the parties or
transactions.
10.
Please acknowledge and agree that you shall bear all the losses and damages which are incurred from the misuse or violation of the terms and
conditions described in this document, including this notice, and hold Renesas Electronics harmless, if such misuse or violation results from your
resale or making Renesas Electronics products available any third party.
11.
This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas
Electronics.
12.
Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas
Electronics products.

(Note 1)   "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its majority-owned
subsidiaries.
(Note 2)   "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.

3

Abbreviations and Acronyms

Abbreviation / Acronym
Description
API
Application Programming Interface
AUTOSAR
AUTomotive Open System ARchitecture
BSWMDT
Basic Software Module Description Template
ECU
Electronic Control Unit
Id
Identifier
MCAL
Microcontroller Abstraction Layer
Dio/DIO
Digital Input Output
XML
eXtensible Mark-up Language
ARXML
AutosaR eXtensible Mark-up Language

Definitions

Terminology
Description
BSWMDT File
This file is the template for the Basic Software Module Description.
ECU Configuration Description
Input file to MCAL Code Generator Tool. ECU Configuration
File
Editor generates it.
Sl. No
Serial Number.
5

Introduction
Chapter 1

Chapter 1  Introduction

The DIO Driver component provides the service for initializing the whole DIO
structure of the microcontroller

The DIO Driver module comprises of two sections as Embedded Software
and the MCAL Code Generator Tool to achieve scalability and configurability.

The document describes the DIO module specific inputs and outputs of the
MCAL Code Generator Tool that is the common code generator engine used
for the generation of the configuration code for all MCAL modules. MCAL
Code Generator Tool is a command line tool that extracts information from
ECU Configuration Description File and BSWMDT File and generates DIO
Driver C Source and C Header files such as Dio_Cfg.h, Dio_Hardware.h,
Dio_Cbk.h, Dio_Lcfg.c, Dio_PBcfg.c and Dio_Hardware.c

This document contains information on the options, input and output files of
the MCAL Code Generator Tool. In addition, this manual covers a step-by-
step procedure for the usage of MCAL Code Generator Tool.

1.1  Document Overview

This user manual is organized as given in the table below:

      Table 1-1       Document Overview

Section
Contents
Section 1 (Introduction)
Introduces the document and explains how information is organized in
this manual.
Section 2 (Reference)
Provides a list of documents referred while developing this document.
Section 3 (Code Generation
Provides the Code Generation Overview.
Overview)
Section 4 (Input Files)
Provides information about ECU Configuration Description File.
Section 5 (Output Files)
Explains the output files that are generated by the MCAL Code
Generator Tool.
Section 6 (Precautions)
Contains precautions to be taken during configuration of ECU
Configuration Description File.
Section 7 (User Configuration
Describes about user configuration validation done by the MCAL Code
Validation)
Generator Tool.
Section 8 (Configuration

Overview)
Provides Container Overview and details of parameters.
Section 9 (Messages)
Describes all the Error/Warning/Information messages of R4.0.3 which
helps the user to understand the probable reason for
the same.
9

Chapter 1 Introduction

10

Reference
Chapter 2

Chapter 2  Reference

2.1  Reference Documents

The following table lists the documents referred to develop this document:

Table 2-1 Reference Documents

Sl. No.  Title
Version
1.
AUTOSAR_SWS_DIODriver.pdf
2.5.0
2.
MCAL_CodeGenerator_Tool_UserManual.pdf
1.7
3.
R20UT3828EJ0101-AUTOSAR.pdf
1.0.3

2.2  Trademark Notice

Microsoft and Windows are trademarks/registered trademarks of Microsoft
Corporation.
11

Chapter 2 Reference

12

Code Generation Overview
Chapter 3

Chapter 3  Code Generation Overview

Overview of Code Generation is shown below.

ECU

Configuration

Description File

and BSWMDT

File

Dio_Cfg.h,

Dio_Cbk.h,
Velocity

Template Files
MCAL Generator
  Dio_Hardware.h,

for Dio

Dio_PBcfg.c,

Dio_Lcfg.c,

Dio_Hardware.c

Configuration

XML File

Figure 3-1  Overview of Code Generation

•
ECU Configuration Description File (.arxml):
This file will contain DIO Driver specific configuration
information. This file shall be generated by AUTOSAR specified
Configuration Editor.

•
BSWMDT File (.arxml):
MCAL Code Generator Tool uses “Common Published
Information” from DIO module specific BSWMDT File. DIO
module specific BSWMDT File should not be updated manually
since it is “Static Configuration” file.

•
Velocity template files:
Dio_PBcfg_c, Dio_Cfg_h, Dio_Hardware_h, Dio_Cbk_h,
Dio_Hardware_c, Dio_Lcfg_c, Dio_Validate and
CommonHelper.
The MCAL Code Generator Tool interprets them in order to
provide user input validation and generate the final output file
needed by the AUTOSAR configuration chain. They are the
"logic" of the Code Generator

13

Chapter 3                                                                                                    Code Generation Overview

•
Configuration XML File (.xml):
This file is used to specify which velocity template to use and
their location and the name of the output file generated.

For the error free input file, the MCAL Code Generator Tool generates the
following output files: Dio_Cfg.h, Dio_Cbk.h, Dio_Hardware.h, Dio_PBcfg.c,
Dio_Lcfg.c and Dio_Hardware.c and displays appropriate context sensitive
error messages for wrong input and exits.

ECU Configuration Description File can be created or edited using ECU
Configuration Editor.

Concept of execution for MCAL Code Generator Tool
is as follows:

Generation start

Common
Validate
Helper

config.xml

ECU Configur  ation
Description

Files
MCAL Code Generator
Template files
And BSWMDT file
Tool

(.arxml)

No
Yes
Validation

successful

Displ  ay Error
Generate Output Files


  Generation stop

Figure 3-2       Flow Diagram of Code Generation

14

Code Generation Overview

Chapter 3

The module “Validate” will validate the configuration (contents of ECU
Configuration Description File(s) as input). If there are incorrect values or
incorrect dependencies, the MCAL Code Generator Tool will display error,
warning and information messages. In case of errors, the MCAL Code
Generator Tool will abort the execution.
Dio_Cfg_h / Dio_Cbk_h / Dio_PBcfg_c / Dio_Lcfg_c will generate compiler
switch / structures necessary to the AUTOSAR Configuration chain and
vendor specific parameters.
Dio_Hardware_h / Dio_Hardware_c will generate hardware related info
(defines number of actual instances / channels used / structure to access
to the I/O mapped peripheral).

Remark   Please consult the general MCAL Code Generator Tool User Manual
          (MCAL_CodeGenerator_Tool_UserManual.pdf) and
          Getting Started MCAL Drivers X1x User Manual (R20UT3828EJ0101-
          AUTOSAR.pdf) for details about the tool command line options.

15

Chapter 3 Code Generation Overview

16

Input Files

Chapter 4

Chapter 4 Input Files

MCAL Code Generator Tool will accept the config.xml file, which has paths
to the Velocity template files for generating Dio Driver files. MCAL Code
Generator Tool need ECU Configuration Description File(s) and BSWMDT
File as inputs to generate Dio Driver specific source files. Hence, ECU
Configuration Description File should contain configuration of DIO Driver
module. MCAL Code Generator Tool ignores any other AUTOSAR
component configured in the ECU Configuration Description File. ECU
Configuration Description File can be generated using configuration editor.

ECU Configuration Description File must comply with AUTOSAR standard
ECU Configuration Description File format

Remark The detailed explanation about the parameters and containers are found in
Parameter Definition File.

17

Chapter 4 Input Files

18

Output Files
Chapter 5

Chapter 5 Output Files

MCAL Code Generator Tool generates configuration details in C Header and C
Source files (Dio_Cfg.h, Dio_Cbk.h, Dio_PBcfg.c, Dio_Lcfg.c, Dio_Hardware.h
and Dio_Hardware.c).

The content of each output file is given in the table below:

Table 5-1 Output Files Description

Output File
Details
Dio_Cfg.h
This file contains the macro definitions for development error detects, version info API
and channel group. This file contains DIO Channel Configuration Handles, DIO Port
Configuration Handles and DIO Channel Group Configuration Handles.
Dio_PBcfg.c
This file contains Data Structures for DIO Port Group Configuration, DIO Port Channel
Configuration and DIO Port Channel Group Configuration. This file also contains
information on Number of ports and Channels configured.
Dio_Lcfg.c
This file contains Data Structure of DIO Port Channel Group Configuration.
Dio_Hardware.h
This file contains the definitions for addresses of the hardware registers used in the
Dio Driver Module.
Dio_Hardware.c
This file contains the declarations for addresses of the hardware registers used in the
Dio Driver Module.
Dio_Cbk.h
This file contains callback function prototype declarations to be used by application.

Remark Output files generated by MCAL Code Generator Tool should not be
modified or edited manually

19

Chapter 5 Output Files

.
20

Precautions
Chapter 6

Chapter 6  Precautions

•  ECU Configuration Description File and BSWMDT File must comply with
AUTOSAR standard for R4.0.3 ECU Configuration Description File and
BSWMDT File respectively.

•  The input file must contain DIO Driver module.

•  All the function names and the string values configured should follow C
syntax for variables. It can only contain alphanumeric characters and “_”. It
should start with an alphabet.

•  Configuration XML File should contain the file extension ‘.xml’.

•  Configuration XML File: config.xml file should convey the velocity template
file location and output file location

•  If the output files generated by MCAL Code Generator Tool are modified
externally, then they may not produce the expected results or may lead to
error/warning/Information messages.

•  Short Name for a container shall be unique within a name space.

•  An error free ECU Configuration Description File generated from
configuration editor has to be provided as input to the MCAL Code
Generator Tool. Otherwise, MCAL Code Generator Tool may not produce
the expected results or may lead to errors/warnings/information messages.

•  The description file should always be generated using AUTOSAR specified
configuration editor and it should not be edited manually.

Remark      Refer the DIO Component User Manual (R20UT3639EJ0102-
  AUTOSAR.pdf) for deviations from AUTOSAR.

21

Chapter 6 Precautions

22

User Configuration Validation
Chapter 7

Chapter 7  User Configuration Validation

This section provides help to analyze the error, warning and information
messages displayed during the execution of MCAL Code Generator Tool. It
ensures conformance of input file with syntax and semantics. It also performs
validation on the input file for correctness of the data.

For more details on list of Error/Warning/Information messages that are
displayed as a result of input file(s) validation, refer Chapter 9 “Messages”.

The MCAL Code Generator Tool displays error or warning or information
when the user has configured incorrect inputs. The format of
Error/Warning/Information message is as shown below.

<message_type>_<vendor_id>_<module_id>_<message_id>:<message_cont
ent>.
where,
  <message_type> : ERR/WARNING/INFO

  <vendor_id>            : vendor Id = 59

  <module_id>           : 120 - DIO Driver Module id (120) for user
               configuration checks.

  <Message_id>        :  001-999

  <message_content>:   Message content provides information
                about error or warning or information displayed
                when the user has configured incorrect inputs.

                                                               File Name’ and ‘Path’ need not be present for all
                                          Error/Warning/Information messages

                File Name: Name of the file in which the error has
                occurred

                Path: Absolute Path of the container in which
                the parameter that caused the message is
                present.

23

Chapter 7 User Configuration Validation

24

Configuration Overview
Chapter 8

Chapter 8  Configuration Overview

8.1  Container Overview

            The following figure represents container overview

Dio

DioDemEventParamet
DioConfig
DioGeneral

erRefs

DioPort

DioChannel
DioChannelGroup

Figure 8-1       Configuration Overview

25

Chapter 8                                                                                                         Configuration Overview

8.2  Pre-Compile Configurable Parameters

  Table 8-1 Pre-Compile Configurable Parameters
Container
Parameter Name
Para
Parameter
Parameter Description
Name
meter
Range
Type
This parameter switches
DioGeneral
DioDevErrorDetect
Boolean
TRUE / FALSE
the Development Error
Detection and Notification
ON or OFF.
Adds / removes the
DioMaskedWritePort
Boolean
TRUE / FALSE
service
Api
Dio_MaskedWritePort()
from the code.
This parameter adds /
DioFlipChannelApi
Boolean
TRUE / FALSE
removes the service
Dio_FlipChannel() from
the code.
Adds / removes the
DioVersionInfoApi
Boolean
TRUE / FALSE
service
Dio_GetVersionInfo() from
the code.
Enable / disable
DioVersionCheckExt
Boolean
TRUE / FALSE
AUTOSAR Version check
ernalModules
for inter-module
dependencies.
This parameter specifies if
TRUE / FALSE
the DIO driver CPU load
can be reduced by
DioCriticalSectionPr

Boolean
disabling the enter/exit
otection
critical section functionality

by adding a precompiled
configuration parameter to
the DIO driver.
R7F701370A,
R7F701371,
This parameter contains
DioDeviceName
Enum
R7F701372,
the supported device
R7F701373,
name.
R7F701374
This parameter
DioWriteVerify
Enum
WV_INIT_RUNTIME
Enable/Disable

WV_DISABLE
Register write verification
service.
This parameter allows the
DioUseWriteVerifyEr
user to generate a user
TRUE / FALSE
rorInterface
Boolean
specific callback function

for Register write

verification service.

DioWriteVerifyErrorI
A User can give a callback
nterface
String
STRING
function name for register
write verification in this

parameter.
26

Configuration Overview
Chapter 8

8.3  Post Build Time Configurable Parameters

Table 8-2 Post Build Time Configurable Parameters

Container
Parameter Name
Parameter
Parameter
Parameter
Name
Type
Range
Description
This value will
DioPort
be assigned to
Numeric identifier of the
the DIO port
DIO port. Not all MCU
DioPortId
Integer
symbolic name.
ports may be used for
DIO, thus there may be
This parameter
"gaps" in the list of all
is not used for
IDs.
implementation.
For
R7F701370A,
R7F701371,
R7F701372

PORTGROUP_
0_BITS_0_TO_
10_13_14,
PORTGROUP_
1_BITS_1_TO_
7,
PORTGROUP_
2_BITS_0_TO_
15,
PORTGROUP_
3_BITS_0_TO_
14,
PORTGROUP_
This parameter specifies
DioPortName
Enum
4_BITS_0_TO_
the DIO port group for a
14,
DIO port.
PORTGROUP_
5_BITS_4_TO_
15_0_1,
PORTGROUP_
6_BITS_0_TO_
15,
PORTGROUP_
7_BITS_0_TO_
9,
PORTGROUP_
8_BITS_0_TO_
15,
PORTGROUP_
9_BITS_0_TO_
8,
PORTGROUPJ
TAG_0_BITS_0
_TO_5

27

Chapter 8                                                                                                         Configuration Overview

Container
Parameter Name
Parameter
Parameter
Parameter
Name
Type
Range
Description

For R7F701373
PORTGROUP_
0_BITS_0_TO_
10_13_14,
PORTGROUP_
1_BITS_1_TO_
7,
PORTGROUP_
2_BITS_0_TO_
15,
PORTGROUP_
3_BITS_0_TO_
14,
PORTGROUP_
4_BITS_0_TO_
14,
PORTGROUP_
5_BITS_4_TO_
15_0_1,
PORTGROUP_
6_BITS_0_TO_
6_10_11_12_13
,
PORTGROUP_
7_BITS_0_TO_
5,
PORTGROUP_
9_BITS_7_8,
PORTGROUPJ
TAG_0_BITS_0
_TO_5
For R7F701374
28

Configuration Overview
Chapter 8

Container
Parameter Name
Parameter
Parameter
Parameter
Name
Type
Range
Description
PORTGROUP_
0_BITS_0_TO_
10_13_14,
PORTGROUP_
1_BITS_1_TO_
4,
PORTGROUP_
2_BITS_0_TO_
15,
PORTGROUP_
3_BITS_0_TO_
14,
PORTGROUP_
4_BITS_0_TO_
14,
PORTGROUP_
5_BITS_4_TO_
15_0_1,
PORTGROUP_
6_BITS_0_TO_
3,
PORTGROUPJ
TAG_0_BITS_0
_TO_5
This value will
DioChann
be assigned to
el
the symbolic
DioChannelId
Integer
names.
Channel Id of the DIO
channel
This parameter
is not used for
implementation.
DioChannelBitPositio
This parameter contains
Integer
0-15
n
channel bit position of the
DIO channel.
The DIO channel group is
DioChann
identified in DIO API by a
elGroup
This parameter
pointer to a data structure
DioChannelGroupIde
String
is not used for
(of type
ntification
implementation.
Dio_ChannelGroupType).
That data structure
contains the channel
group information.
This shall be the mask,
DioPortMask
Integer
0-65535
which defines the
positions of the channel
group.
The position of the
Channel Group on the
DioPortOffset
Integer
0-15
port, counted from the
LSB. This value can be
derived from
DioPortMask.
Reference to the
DioDemEventParam
DioDemEv
Reference to
DemEventParameter
eterRefs
entParame
Reference
DemEventId of
which shall be issued
terRefs

Dem module.
when the error "DIO
register write verification
29

Chapter 8                                                                                                         Configuration Overview

Container
Parameter Name
Parameter
Parameter
Parameter
Name
Type
Range
Description

failed (HW)" has
occurred.

30

Messages
Chapter 9

Chapter 9
Messages

The messages help to identify the syntax or semantic errors in the ECU
Configuration Description File. Hence, it ensures validity and correctness of
the information available in the ECU Configuration Description File.

The following section gives the list of error, warning and information
messages displayed by the MCAL Code Generator Tool.

9.1  Error Messages

          ERR_59_120_001: Parsing of Dio module is incorrect.
This error will occur when the parameter passed is not for Dio module.
ERR_59_120_002: The parameter ‘parameter name’ in the container ‘container
name’ shall be configured.
This error will occur, if any of the mandatory configuration parameter(s) mentioned
below is (are) not configured in ECU Configuration Description File.
Table 9-1 Parameters and Container related to error ERR_59_120_002

Container
Parameters
DioPort
DioPortName
DioChannel
DioChannelBitPosition
DioPortMask
DioChannelGroup
DioPortOffset

Note: DioChannel and DioChannelGroup containers are optional container. If these containers
are configured, then respective parameters from above table are mandatory.

ERR_59_120_003: The value <value for DioPortName> configured for the
parameter ‘DioPortName’ present in the container ‘DioPort’ shall be unique.
This error will occur, if the Parameter DioPortName is configured with same value
more than once in a configset.
ERR_59_120_004: The value for parameter ‘DioChannelBitPosition’ present in
the container ‘DioChannel’ of the DIO port group <value for DioPortName
parameter> is not in the range of <Start> and <End>.
This  error  will  occur,  if  the  value  for  parameter  DioChannelBitPosition  present  in  the
container DioChannel for respective DIO port group is not valid as configured channel
bit  position  must  belongs  to  the  respective  DIO  port  group.  In  above  error  message,
<Start> and <End> will be replaced by ‘start channel bit position’ and ‘end channel bit
position’ respectively for selected DIO port group.
Example: Suppose in PORTGROUP_2_BITS_0_TO_2, only 0 to 2 channels are
available. If user configures channels, which does not belong to
PORTGROUP_2_BITS_0_TO_2 then it is invalid configuration. Here start is 0 and end
is 2.
31

Chapter 9                                                                                                                              Messages

ERR_59_120_005: The value <value for DioChannelBitPosition> configured for
the parameter ‘DioChannelBitPosition’ present in the container ‘DioChannel’ of
the DIO port group <value for DioPortName parameter> shall be unique.
This error will occur, if the value for parameter DioChannelBitPosition present in the
container DioChannel is not unique for respective DIO port group configured for the
parameter DioPortName.
ERR_59_120_006: The value for parameter ‘DioPortMask’ <value for the
DioPortMask> present in the container ‘DioChannelGroup’ of the DIO port group
<value for DioPortName parameter> is not valid.
This error will occur, if value for parameter DioPortMask present in the container
DioChannelGroup for respective DIO port group is not valid as the grouped channels
must belong to the respective DIO port group.
Example: Suppose in PORTGROUP_2_BITS_0_TO_2, only 0 to 2 channels are
available. In this case, user should not consider channel 3 and channel 4 in channel
grouping, since channel 3 and channel 4 does not belong to
PORTGROUP_2_BITS_0_TO_2.
ERR_59_120_007: The number of ‘DioChannelGroup’ container is not same
across multiple configuration sets.
This error will occur, if the number of DioChannelGroup container is not same across
multiple configuration sets
ERR_59_120_008: The value for parameter ‘DioPortOffset’ <value for the
DioPortOffset> present in the container ‘DioChannelGroup’ of the DIO port
group <value for DioPortName parameter> is not valid. The value of the
parameter ‘DioPortOffset’ shall be equal to the start position of the DIO channel
group.
This error will occur, if the value for parameter DioPortOffset present in the container
DioChannelGroup is not valid. The value of the parameter DioPortOffset shall be equal
to the start position of the DIO channel group.
Example: Suppose DIO channel grouping started from Channel 2 then value for
parameter DioPortOffset shall be 2.
ERR_59_120_009: The short name <short name for DioPort> configured for the
container ‘DioPort’ shall be unique.
This error will occur, if short name of the container DioPort is not unique in ECU
Configuration Description File.
ERR_59_120_010: The short name <short name for DioChannel> configured for
the container ‘DioChannel’ shall be unique.
This error will occur, if short name of the container DioChannel is not unique in each
DioPort container.
ERR_59_120_011: The short name <short name for DioChannelGroup>
configured for the container ‘DioChannelGroup’ shall be unique.
This error will occur, if short name of the container DioChannelGroup is not unique in
each DioPort container.
ERR_59_120_012: The number of ‘DioPort’ container is not same across
multiple configuration sets.
This error will occur, if the number of DioPort container is not same across multiple
configuration sets.
ERR_59_120_013: The number of ‘DioChannel’ container is not same across
multiple configuration sets.
32

Messages
Chapter 9

This error will occur, if the number of DioChannel container is not same across
multiple configuration sets.
ERR_59_120_014: The number of ‘DioChannelGroup’ container is not same
across multiple configuration sets.
This error will occur, if the number of DioChannelGroup container is not same across
multiple configuration sets.
ERR_59_120_015:  DioWriteVerifyErrorInterface should have a valid error
notification, since the value of the parameter DioWriteVerify is
<WV_INIT_RUNTIME> and the parameter DioUseWriteVerifyErrorInterface is
configured as true.
This error will occur if there is no valid error notification configured for the parameter
DioUseWriteVerifyErrorInterface when write-verify check is enabled.
ERR_59_120_016: DioUseWriteVerifyErrorInterface parameter should not be
configured as true in DioGeneral Container, since the value of DioWriteVerify is
<WV_DISABLE>
This error will occur when the parameter DioUseWriteVerifyErrorInterface is configured
as true, when the write-verify check is disabled.
ERR_59_120_017: The reference path <path> provided for the parameter
'DIO_E_REG_WRITE_VERIFY’ within the container ‘DioDemEventParameterRefs’
is incorrect.
This error will occur, if the path provided for the parameter
DIO_E_REG_WRITE_VERIFY in the container DioDemEventParameterRefs is
incorrect.
ERR_59_120_018: The reference parameter 'DIO_E_REG_WRITE_VERIFY' of the
container 'DioDemEventParameterRefs' shall be configured, since the value of
the parameter 'DioWriteVerify' of the container 'DioGeneral' is configured as
<WV_INIT_RUNTIME>.
This error will occur, if there is no path provided for parameter
DIO_E_REG_WRITE_VERIFY
ERR_59_120_019: The error notification configured for the parameter
'DioWriteVerifyErrorInterface' should follow C syntax <[a-z A-Z][a-z A-Z 0-9_]>
This error will occur if the parameter DioWriteVerifyErrorInterface in container
DioGeneral0 does not follow C syntax <[a-zA-Z][a-zA-Z0-9_]>.
ERR_59_120_020: The container short name of ‘DioChannel’ container is not
same across multiple configuration sets.
This error will occur, if the container short name of DioChannel container is not same
across multiple configuration sets.
ERR_59_120_021: The variant is not supported currently.
This error occurs when the parameter 'DioDeviceName' in the General container is
configured other than the supported devices.
ERR_59_120_022: The error notification configured for the parameter
'DioWriteVerifyErrorInterface' should not be $ErrInterface, since the value of the
parameter 'DioWriteVerify' of the container 'DioGeneral' is configured as
<WV_INIT_RUNTIME>.
This error will occur if error notification configured as NULL/NULL_PTR for the
parameter DioUseWriteVerifyErrorInterface when write-verify check is enabled.

33

Chapter 9                                                                                                                              Messages

ERR_59_120_023: The container DioGeneral0 shall be configured
This error occur if the container DioGeneral0 is not configured.
          ERR_59_120_1001: The specified AR-PACKAGE Name not found in description
          file

This error will occur, if Specified AR-PACKAGE Name not found in description file
          ERR_59_100_1008: The parameter DioDevErrorDetect in the DioGeneral0
          Container is not configured.

This error will occur, if the parameter DioDevErrorDetect in the DioGeneral0 Container
is not configured.

9.2   Warning Messages

                   None

9.3  Information Messages

                   None

34

Revision History

Sl. No.  Description
Version
Date
1.
Initial Version
1.0.0
04-Aug-2015
2.
The following changes are made:
1.0.1
30-Mar-2016
1.  R number is added in the last page
2.  Added parameter DioCriticalSectionProtection in Figure 8-1
   Configuration overview.
3.  Added parameter DioCriticalSectionProtection in 8.2 Pre-
Compile Configurable Parameters.
4.  Added error message ERR_59_120_009 in 10.1.1 Error
Messages
5.  Description added for error messages in 10.1.1 Error
Messages
6.  Compiler version updated in 9.3 User Environment Settings

3

The following changes are made:
1.0.2
23-Feb-2017
1.  Chapter 1, Updated Introduction.
2.  Section 2.1, Updated reference document details.
Chapter 5, Updated description of output files.
3.  Chapter 6, Added one more point in precautions.
4.  Section 8.2, Updated Pre-Compile Configurable Parameters
5.  Section 8.3, Updated Post Build Time Configurable
Parameters
6.  Chapter 9.1.1, Modified Error messages ERR_59_120_001 to
ERR_59_120_009 and added ERR_59_120_010 to
ERR_59_120_022
7.  Chapter 7, Updated the format of Error/Warning/Information
message.
8.  Chapter 4, Updated description of Input files.
9.  Updated Chapters 1,3,4,5,6,7 by rephrasing Tool and DIO
Driver Generation Tool  with MCAL Code Generator Tool
10.  Removed Chapter 9 Generation Tool Options, Chapter-10
Notes.
11.  Chapter 3, Added remark for common MCAL Code Generator
Tool user manual.
12.  Figure 3-2 is renamed from Flow-Diagram of MCAL Code
Generator Tool to Flow-Diagram of Code Generation
13.  Chapter 3, Updated Figure 3-2 Flow-Diagram of Code
Generation
14.  Chapter 3, Renamed chapter name MCAL Code Generator
Tool Overview to Code Generation Overview
15.  Removed parameters from Figure 8-1, Configuration Overview
16.  Updated copyright year.

4
The follo  wing changes are made:
1.0.3
23-May-2017
1.  Added details of Error message ERR_59_120_023 in section
9.1
2.  Copyright details and notice are changed.
3.  Modified Table 8-2 to update values of the parameter
DioPortName.
4.  Added ERR_59_120_1001 and ERR_59_120_1008 in section
9.1.
5.  Chapter 3, Removed extension.vm from Velocity template
files.
5
1.  Updated Table 8-1 to change the parameter type and
1.0.4
16-Jun-2017
parameter range of the parameter DioWriteVerify.
2.  Updated R number of the Component User Manual in
Chapter 6.

35

AUTOSAR MCAL R4.0.3 User's Manual
DIO Driver Component Ver.1.0.4
Generation Tool User's Manual

Publication Date: Rev 1.02, June 16, 2017

Published by: Renesas Electronics Corporation

SALES  OFFICES

http://www.renesas.com

Refer  to "http://www.renesas.com/" for the latest  and  detailed  information.
Renesas Electronics America Inc.
2801 Scott Boulevard Santa Clara, CA 95050-2549, U.S.A.
Tel: +1-408-588-6000, Fax: +1-408-588-6130
Renesas Electronics Canada Limited
9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3
Tel: +1-905-237-2004
Renesas Electronics Europe Limited
Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K
Tel: +44-1628-585-100, Fax: +44-1628-585-900
Renesas Electronics Europe GmbH
Arcadiastrasse 10, 40472 Düsseldorf, Germany
Tel: +49-211-6503-0, Fax: +49-211-6503-1327
Renesas Electronics (China) Co., Ltd.
Room 1709, Quantum Plaza, No.27 ZhiChunLu Haidian District, Beijing 100191, P.R.China
Tel: +86-10-8235-1155, Fax: +86-10-8235-7679
Renesas Electronics (Shanghai) Co., Ltd.
Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, P. R. China 200333
Tel: +86-21-2226-0888, Fax: +86-21-2226-0999
Renesas Electronics Hong Kong Limited
Unit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong
Tel: +852-2265-6688, Fax: +852 2886-9022
Renesas Electronics Taiwan Co., Ltd.
13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan
Tel: +886-2-8175-9600, Fax: +886 2-8175-9670
Renesas Electronics Singapore Pte. Ltd.
80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949
Tel: +65-6213-0200, Fax: +65-6213-0300
Renesas Electronics Malaysia Sdn.Bhd.
Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia
Tel: +60-3-7955-9390, Fax: +60-3-7955-9510
Renesas Electronics India Pvt. Ltd.
No.777C, 100 Feet Road, HAL II Stage, Indiranagar, Bangalore, India
Tel: +91-80-67208700, Fax: +91-80-67208777
Renesas Electronics Korea Co., Ltd.
12F., 234 Teheran-ro, Gangnam-Gu, Seoul, 135-080, Korea
Tel: +82-2-558-3737, Fax: +82-2-558-5141

© 2006-2017 Renesas  Electronics  Corporation.  All rights reserved.
Colophon  4.1

AUTOSAR MCAL R4.0.3

User’s Manual

R20UT3640EJ0102

Document Outline

Last modified October 12, 2025: Initial commit (ddf2e20)