AUTOSAR_MCU_Tool_UserManuals

AUTOSAR MCAL R4.0.3
User‟s Manual

MCU Driver Component Ver.1.0.3

Generation Tool User‟s Manual

Target Device:
RH850/P1x

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.0.01 Apr 2015

Notice
1.
All information included in this document is current as of the date this document is issued. Such information, however, is subject
to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the
latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and
different information to be disclosed by Renesas Electronics such as that disclosed through our website.
2.
Renesas Electronics does not assume any liability for infringement of 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. No
license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of
Renesas Electronics or others.
3.
You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part.
4.
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 of these circuits, software, and
information in the design of your equipment.  Renesas Electronics assumes no responsibility for any losses incurred by
you or third parties arising from the use of these circuits, software, or information.
5.
When exporting the products or technology described in this document, you should comply with the applicable export control
laws and regulations and follow the procedures required by such laws and regulations.  You should not use Renesas Electronics
products or the technology described in this document for any purpose relating to military applications or use by the military,
including but not limited to the development of weapons of mass destruction.  Renesas Electronics products and technology may
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.
6.
Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics
does not warrant that such information is error free.  Renesas Electronics assumes no liability whatsoever for any damages
incurred by you resulting from errors in or omissions from the information included herein.
7.
Renesas Electronics products are classified according to the following three quality grades:  "Standard", "High Quality", and
"Specific".  The recommended applications for each Renesas Electronics product depends on the product's quality grade, as
indicated below.  You must check the quality grade of each Renesas Electronics product before using it in a particular application.
You may not use any Renesas Electronics product for any application categorized as "Specific" without the prior written consent
of Renesas Electronics.  Further, you may not use any Renesas Electronics product for any application for which it is not intended
without the prior written consent of Renesas Electronics.  Renesas Electronics shall not be in any way liable for any damages or
losses incurred by you or third parties arising from the use of any Renesas Electronics product for an application categorized as
"Specific" or for which the product is not intended where you have failed to obtain the prior written consent of Renesas
Electronics.  The quality grade of each Renesas Electronics product is "Standard" unless otherwise expressly specified in a
Renesas Electronics data sheets or data books, etc.
"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.
"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anti-
crime systems; safety equipment; and medical equipment not specifically designed for life support.
"Specific":
Aircraft; aerospace equipment; submersible repeaters; nuclear reactor control systems; medical equipment or
systems for life support (e.g. artificial life support devices or systems), surgical implantations, or healthcare
intervention (e.g. excision, etc.), and any other applications or purposes that pose a direct threat to human life.
8.
You should use the Renesas Electronics products described in this document within the range specified by Renesas Electronics,
especially with respect to the maximum rating, operating supply voltage range, movement power voltage range, heat radiation
characteristics, installation and other product characteristics. Renesas Electronics shall have no liability for malfunctions or
damages arising out of the use of Renesas Electronics products beyond such specified ranges.
9.
Although Renesas Electronics endeavors to improve the quality and reliability of its 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 be sure to implement safety measures to guard
them against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a
Renesas Electronics product, 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.  Because the
evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or system
manufactured by you.
10.   Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility
of each Renesas Electronics product.  Please use Renesas Electronics products in compliance with all applicable laws and
regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive.
Renesas Electronics assumes no liability for damages or losses occurring as a result of your noncompliance with applicable laws
and regulations.
11.   This document may not be 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, or if you have any other inquiries.

(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
AUTOSAR
AUTomotive Open System ARchitecture
BSWMDT
Basic Software Module Description Template
DEM
Diagnostic Event Manager
ECM
Error Control Module
ECU
Electronic Control Unit
Id
Identifier
MCAL
Micro Controller Abstraction Layer
MCU
Micro Controller Unit
SPAL
Standard Peripheral Abstraction Layer
XML
eXtensible Mark-up Language

Definitions

Terminology
Description
BSWMDT File
This file is the template for the Basic Software Module Description.
Configuration XML File
This file contains the setting of command line options.
ECU Configuration Description
Input file to MCU Driver Generation Tool. It is generated by ECU
File
Configuration Editor.
Sl.No
Serial Number.
Translation XML File
This file contains the translation and device specific header file path.

5

List of Figures

Figure 3-1
Overview of MCU Driver Generation Tool ........................................................................... 13

List of Tables

Table 5-1
Output Files Description ......................................................................................................... 17

8

Introduction
Chapter 1

Chapter 1 Introduction

The MCU Driver component provides services for basic microcontroller
initialization, Error Control Module (ECM), reset and microcontroller
specific functions required from other SPAL components.

The MCU Driver Component comprises of two sections i.e., Embedded
Software and Generation Tool to achieve scalability and configurability.

The document describes the features of the MCU Driver Generation Tool.
MCU Driver Generation Tool is a command line tool that extracts information
from ECU Configuration Description File, BSWMDT File and generates MCU
Driver C source and C header files (Mcu_PBcfg.c, Mcu_Reg.h, Mcu_Cbk.h
and Mcu_Cfg.h).

1.1.
Document Overview

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

Section
Contents
Section 1 (Introduction)
Provides an introduction to 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 (MCU Driver
Provides the MCU Driver Generation Tool Overview.
Generation Tool 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 MCU Driver
Generation 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 MCU Driver
Validation)
Generation Tool.
Section 8 (Messages)
Describes all the Error/Warning/Information messages of R4.0.3 which
helps the user to understand the probable reason for the same.
Section 9 (Notes)
Provides notes to help the user to understand this document better.

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:

Sl. No Title
Version
1.
Autosar R4.0
3.2.0

AUTOSAR_SWS_MCUDriver.pdf
2.
P1x Parameter Definition File
1.1.4

R403_MCU_P1M_04_05.arxml.arxml

3.
P1x Parameter Definition File
1.0.1

R403_MCU_P1M_10_to_15_18_to_23.arxml.arxml

2.2.
Trademark Notice

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

11

Chapter 2 Reference

12

MCU Driver Generation Tool Overview
Chapter 3

Chapter 3  MCU Driver Generation Tool Overview

MCU Driver Generation Tool overview is shown below.

ECU

Configuration

Description File,
Mcu_Cfg.h,
MCU Driver
Translation XML
Mcu_Reg.h,
Generation
File, BSWMDT File
Mcu_Cbk.h,
Tool
and
Mcu_PBcfg.c
Configuration
XML File

Figure 3-1  Overview of MCU Driver Generation Tool

MCU Driver Generation Tool is a command line tool that extracts, analyzes
the configuration details provided in the input file and validates correctness of
the data and provides scalability and configurability for MCU Driver module. It
accepts ECU Configuration Description File(s), Translation XML File,
BSWMDT File and Configuration XML File as input and displays appropriate
context sensitive error messages for wrong input and exits. Tool creates the
Log file (Mcu.log) that contains the list of Error/Warning/Information messages
in the output directory.

For the error free input file, the tool generates the following output files:
Mcu_Cfg.h, Mcu_Reg.h, Mcu_Cbk.h and Mcu_PBcfg.c.

Mcu_Cfg.h, Mcu_Reg.h and Mcu_Cbk.h will be compiled and linked with
MCU Driver Module. Mcu_PBcfg.c will be compiled and linked separately
from the other C Source files and placed in flash.

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

Remark
•
In case of errors the generation tool returns a 1, in case of no errors
the generation tool returns a 0.

•
MCU Driver Generation Tool uses “Common Published Information” from
MCU module specific BSWMDT File. MCU module specific BSWMDT File
should not be updated manually since it is ”Static Configuration” file.

13

Chapter 3 MCU Driver Generation Tool Overview

14

Input Files
Chapter 4

Chapter 4 Input Files

MCU Driver Generation Tool accepts ECU Configuration Description File(s),
Translation XML File, BSWMDT File and Configuration XML File as input.
MCU Driver Generation Tool needs information about MCU Driver module.
Hence ECU Configuration Description File should contain configuration of
MCU Driver module. Generation 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 mentioned in Reference Documents section.

15

Chapter 4 Input Files

16

Output Files
Chapter 5

Chapter 5  Output Files

MCU Driver Generation Tool generates configuration details in C Header and
C Source files Mcu_Cfg.h, Mcu_Reg.h, Mcu_Cbk.h and Mcu_PBcfg.c.

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

Table 5-1  Output Files Description

Output File
Details
Mcu_Cfg.h
This file contains pre-compile time parameters.
Mcu_Reg.h
This file contains the definitions for addresses of the hardware registers used in the
MCU Driver Module.
Mcu_Cbk.h
This file contains callback function prototype declarations to be used by application.
Mcu_PBcfg.c
This file contains post-build configuration data.

Remark  Output files generated by MCU Driver Generation Tool should not be modified
or edited manually.

17

Chapter 5 Output Files

18

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 MCU Driver and DEM component related
configuration.

•  Default Translation XML File (Mcu_P1x.trxml) should be present in same
location of Mcu_P1x.exe when the variant specific trxml file is not given as
input in command line.

•  Default Configuration XML File (Mcu_P1x.cfgxml) must be present in same
location of Mcu_P1x.exe.

•  If  Translation  XML  File  is  not  provided  on  the  command  line,
Mcu_P1x.trxml  which  is  present  in  same  location  of  Mcu_P1x.exe  is
considered as „default‟ Translation XML File.

•  If Configuration XML File is not provided on the command line,
Mcu_P1x.cfgxml which is present in same location of Mcu_P1x.exe is
considered as „default‟ Configuration XML File.

•  Translation XML File should contain the file extension „.trxml‟.

•  Configuration XML File should contain the file extension „.cfgxml‟.

•  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.

•  If the output files generated by MCU Driver Generation 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 should 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 MCU Driver
Generation Tool. Otherwise Tool may not produce the expected results or
may lead to errors/warnings/information messages.

•  User has to make sure that the respective device specific configuration file
is used. Otherwise 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  Please refer the MCU Component User Manual for deviations from AUTOSAR
specifications, if any.

19

Chapter 6 Precautions

20

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 MCU Driver Generation 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 8 “Messages”.

The Generation 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.

•  ERR/WRN/INF<mid><xxx>: <Error/Warning/Information Message>.

where,
<mid>: 101 - MCU Driver Module Id (101) for user configuration checks.

000 - for command line checks.

<xxx>: 001-999 - Message Id.

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

•  Path: Absolute path of the container in which the parameter is present.

„File Name‟ and „Path‟ need not be present for all Error/Warning/Information
messages.

21

Chapter 7 User Configuration Validation

22

Messages
Chapter 8

Chapter 8  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 Generation Tool.

8.1  Error Messages

ERR101001: Number of fields is not same for the entity 'Structure Name'.

This error occurs, if the number of fields is not same in the structure that is to
be generated in the output file.

ERR101002: Field 'Field Name' is empty in the entity 'Structure Name'.

This error occurs, if the structure fields that are to be generated in the output
file are empty.

ERR101003: 'MCU Driver' or 'DEM Driver' Component is not present in the
input file(s).

This error occurs, if MCU Driver or DEM Driver component is not present in
the input ECU Configuration Description File(s).

ERR101004: The parameter 'parameter name' in the container 'container
name' should be configured.

This error occurs, if any of the mandatory configuration parameter(s)
mentioned below is (are) not configured in ECU Configuration Description File.
The list of mandatory parameters with respect to container is listed below:

Parameter Name
Container Name
McuVersionCheckExternalModules

McuDevErrorDetect

McuGetRamStateApi

McuInitClock

McuNoPll

McuPerformResetApi
McuGeneralConfiguration

McuVersionInfoApi

McuCriticalSectionProtection

McuSwResetCallApi

McuEcmDelayTimerOverflowValue

McuEcmErrorOutputMode

23

Chapter 8                                                                                                                               Messages

Parameter Name
Container Name
McuEcmErrorOutTimer

McuRamSectorSetting

McuDeviceName

McuClm0Operation

McuGeneralConfiguration
McuClm0MonitoringClockAccuracy

McuClm0SamplingClockAccuracy
McuClm1Operation
McuClm1MonitoringClockAccuracy
McuClm1SamplingClockAccuracy
McuClm2Operation
McuClm2MonitoringClockAccuracy
McuClm2SamplingClockAccuracy
McuClm3Operation
McuClm3MonitoringClockAccuracy
McuClm3SamplingClockAccuracy
McuCvmSelfDiagnosticTest
McuClma0SelfDiagnosticTest
McuClma1SelfDiagnosticTest
McuClma2SelfDiagnosticTest
McuClma3SelfDiagnosticTest
McuEcmSelfDiagnosticTest
McuReadBackConfiguration

McuLoopCount
McuLockStepSelfDiagnosticTest
McuLviDetectionLevel

McuLviResetMask

McuCvmOutMaskFbist
McuModuleConfiguration
McuCvmOutMaskDiag
McuCvmOutputFilter
McuCvmResetEnable
McuClockSettingId

McuMainOsciFrequency
McuClockSettingConfig
McuCpuMainSysClk
McuUnitName
McuUnitName

McuHighspeedPeriClk
McuPeripheralClock
McuUnitName

McuLowspeedPeriClk
McuPeripheralClock
McuWdtCounterDivider

McuWdtacounterClk
McuUnitName
McuPeripheralClock
McuExternalClk0SourceSel

McuExternalClk0DividerSel

McuExternalClock0
McuExternalClkOutSetting
McuExternalClk1SourceSel
McuExternalClk1DividerSel
McuExternalClock1
24

Messages
Chapter 8

Parameter Name
Container Name
McuEcmErrorMaskableInterrupt

McuEcmErrorNonMaskableInterrupt
McuEcmErrorSource0 to McuEcmErrorSource42
McuEcmErrorInternalReset
(except McuEcmErrorSource2,
McuEcmErrorSource3, McuEcmErrorSource13,
McuEcmErrorNMIDelayTimer
McuEcmErrorSource25 and
McuEcmErrorMIDelayTimer
McuEcmErrorSource35)
McuEcmErrorOutputMask

McuEcmErrorInternalReset

McuEcmErrorOutputMask
McuEcmErrorSource129
MCU_E_CLOCK_FAILURE

McuDemEventParameterRefs
MCU_E_WRITE_TIMEOUT_FAILURE
McuModeType

McuMode
McuModeSettingConf
McuRamDefaultValue

McuRamSectionBaseAddress

McuRamSectorSettingConf
McuRamSectionSize
McuRamTypeSel

McuRstRsnConfPowOnClr

McuRstRsnConfPinRst

McuRstRsnConfSwRst
McuRstRsnConfWdta

McuRstRsnConfLockStepCompare
McuRstRsnConfClkMonUprLimErMosc

McuRstRsnConfClkMonLwrLimErMosc
McuRstRsnConfClkMonUprLimErWdt

McuRstRsnConfClkMonLwrLimErWdt
McuRstRsnConfClkMonUprLimErPclk
McuResetReason
McuRstRsnConfClkMonLwrLimErPclk

McuRstRsnConfClkMonUprLimErPe1
McuRstRsnConfClkMonLwrLimErPe1

McuRstRsnConfLRamEcc2AddPrty

McuRstRsnConfInstCacheRamEcc2
McuRstRsnConfCodeFlsEcc2AddPrty

McuRstRsnConfDataFlsEcc2

McuRstRsnConfDtsRamEcc2
McuRstRsnConfCsihRamEcc2

McuRstRsnConfCanRamEcc2

McuRstRsnConfFrRamEcc2
McuRstRsnConfFlsProgMode

McuRstRsnConfTestMode

McuRstRsnConfSingChipModInact
McuRstRsnConfPeGuard

McuRstRsnConfPBusGuard

McuRstRsnConfSarAdcPrty
McuRstRsnConfBusDataPrty

McuRstRsnConfEcmCompare

McuRstRsnConfLvi
McuRstRsnConfTempSensor

25

Chapter 8                                                                                                                               Messages

Parameter Name
Container Name

McuRstRsnConfDmaTrans
McuRstRsnConfDmaViol

McuRstRsnConfLRamEcc1
McuResetReason
McuRstRsnConfCodeFlsEcc1
McuRstRsnConfDataFlsEcc1


McuRstRsnConfDtsRamEcc1

McuRstRsnConfPeriRamEcc1
McuRstRsnConfBistCodeEcc1
McuRstRsnConfBistCodeEcc2
McuRstRsnConfFaci
McuRstRsnConfEcmDelayOverFlow
McuRstRsnConfRstUndefined
McuRstRsnConfRstUnknown
McuRstRsnConfCvmRst

ERR101005: The value for parameter ‘parameter name’ present in the
container 'container name' should be same across multiple
configuration set 'McuModuleConfiguration'.

This error occurs, if the value configured for the following parameter present
in the respective container is not same across multiple configuration set
McuModuleConfiguration.

  Parameter
  Container
McuMainOsciFrequency
  McuClockSettingConfig
McuWdtCounterDivider
  McuWdtacounterClk

ERR101006: The value of the parameter
'McuEcmErrorMaskableInterrupt' should configure as <true> since the
'McuMiNotification' parameter is configured in container <Configured
ecm error source container>.

This error occurs, if the value of the parameter
McuEcmErrorMaskableInterrupt is not configure as true, since the
McuMiNotification parameter is configured in container <Configured ecm
error source container>.

ERR101007: The configured value in 'McuPeripheralClock'  in container
'McuWdtacounterClk' should be equal to <8000000/configured value of
McuWdtCounterDivider parameter>.

This error occurs, if the configured value in McuPeripheralClock in container
McuWdtacounterClk is not equal to <8000000/configured value of
McuWdtCounterDivider parameter>.

ERR101008: The configured value in 'McuExternalClockX' in container
'McuExternalClkOutSetting' should be equal to
<McuExternalClkXSourceSel/McuExternalClkXDividerSel>.

This error occurs, if the configured value in McuExternalClockX in container
McuExternalClkOutSetting is not equal to
<McuExternalClkXSourceSel/McuExternalClkXDividerSel>.
26

Messages
Chapter 8


                           Remark Where X=0 or 1

ERR101009: The value of the parameter
'McuEcmErrorNonMaskableInterrupt' should configure as <true> since
the 'McuNmiNotification' parameter is configured in container
<Configured ecm error source container>.

This error occurs, if the value for parameter
McuEcmErrorNonMaskableInterrupt is not configure as true, since the
McuNmiNotification parameter is configured in container <Configured ecm
error source container>.

ERR101017: The value for parameter 'parameter name' configured in
container 'container name' should be <expected value of parameter>. In
general per configuration set, the value of 'parameter name' parameter
should start with <0> and should be sequential without any gaps.

This error occurs, if the value configured for the following parameter in the
respective container does not start with 0 and not sequential in multiple
configurations set container McuModuleConfiguration.

Parameter
Container
McuClockSettingId
McuClockSettingConfig

                           Remark   As issue raised in Bugzilla: 54536 Autosar parameter
McuClockSettingId in McuClockSettingConfig container range is changed to 0
to 255 instead of 1 to 255.

ERR101020: The value for parameter ' McuRamSectionBaseAddress ' in
container ' McuRamSectorSettingConf ' should be in the range.

This error occurs, if value for parameter McuRamSectionBaseAddress in
container McuRamSectorSettingConf is not in the range of <configured value
for McuRamTypeSel>.

ERR101022: Atleast one 'McuRamSectorSettingConf' container should be
configured. Since 'McuRamSectorSetting' parameter in
'McuGeneralConfiguration' container is configured as <true>.

This error occurs, if no McuRamSectorSettingConf container is configured and
parameter McuRamSectorSetting in McuGeneralConfiguration container is
configured as <true>.

ERR101026: The reference path <McuDemEventParameterRefs> provided
for the parameter 'Parameter Name' within the container 'Container Name'
is incorrect.

This error occurs, if the reference path <McuDemEventParameterRefs>
provided for the following parameters in McuDemEventParameterRefs
container is not correct.

Parameter
Container
MCU_E_CLOCK_FAILURE

McuDemEventParameterRefs

27

Chapter 8                                                                                                                               Messages

Parameter
Container
MCU_E_WRITE_TIMEOUT_FAILURE

MCU_E_CVM_SELFDIAG_FAILURE

MCU_E_CLM_SELFDIAG_FAILURE
McuDemEventParameterRefs
MCU_E_ECM_SELFDIAG_FAILURE
MCU_E_LOCKSTEP_SELFDIAG_FAILURE

ERR101027: The short name of the container 'McuClockSettingConfig'
should be same for clock having 'McuClockSettingId' <value of
McuClockSettingId> across multiple configuration sets.

This error occurs, if the short name of the container McuClockSettingConfig is
not same for clock having same McuClockSettingId across multiple
configuration sets.

ERR101029: The value for parameter 'McuLviResetMask' present in
container 'McuModuleConfiguration' should be same across multiple
configurations set.

This error occurs, if the value for parameter McuLviResetMask present in
container McuModuleConfiguration is not same across multiple configurations
set.

ERR101031: The value for parameter 'McuInitClock' present in container
'McuGeneralConfiguration' should not be configured as <false>.

This error occurs, if the value for parameter McuInitClock present in container
McuGeneralConfiguration is configured as false.

ERR101032: The value for the parameter 'Parameter Name' present in the
container 'Container Name' should be same across multiple
configuration set 'McuModuleConfiguration'.

This error occurs, if the value configured for the following parameters in
McuDemEventParameterRefs container is not same across multiple
configuration set container McuModuleConfiguration.

Parameter
Container
MCU_E_CLOCK_FAILURE

MCU_E_WRITE_TIMEOUT_FAILURE


MCU_E_CVM_SELFDIAG_FAILURE

McuDemEventParameterRefs
MCU_E_CLM_SELFDIAG_FAILURE

MCU_E_ECM_SELFDIAG_FAILURE

MCU_E_LOCKSTEP_SELFDIAG_FAILURE

28

Messages
Chapter 8

ERR101035: The value for parameter 'McuClockSettingId' present in
container 'McuClockSettingConfig' should be same across multiple
configurations set container 'McuModuleConfiguration'.

This error occurs, if the value for parameter McuClockSettingId present in
container McuClockSettingConfig does not same across multiple configurations
set container McuModuleConfiguration.

ERR101036: Parameter 'MCU_E_CVM_SELFDIAG_FAILURE' should be
configured, since parameter 'McuCvmSelfDiagnosticTest' inside
container ‘McuGeneralConfiguration' is configured as <true>.

This error occurs, if parameter 'MCU_E_CVM_SELFDIAG_FAILURE' is not
configured, since parameter 'McuCvmSelfDiagnosticTest' inside container
„McuGeneralConfiguration' is configured as true.

ERR101037: Parameter 'MCU_E_CLM_SELFDIAG_FAILURE' should be
configured, since one or more of parameters
'McuClma0SelfDiagnosticTest', 'McuClma1SelfDiagnosticTest',
'McuClma2SelfDiagnosticTest' and 'McuClma3SelfDiagnosticTest' inside
container ‘McuGeneralConfiguration’ is configured as <true>.

This error occurs, if parameter 'MCU_E_CLM_SELFDIAG_FAILURE' is not
configured, since one or more of parameters 'McuClma0SelfDiagnosticTest',
'McuClma1SelfDiagnosticTest', 'McuClma2SelfDiagnosticTest' and
'McuClma3SelfDiagnosticTest' inside container „McuGeneralConfiguration‟ is
configured as true.

ERR101038: Parameter 'MCU_E_ECM_SELFDIAG_FAILURE' should be
configured, since parameter 'McuEcmSelfDiagnosticTest' inside
container 'McuGeneralConfiguration' is configured as <true>.

This error occurs, if parameter 'MCU_E_ECM_SELFDIAG_FAILURE' is not
configured, since parameter 'McuEcmSelfDiagnosticTest' inside container
„McuGeneralConfiguration' is configured as true.

ERR101039: Parameter 'MCU_E_LOCKSTEP_SELFDIAG_FAILURE'
should be configured, since parameter 'McuLockStepSelfDiagnosticTest'
inside container 'McuGeneralConfiguration' is configured as <true>.

This error occurs, if parameter 'MCU_E_LOCKSTEP_SELFDIAG_FAILURE' is
not configured, since parameter 'McuLockStepSelfDiagnosticTest' inside
container „McuGeneralConfiguration' is configured as true.

ERR101040: The value for parameters 'McuEcmErrorNMIDelayTimer' and
'McuEcmErrorMIDelayTimer' should not be configured as <true> for
containers 'McuEcmErrorSource4 to McuEcmErrorSource11'.

This error occurs, if the value for parameter 'McuEcmErrorNMIDelayTimer' and
'McuEcmErrorMIDelayTimer' are configured as true for containers
'McuEcmErrorSource4 to McuEcmErrorSource11'.

ERR101041: The value for parameter ‘Parameter Name’ present in
container McuGeneralConfiguration' should be configured as <true>
since parameter 'Parameter Name' is configured as <true> ".

29

Chapter 8                                                                                                                               Messages

This error occurs, if the value configured for parameter on left column of
following table present in container McuGeneralConfiguration is true but value
configured for parameter on right column of following table is configured as
false.

The Parameter which is configured as <true>
Parameter that should be configured as
<true>
McuClma0SelfDiagnosticTest
McuClm0Operation

McuClma1SelfDiagnosticTest
McuClm1Operation

McuClma2SelfDiagnosticTest
McuClm2Operation
McuClma3SelfDiagnosticTest
McuClm3Operation

ERR101042: The value for the parameters 'parameter name' and
'parameter name' present in the container 'McuDemEventParameterRefs'
should be unique.

This error occurs, if the value configured for the following parameters in
McuDemEventParameterRefs container is not unique.

Parameter
Container
MCU_E_CLOCK_FAILURE

MCU_E_WRITE_TIMEOUT_FAILURE

MCU_E_CVM_SELFDIAG_FAILURE

McuDemEventParameterRefs
MCU_E_CLM_SELFDIAG_FAILURE
MCU_E_ECM_SELFDIAG_FAILURE
MCU_E_LOCKSTEP_SELFDIAG_FAILURE

ERR101043: Atleast one ‘McuWdtacounterClk’ container should be
configured. Since ‘McuClm2Operation’ parameter in
'McuGeneralConfiguration' container is configured as <true>.

This error occurs, if container McuWdtacounterClk is not configured since
parameter McuClm2Operation of container McuGeneralConfiguration is
configured as true.

ERR101044: The configured value for parameter ‘McuExternalClockX’ in
container 'McuExternalClkOutSetting’ should be equal to 0.

This error occurs, if the value configured for the parameter McuExternalClockX
in container  McuExternalClkOutSetting is not equal to 0.

                   Remark Where X=0 or 1
ERR101045: The value for parameters ‘McuEcmErrorMaskableInterrupt’
or ‘McuEcmErrorNonMaskableInterrupt’ should be <true> in all container
McuEcmErrorSource<12, 14, 17, 18 to 20, 34, 38 and 39> since
‘McuGetRamStateApi’ is configured as <true> in
‘McuGeneralConfiguration’ container.

This error occurs, if the value configured for the parameters
McuEcmErrorMaskableInterrupt or should be <true> in all containers
McuEcmErrorSource<12, 14, 17, 18 to 20, 34, 38 and 39> when
30

Messages
Chapter 8

McuGetRamStateApi‟ is configured as <true> in „McuGeneralConfiguration‟
container.

ERR101046: The order of container 'McuRamSectorSettingConf'
configuration and their short names should be same across multiple
configuration sets.

This error occurs, if the order of container 'McuRamSectorSettingConf'
configuration and their short are not same across multiple configuration

ERR101047: The number of 'McuRamSectorSettingConf' containers
should be same across multiple configuration sets.

This error occurs, if the number of 'McuRamSectorSettingConf' containers are
not same across multiple configuration sets.

8.2  Warning Messages

WRN101001: The value of the parameters
'McuEcmErrorNonMaskableInterrupt' and
'McuEcmErrorMaskableInterrupt' should not be <true> since the
parameter 'McuEcmErrorInternalReset' of the container <configured Ecm
error sources>is configured as <true>.

This warning occurs, if the value of the parameters
McuEcmErrorNonMaskableInterrupt and McuEcmErrorMaskableInterrupt is
<true> since the parameter McuEcmErrorInternalReset of the container
<configured Ecm error sources>is configured as <true>.

WRN101002: The value of the parameter 'McuEcmErrorMaskableInterrupt'
should not be <true> since the parameter
'McuEcmErrorNonMaskableInterrupt' of the container <configured Ecm
error sources> is configured as <true>.

This warning occurs, if the value of the parameter
McuEcmErrorMaskableInterrupt is <true> since the parameter
McuEcmErrorNonMaskableInterrupt of the container <configured Ecm error
sources>is configured as <true>.

8.3  Information Messages

INF101001: The configured ‘McuRamSectorSettingConf’ container is not
used. Since ‘McuRamSectorSetting’ parameter in
‘McuGeneralConfiguration’ container is configured as <false>.

This information occurs, if McuRamSectorSettingConf container is configured
and parameter McuRamSectorSetting in McuGeneralConfiguration container is
configured as <false>.

INF101002: The configured value for parameter ‘McuExternalClockX' will
be ignored if parameter 'McuExternalClkXSourceSel' is configured as
'MCU_NO_OUTPUT'.

This information occurs, if the configured value of parameter
McuExternalClockX is ignored when parameter McuExternalClkXSourceSel  is
configured as MCU_NO_OUTPUT.

31

Chapter 8                                                                                                                               Messages

                   Remark Where X=0 or 1

INF101003: The parameter ‘McuEcmErrorMIDelayTimer’ / ’
McuEcmErrorNMIDelayTimer’ does not have any effect since the
corresponding intrrupt ‘McuEcmErrorMaskableInterrupt’ /
‘McuEcmErrorNonMaskableInterrupt’ is configured as <false> in
container ‘McuEcmErrorSource’ .

This information occurs, if the parameter McuEcmErrorMIDelayTimer is
configured when McuEcmErrorMaskableInterrupt is configured as false in
same or the parameter McuEcmErrorNMIDelayTimer is configured when
McuEcmErrorNonMaskableInterrupt is configured as false.

32

Notes
Chapter 9

Chapter 9 Notes

“Generation Tool” and “Tool” terminologies are used interchangeably to refer
MCU Driver Generation Tool.
33

35

Chapter 9
Notes
34

Revision History
Sl.No.  Description
Version
Date
1
Initial Version
1.0.0
18-Oct-2013
2
Following changes are made:
1.0.1
15-Apr-2014

•
Error message ERR101004 is updated in section 8.1 to add
the parameter McuRamSectorSetting,  McuRamTypeSel,
McuModeType and McuLockStepSelfDiagnosticTest and to
remove the parameters
MCU_E_CVM_SELFDIAG_FAILURE,
MCU_E_CLM_SELFDIAG_FAILURE and
MCU_E_ECM_SELFDIAG_FAILURE.

•
Error messages ERR101020,  ERR101022, ERR101036,
ERR101037, ERR101038, ERR101039, ERR101040,
ERR101041, ERR101042, ERR101043 and  ERR101044 are
added newly in section 8.1.

•
Information message INF101001 and INF101002 is added
newly in section 8.3.

•
Error messages ERR101026 and ERR101032 are updated in
section 8.1.
3
Following changes are made:
1.0.2
30-Oct-2014


Error message ERR101004 is updated in section 8.1.


Reference Documents section is updated for adding
Parameter Definition Files.


Chapter 6 Precautions is updated.


Remark of Chapter 4 Input Files is updated for PDF
reference.


Error messages ERR101045, ERR101046 and ERR101047
are added newly in section 8.1.


Information message INF101003 is added newly in section
8.3.


McuRstRsnConfCvmRst container is added in error message
ERR101004 table.

4
The follo  wing changes are made:
1.0.3
28-Apr-2015

•
Pdf name and version are updated in  Section 2.1

•
Updated version and copyright year.



35

AUTOSAR MCAL R4.0.3 User's Manual
MCU Driver Component Ver.1.0.3
Generation Tool User's Manual

Publication Date: Rev.0.01, April 29, 2015

Published by: Renesas Electronics Corporation

SALES  OFFICES

http://www.renesas.com
Refer  to "http://www.renesas.com/" for the latest  and  de  tailed  information.
Renesas  Electronics  America  Inc.
2880  Scott  Boulevard  Santa  Clara,  CA 95050-2554, U.S.A.
Tel:   +1-408-588-6000, Fax:  +1-408-588-6130
Renesas  Electronics  Canada  Limited
1101  Nicholson Road,  Newmarket, Ontari o  L3Y  9C3,  Canada
Tel:  +1-905-898-5441, Fax:  +1-905-898-3220
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-65030, Fax:  +49-211-6503-1327
Renesas  Electronics (China)  Co.,  Ltd.
7th  Floor,  Quantum  Plaza,  No.27  ZhiChunLu Haidian  District,  Beijing  100083,  P.R.China
Tel:  +86-10-8235-1155, Fax:  +86-10-8235-7679
Renesas  Electronics (Shanghai) Co.,  Ltd.
Unit  204,  205,  AZIA  Center,  No.1233  Lujiazui  Ring  Rd.,  Pudong  District,  Shanghai  200120,  China
Tel:  +86-21-5877-1818, Fax:  +86-21-6887-7858 / -7898
Renesas  Electronics Hong  Kong  Limited
Unit  1601-1613, 16/F.,  Tower  2, Grand  Century  Place,  193  Prince  Edward  Road  West,  Mongkok, Kowloon,  Hong  Kong
Tel:  +852-2886-9318, Fax:  +852  2886-9022/9044
Renesas  Electronics Taiwan  Co.,  Ltd.
7F,  No.  363  Fu Shing  North  Road  Taipei,  Taiwan
Tel:  +886-2-8175-9600, Fax:  +886  2-8175-9670
Renesas  Electronics Singapore Pte.  Ltd.
1 harbourFront Avenue,  #06-10,  Keppel  Bay  Tower,  Singapore 098632
Tel:  +65-6213-0200, Fax:  +65-6278-8001
Renesas  Electronics Malaysia  Sdn.Bhd.
Unit  906,  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 Korea  Co.,  Ltd.
11F.,  Samik  Lavied'  or Bldg.,  720-2  Yeoksam-Dong, Kangnam-Ku, Seoul  135-080,  Korea
Tel:  +82-2-558-3737, Fax:  +82-2-558-5141

© 2015 Renesas  Electronics  Corporation.  All rights reserved.
Colophon  1.0

AUTOSAR MCAL R4.0.3

User‟s Manual

Document Outline

Last modified October 12, 2025: Initial commit (1fadfc4)