R20UT3729EJ0101-AUTOSARs

AUTOSAR MCAL R4.0.3
User’s Manual

WDG Driver Component Ver.1.0.6

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.1.01 Feb 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
Cbk
Callback Notification
DEM
Diagnostic Event Manager
ECU
Electronic Control Unit
ID/Id
Identifier
MCAL
MicroController Abstraction Layer
MCU
MicroController Unit
NMI
Non Maskable Interrupt
PDF
Parameter Definition File
PBcfg
Post-Build configuration
RUCG
Renesas Unified Code Generator
WDG/Wdg
Watchdog Driver
WDTA
Window Watchdog Timer A
XML
eXtensible Mark-up Language

Definitions

Terminology
Description
BSWMDT File
This file contains Common Published Information of WDG driver.
ECU Configuration Description
Input file to WDG 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

Introduction Chapter 1

Chapter 1
Introduction

The Watchdog Driver provides services for initialization, changing the
operation mode and triggering the Watchdog.

The WDG Driver module comprises of two sections as Embedded Software
and the Generation Tool to achieve scalability and configurability.

The document describes the features of the WDG Driver Generation Tool.
WDG Driver Generation Tool is a command line tool that extracts information
from ECU Configuration Description File and BSWMDT File and generates
WDG Driver C Source and C Header files (Wdg_59_DriverA_Cfg.h,
Wdg_59_DriverA_PBcfg.c and Wdg_59_DriverA_Cbk.h).

This document contains information on the options, input and output files of the
WDG Driver Generation Tool. In addition, this manual covers a step-by-step
procedure for the usage of tool. ECU Configuration Description File contains
information about WDG configuration.

Remark Based on the value for the parameter ‘VendorApiInfix’, WDG Generation Tool
generates Wdg_59_DriverA_Cfg.h, Wdg_59_DriverA_PBcfg.c and
Wdg_59_DriverA_Cbk.h files. Hence in this document
‘Wdg_59_DriverA_Cfg.h, Wdg_59 _DriverA_PBcfg.c and
Wdg_59_DriverA_Cbk.h’ terms are used.

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 (WDG Driver
Provides the WDG 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 WDG 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 WDG 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 create this document:

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

AUTOSAR_SWS_WatchdogDriver.pdf
2.
P1x Parameter Definition File
1.0.5
R403_WDG_P1M_04_05_10_to_15_18_to_23.arxml

2.2
Trademark Notice

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

11

Chapter 2
Reference

12

WDG Driver Generation Tool Overview
Chapter 3

Chapter 3
WDG Driver Generation Tool Overview

WDG Driver Generation Tool overview is shown below.

ECU

Configuration

Wdg_59_DriverA_
Description File,
WDG Driver
Cfg.h,
BSWMDT File,
Generation
Wdg_59_DriverA_
Translation XML
Tool
PBcfg.c
File and
and
Configuration
Wdg_59_DriverA_
XML File
Cbk.h

Figure 3-1  Overview of WDG Driver Generation Tool

WDG 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 WDG Driver module. It
accepts ECU Configuration Description File(s), BSWMDT File, Translation
XML File and Configuration XML File as input and displays appropriate
context sensitive error messages for wrong input and exits. Tool creates the
Log file (Wdg.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:
Wdg_59_DriverA_Cfg.h, Wdg_59_DriverA_PBcfg.c and
Wdg_59_DriverA_Cbk.h

Wdg_59_DriverA_Cfg.h and Wdg_59_DriverA_Cbk.h will be compiled
and linked with WDG Driver Component. Wdg_59_DriverA_PBcfg.c will
be compiled and linked separately from the other C Source files and
placed in flash.

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

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

13

Chapter 3 WDG Driver Generation Tool Overview

14

Input Files
Chapter 4

Chapter 4
Input Files

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

15

Chapter 4 Input Files

16

Output Files
Chapter 5

Chapter 5
Output Files

WDG Driver Generation Tool generates configuration details in C Header and
C Source files (Wdg_59_DriverA_Cfg.h, Wdg_59_DriverA_PBcfg.c and
Wdg_59_DriverA_Cbk.h).

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

Table 5-1 Output Files Description

Output File
Details
Wdg_59_DriverA_
This file contains pre-compile time parameters. This file also contains the macro
Cfg.h
definitions for development error detect, version info API, compile switch to allow/
forbid disabling Watchdog Driver during runtime and Watchdog Driver Id. This file also
contains information for maximum Watchdog Timer timeout, Minimum Watchdog
Timer timeout, configuration set handles, resolution of Watchdog time out period and
Watchdog trigger mode.
Wdg_59_DriverA_
This file contains post-build configuration data.
PBcfg.c
Wdg_59_DriverA_
This file contains Prototype Declarations for WDG callback Notification Functions.
Cbk.h

Remark Output files generated by WDG 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 WDG Driver, MCU Driver and DEM component
related configuration.

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

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

•  If Translation XML File is not provided on the command line, Wdg_X1x.trxml
which is present in same location of Wdg_X1x.dll is considered as ‘default’
Translation XML File.

•  If Configuration XML File is not provided on the command line,
Wdg_X1x.cfgxml which is present in same location of Wdg_X1x.dll 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 WDG 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.

•  C Source and C Header files will be generated by the Watchdog Driver
Generation Tool based on the configuration of the parameters ‘VENDOR-
ID’ and ‘VENDOR-API-INFIX’ in the WDG Driver specific BSWMDT File.

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

•  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 WDG 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 WDG  Driver Generation Tool. It
ensures conformance of input files 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 validation, refer Chapter 8 “Messages”.

The Generation Tool displays errors 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>: 102 - WDG Driver Module Id (102) 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

ERR102001: 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.

ERR102002: 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.

ERR102003: 'WDG Driver' Component is not present in the input file(s).

This error occurs, if WDG Driver Component is not present in the input ECU
Configuration Description File(s).

ERR102004: 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:

Table 8-1  Parameters and Container related to error ERR102004

Parameter Name
Container Name
WdgDevErrorDetect

WdgDisableAllowed

WdgIndex

WdgVersionInfoApi
WdgGeneral

WdgVaryingActivationCodeMode

WdgTriggerLocation

WdgDeviceName

WdgInitialTimeout

WdgRunArea

23

Chapter 8
Messages

Parameter Name
Container Name
WdgMaxTimeout

WdgCriticalSectionProtection

WdgVersionCheckExternalModules

WdgClockRef
WdgWriteVerify
WdgUseWriteVerifyErrorInterface
WdgInterruptConsistencyCheck
WdgTriggerMode
WdgPublishedInformation
WdgClkSettingsFast
WdgSettingsFast
WdgClkSettingsSlow
WdgSettingsSlow
-
WdgSettingsOff
WdgDefaultMode
WdgSettingsConfig

ERR102005: The reference path <path> provided for the parameter
‘Parameter Name’ within the container ‘Container Name’ is incorrect.

This error occurs, if path provided for the reference parameters mentioned in
the below table are incorrect:

Table 8-2  Parameters and Container related to error ERR102005

Parameter Name
Container Name
WdgClockRef
WdgGeneral
WDG_E_DISABLE_REJECTED
WdgDemEventParameterRefs
WDG_E_MODE_FAILED
WDG_E_REG_WRITE_VERIFY
WDG_E_INT_INCONSISTENT

ERR102006: The value configured for the parameter
‘WdgClkSettingsFast’ in the container ‘WdgSettingsFast’ and value of
the parameter ‘WdgClkSettingsSlow’ in the container ‘WdgSettingsSlow’
are same.

This error occurs, if the value configured for the parameter
WdgClkSettingsFast in the container WdgSettingsFast and value of the
parameter WdgClkSettingsSlow in the container WdgSettingsSlow are same.

ERR102007: The value configured for the parameter
‘WdgClkSettingsSlow’ in the container ‘WdgSettingsSlow’ is faster
(valid configuration should be WdgClkSettingsSlow > WdgSettingsFast)
than the value of the parameter ‘WdgClkSettingsFast’ in the container
‘WdgSettingsFast’.

This error occurs, if the value configured for the parameter
WdgClkSettingsSlow in the container WdgSettingsSlow is faster than the
value of the parameter WdgClkSettingsFast in the container
WdgSettingsFast.

ERR102008: The value of the parameter ‘WdgInitialTimeout’ is greater
than the value of the parameter ‘WdgMaxTimeout’.

24

Messages
Chapter 8

This error occurs, if the value of the parameter WdgInitialTimeout is greater
than the value of the parameter WdgMaxTimeout.

ERR102010: The total instances of ‘WdgSettingsConfig’ container per
WDTA instance is more than <1>.

This error occurs, if the total instance of WdgSettingsConfig container per
WDTA instance is more than 1.

ERR102011: The macro definition <Macro name> is not found in
<Translation Header File name> translation C Header File. The macro
label format should be 'Macro format'.

This error occurs, if the macro definitions “RENESAS_ICWDTA<WDG
instance>NMI_IMR” and “RENESAS_ICWDTA<WDG instance>_IMR” are not
present in Translation Header File.

ERR102012:  "DriverA"  WDG  instance  is  not  present  in  input  BSWMDT
File.  "VENDOR-API-INFIX"  tag  in  WDG  specific  BSWMDT  File  should
contain DriverA".

This error occurs, if “DriverA” WDG instance is not present in BSWMDT file.


ERR102014:  The  reference  to  BSWMDT  file  'MODULE-DESCRIPTION-
REF' should not refer to the same 'VendorApiInfix' for two different WDG
drivers. 'VendorApiInfix' should be unique for each hardware driver.

This error occurs, if the value of ‘VendorApiInfix’ is not unique for each
hardware driver.

ERR102015: The value configured for the parameter 'WdgIndex' is same
for  all  the  configured  WDG  drivers.  The  value  of  WdgIndex  should  be
unique for each hardware driver.

This error occurs, if the value configured for the parameter WdgIndex is same
for all the configured WDG drivers.

ERR102016: The short name of the container ‘WdgSettingsConfig’
should be unique across the Drivers.

This  error  occurs,  if  the  short  name  of WdgSettingsConfig  container  is  not
same across the Drivers.

ERR102018:  The  minimum  and  maximum  values  for  slow_time_value
should be 0 and 196.608.

This error will occur, if the slow_time_value is less than 0 or exceeds 196.608.

ERR102019:  The  minimum  and  maximum  values  for  fast_time_value
should be 0 and 196.608.

This error will occur, if the fast_time_value is less than 0 or exceeds 196.608.

ERR102020:  The  parameter  'WDG_E_REG_WRITE_VERIFY'  in  the

25

Chapter 8
Messages

container  '  WdgDemEventParameterRefs’  should  be  configured  since
parameter 'WdgWriteVerify'in container 'WdgGeneral' is not configured
as 'WV_DISABLE'.

This  error  will  occur,  if  parameter  'WDG_E_REG_WRITE_VERIFY'  is  not
configured while parameter 'WdgWriteVerify' is configured other than
'WV_DISABLE'.

ERR102021:  WdgWriteVerifyErrorInterface  parameter  should  have  a
value  when  the  parameter  WdgUseWriteVerifyErrorInterface  is
configured as true.

This error will occur, if WdgUseWriteVerifyErrorInterface is configured as true
and WdgWriteVerifyErrorInterface parameter is set as NULL.

ERR102022:  The  parameter  'WDG_E_INT_INCONSISTENT'  in  the
container  '  WdgDemEventParameterRefs’  should  be  configured  since
the
parameter
'WdgInterruptConsistencyCheck'
in
container
'WdgGeneral' is configured as true.

This error will occur, if the parameter 'WDG_E_INT_INCONSISTENT' is not
configured  while  parameter  'WdgInterruptConsistencyCheck'  in  container
'WdgGeneral' is configured as true.

8.2  Warning Messages

WRN102001: The value of the parameter 'WdgInitialTimeout' is
configured as <0> and 'WdgDefaultMode' is not configured as
<WDGIF_OFF_MODE>. Hence, Watchdog hardware will be enabled
directly after Wdg Module initialization and WDG counter will expire
after <calculated_value in msec>.

This warning occurs, if WdgInitialTimeout parameter is configured as 0 and
WdgDefaultMode is not configured as WDGIF_OFF_MODE.

WRN102002: The window open period when a WDTA trigger is
valid is not set to 25%.

This warning occurs if the generated value for WDG Mode register has Window
open period set other than 25%.

8.3  Information Messages

INF102001: The duration of 75% of one WDG trigger cycle for slow mode
is <slow_time_value msec>.

This information occurs to provide 75% interrupt time for slow mode. In this
information message ‘slow_time_value’ will be evaluated as follows:

slow_value = Power factor from WdgClkSettingsSlow
slow_time_value =  ((0.75 * (2 ** $slow_value / $clock)) * 1000)

26

Messages
Chapter 8

INF102002: The duration of 75% of one WDG trigger cycle for fast mode
is <fast_time_value msec>.

This information occurs to provide 75% interrupt time for fast mode. In this
information message ‘fast_time_value’ will be evaluated as follows:

fast_value = Power factor from WdgClkSettings
Fast fast_time_value = ((0.75 * (2 ** $fast_value / $clock)) * 1000)

INF102003: WdgUseWriteVerifyErrorInterface functionality has no effect
when WdgWriteVerify parameter is DISABLED.

This information occurs if WdgWriteVerify parameter is DISABLED and
WdgUseWriteVerifyErrorInterface is configured TRUE.

INF102004: Reference path is not provided for the parameter <dem
parameter> and hence error shall not be reported.

This information occurs if either of WDG_E_DISABLE_REJECTED
or WDG_E_MODE_FAILED parameter is not provided reference path.

27

Chapter 8
Messages

28

  Notes


  Chapter 9

Chapter 9
Notes

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

29

Chapter 9

Notes

30

Revision History

Sl.No.  Description
Version
Date
1.
Initial Version
1.0.0
18-Oct-2013
2.
Following changes are made:
1.0.1
26-Sep-2014
1. Chapter 2 is updated for addition of PDF reference.
2. WdgRegReadBackEnable parameter is added in ERR102004 error
message table.
3. A note is added for ERR102012 error message.
4. WdgDemEventParameterRefs container and its parameters are added in
the table of error message ERR102005.
5. Error message ERR102017 is added newly.
6. Error messages ERR102015 and ERR102016 are rephrased.
7. Chapter 6 Precautions is updated.
3.
Following change is made:
1.0.2
28-Apr-2015
1. Updated Chapter 2 to add PDF reference.
4.
Following change is made:
1.0.3
29-Mar-2016
1.Updated Chapter 8.1 to add error messages ERR102018 and
ERR102019
2. Added R-Number.
5.
Following changes are made:
1.0.4
13-Jul-2016
1. Chapters 1,3 and 5 are updated to add new output file
Wdg_59_DriverA_Cbk.h
2. Updated Chapter 8.1, error message ERR102005 for new Dem
parameters and removed ERR102009.
3. ERR102004 is updated to add new parameters under container
WdgGeneral.
4. ERR102012 error message is updated, ERR102017 is deleted as
READBACK feature is no longer supported.
5. Added new error IDs ERR102020, ERR102021 and ERR102022.
6. Chapter 8.3 is updated to add information messages INF102003 and
INF102004.
7. Updated Chapter 2 to add PDF version.

6.
Following changes are made:
1.0.5
21-Oct-2016
1. Section 8.2 is updated to add new warning message WRN102002.
2. Table headers adder for Table 8.1 and Table 8.2
7
Following changes are made:
1.0.6
15-Feb-2017
1. Abbreviation list is updated.
2.Chapter 3 and 9 are updated with R-Numbered Tool
  User manual name.
3. Version of R-number is updated at the end of document.
4. Notice and copyright information is updated.
5. R403_WDG_P1M_04_05_10_to_15_18_to_23.arxml version is updated.

31

AUTOSAR MCAL R4.0.3 User's Manual
WDG Driver Component Ver.1.0.6
Generation Tool User's Manual

Publication Date: Rev.1.01, February 15, 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

R20UT3729EJ0101

Document Outline

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