AUTOSAR_FLS_Tool_UserManuals

AUTOSAR MCAL R4.0.3
User‟s Manual

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

Abbreviations and Acronyms

Abbreviation / Acronym
Description
AUTOSAR
AUTomotive Open System ARchitecture
BSWMDT
Basic Software Module Description Template
DEM/Dem
Diagnostic Event Manager
ECU
Electronic Control Unit
FLS
FLash Driver
id
Identifier
MCAL
Microcontroller Abstraction Layer
MCU
MicroController Unit
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 FLS 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 FLS Driver Generation Tool ....................................................................... 13

List of Tables

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

8

Introduction Chapter 1

Chapter 1
Introduction

The FLS Software component provides the service for initializing the whole
FLS structure of the microcontroller.

The FLS Software Component comprises of two sections as Embedded
Software and the Generation Tool to achieve scalability and configurability.

The document describes the features of the FLS Software Generation Tool.
FLS Software Generation Tool is a command line tool that extracts
information from ECU Configuration Description File and generates FLS
Software C Header files and Source Files (Fls_Cbk.h, Fls_Cfg.h, fcl_cfg.h,
fdl_descriptor.h, fcl_descriptor.h and Fls_PBcfg.c).

This document contains information on the options, input and output files of
the FLS Software Generation Tool. In addition, this manual covers a step-
by-step procedure for the usage of tool.

ECU Configuration Description File contains information about FLS
configuration.

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 (FLS Driver
Provides the component overview of FLS Driver.
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 FLS 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 FLS 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.
Specification of Flash Driver for R4.0.3
3.2.0
AUTOSAR_SWS_FlashDriver.pdf

2.
P1x Parameter Definition File
1.1.1

R403_FLS_P1M_04_05.arxml
3.
P1x Parameter Definition File
1.1.1
R403_FLS_P1M_10_to_15.arxml
4.
P1x Parameter Definition File
1.0.1
R403_FLS_P1M_18_to_23.arxml

2.2
Trademark Notice

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

11

Chapter 2
Reference

12

FLS Driver Generation Tool Overview
Chapter 3

Chapter 3
FLS Driver Generation Tool Overview

FLS Driver Generation Tool overview is shown
below.

ECU

Configuration

Fls_Cbk.h,
Description
FLS Driver
Fls_Cfg.h,
File, BSWMDT
fcl_cfg.h,
File, Translation
Generation
fdl_descriptor.h,
XML File and
Tool
fcl_descriptor.h
Configuration
Fls_PBcfg.c
XML File

Figure 3-1 Overview of FLS Driver Generation Tool

FLS 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 FLS 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 Fls.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:

If FLS Driver is configured for Data Flash then generation tool will generate
Fls_Cfg.h, Fls_Cbk.h, Fls_PBcfg.c and fdl_descriptor.h files.

If FLS Driver is configured for Code Flash then generation tool will generate
Fls_Cfg.h, Fls_Cbk.h, Fls_PBcfg.c, fcl_Cfg.h and fcl_descriptor.h files.

Fls_Cfg.h, Fls_Cbk.h, fcl_cfg.h, fdl_descriptor.h, fcl_descriptor.h will be
compiled and linked with FLS Driver Component. Fls_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.

13

Chapter 3                                                                                 FLS Driver Generation Tool Overview

Remark

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

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

14

Input Files
Chapter 4

Chapter 4 Input Files

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

FLS Driver Generation Tool generates configuration details in C Header and C
Source  files  (Fls_Cbk.h,  Fls_Cfg.h,  fcl_cfg.h,  fdl_descriptor.h,  fcl_descriptor.h,
Fls_PBcfg.c ).

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

Table 5-1  Output Files Description

Output File
Details
Fls_Cbk.h
This file contains call-back functions prototype declarations.
Fls_Cfg.h
This file contains pre-compile time parameters.
Fls_PBcfg.c
This file contains post-build time parameters.
fdl_descriptor.h
This file contains FDL run-time configuration descriptor variable related defines. This
file will be generated, if the FLS configured as Data Flash.
fcl_cfg.h
This file contains pre-compile time parameters related to FCL Library. This file will
be generated, if the FLS configured as Code Flash.
fcl_descriptor.h
This file pre-compile time parameters related to FCL descriptor. This file will be
generated, if the FLS configured as Code Flash.

Remark  Output files generated by FLS 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 FLS Driver module.

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

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

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

•
If Configuration XML File is not provided on the command line,
Fls_X1x.cfgxml which is present in same location of Fls_X1x.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 FLS 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 FLS 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 FLS 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 FLS 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>: 092- FLS Driver Module id (092) 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

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

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

ERR092003: 'FLS Driver / MCU Driver' Component is not present in the
input file(s).

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

ERR092004: 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
FlsCancelApi

FlsCompareApi

FlsDevErrorDetect

FlsGetJobResultApi
FlsGeneral

FlsGetStatusApi

FlsSetModeApi

FlsVersionInfoApi

FlsVersionCheckExternalModules

FlsCriticalSectionProtection

FlsDeviceName

FlsAccess

23

Chapter 8
Messages
Parameter Name
Container Name
FlsVirtualBoundaryAddress

FlsTimeoutMonitoring
FlsGeneral
FlsGeneral
FlsUseInterrupts

FlsEraseTime

FlsReadTime

FlsPublishedInformation
FlsWriteTime
FlsCancelTime
FlsErasedValue
FlsBlankCheckTime
FlsSuspendTime
FlsCallCycle

FlsMaxReadNormalMode
FlsConfigSet
FlsMaxWriteNormalMode
FlsMaxEraseNormalMode
FlsSectorIndex

FlsSectorOption

FlsNumberOfSectors
FlsSector
FlsPageSize
FlsSectorSize
FlsSectorStartaddress
FlsBlankCheck

FlsDFBaseAddress

FlsDFBlockSize

FlsDFTotalBlocks

FlsDFTotalSize
FlsDataFlash
FlsFdlCpuFrequency
FlsBlankCheckApi
FlsReadImmediateApi
FlsSuspendApi
FlsResumeApi
FlsCFTotalSize

FlsCFSmallBlockBaseAddress

FlsCFNormalBlockBaseAddress

FlsCFSmallBlockSize

FlsCFNormalBlockSize

FlsCFTotalSmallBlocks

FlsCFTotalNormalBlocks

FlsCodeFlash
FlsFclRamAddress
FlsCommandExecutionMode
FlsFclCpuFrequency
FlsCFEraseTime
FlsCFWriteTime
FlsCFCancelTime
FlsMaxCFReadNormalMode
FlsMaxCFWriteNormalMode
FlsMaxCFEraseNormalMode
FlsCFReadTime
24

      Messages
    Chapter 8

Parameter Name
Container Name
FLS_E_READ_FAILED

FLS_E_WRITE_FAILED

FLS_E_READ_FAILED_DED
FlsDemEventParameterRefs
FLS_E_ERASE_FAILED

FLS_E_COMPARE_FAILED

Remark

               •    The container FlsCodeFlash its parameters are mandatory only when the
                 parameter FlsAccess is configured as FLS_CODEFLASH_ACCESS.

             •   The container FlsDataFlash its parameters are mandatory only when the
                 parameter FlsAccess is configured as FLS_DATAFLASH_ACCESS.

                   ERR092007: The value configured for the parameter 'parameter name'
                   should follow C syntax <[a-zA-Z][a-zA-Z0-9_]>.

This error occurs, if the value of configuration parameters mentioned in below
table does not adhere to C syntax as if the value contains characters other
than (a-z, A-Z, 0-9 or “_”). The parameter value should always start with an
alphabet.

Parameter Name
Container Name
FlsJobEndNotification
FlsConfigSet
FlsJobErrorNotification
FlsEccSedNotification
FlsDataFlash
FlsEccDedNotification

ERR092012: The reference path <reference value> provided for the
parameter 'parameter name’ within the container
'FlsDemEventParameterRefs' is incorrect.

This  error  occurs,  if  the  reference  path  <reference  value>  provided  for  the
following  parameters  within  the  container  'FlsDemEventParameterRefs'  is
incorrect.

Parameter Name
Container Name
FLS_E_COMPARE_FAILED

FLS_E_ERASE_FAILED
FlsDemEventParameterRefs
FLS_E_READ_FAILED
FLS_E_WRITE_FAILED
FLS_E_READ_FAILED_DED

ERR092014: The value configured for the parameter 'parameter name’ in
the container 'FlsSector' should be unique within an 'FlsConfigSet.

This error occurs, if the value configured for the following parameters in the
container FlsSector is not unique within an FlsConfigSet.

Parameter Name
Container Name

25

      Chapter 8
   Messages
FlsSectorIndex
FlsSector
FlsSectorOption

ERR092015: The value configured for the parameter ‘parameter name’ in
the container ‘FlsSector' should be <actual value>, since the sector is
configured as <value of FlsSectorOption>.

This error occurs, if the value configured for the following parameters in the
container FlsSector is not as per below table.

FlsSectorOption
FlsNumberOfSector
FlsSectorSize
FLS_DF_SECTOR
512
64
FLS_CF_SMALL_BLK_SECTOR
8
8192

FLS_CF_NORMAL_BLK_SECTOR
14
32768

ERR092017: The value configured for the parameter ‘parameter name' in
the container 'container name' should be same for the FlsSectorIndex
<value of FlsSectorIndex> across the multiple configuration set of
'FlsConfigSet'.

This  error  occurs,  if  the  value  configured  for  the  following  parameters  in  the
respective  container  is  not  same  for  the  FlsSectorIndex  across  the  multiple
configuration set of FlsConfigSet.

Parameter Name
Container Name
FlsSectorOption

FlsSector
FlsSectorSize
FlsNumberOfSectors
FlsSectorStartaddress

ERR092018: The values configured for the parameters
'FlsEccSedNotification' and 'FlsEccDedNotification' in the container
'FlsDataFlash' and the values configured for the parameters
'FlsJobEndNotification' and 'FlsJobErrorNotification' in any of the
'FlsConfigSet' container should be unique.

This error occurs, if the values configured for the parameters
'FlsEccSedNotification' and 'FlsEccDedNotification' in the container
'FlsDataFlash' and the values configured for the parameters
'FlsJobEndNotification' and 'FlsJobErrorNotification' in any of the
'FlsConfigSet' container is not unique. For example, the following table shows
the conditions when the error message occurs.

Container : FlsDataFlash
Container : FlsConfigSet
FlsEccSedNotification  FlsEccDedNotification  FlsJobEndNotification  FlsJobErrorNotification
EccSedNotification
EccSedNotification
EccSedNotification
EccSedNotification
26

      Messages
    Chapter 8

EccSedNotification
EccSedNotification
-
-
-
-
EccSedNotification
EccSedNotification
-
EccSedNotification
-
EccSedNotification

ERR092019: The value configured for the parameter 'parameter name' in
the container ‘FlsDemEventParameterRefs' should be same across the
multiple configuration set of 'FlsConfigSet'.

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

Parameter Name
Container Name
FLS_E_COMPARE_FAILED

FLS_E_ERASE_FAILED

FLS_E_READ_FAILED
FlsDemEventParameterRefs

FLS_E_WRITE_FAILED

ERR092020: The value configured for the parameter ‘FlsSectorIndex' in
the container ‘FlsSector' should be same across the multiple
configuration set of 'FlsConfigSet'.

This error occurs, if the value configured for the parameter FlsSectorIndex in
the container FlsSector is not same across the multiple configuration set of
FlsConfigSet.

ERR092021: The sub-container ‘FlsDataFlash' and its parameters should be
configured in ‘FlsGeneral' container, since the parameter 'FlsAccess' in
'FlsGeneral' container is configured as <FLS_DATAFLASH_ACCESS>.

This error occurs, if the sub-container FlsDataFlash and its parameters is not
configured in FlsGeneral container and the parameter FlsAccess in FlsGeneral
container is configured as FLS_DATAFLASH_ACCESS.

ERR092022:  The  sub-container  ‘FlsCodeFlash'  and  its  parameters  should
be configured in ‘FlsGeneral' container, since the parameter 'FlsAccess' in
'FlsGeneral' container is configured as <FLS_CODEFLASH_ACCESS>.

This  error  occurs,  if  the  sub-container  FlsCodeFlash  and  its  parameters  is  not
configured  in  FlsGeneral  container  and  the  parameter  FlsAccess  in  FlsGeneral
container is configured as FLS_CODEFLASH_ACCESS.

ERR092023: The reference path of MCU <configured value of
FlsFdlCpuFrequency> provided for the parameter ‘FlsFdlCpuFrequency’ in
the container 'FlsDataFlash' is incorrect.

This error occurs, if the reference path of MCU provided for the parameter
FlsFdlCpuFrequency in the container FlsDataFlash is incorrect.

ERR092024: The 'FlsSector' container should be configured with
parameter ‘FlsSectorOption' as 'FLS_DF_SECTOR', since the parameter
'FlsAccess' in 'FlsGeneral' container is configured as

27

      Chapter 8
   Messages
<FLS_DATAFLASH_ACCESS>.

This error occurs, if the FlsSector container is not configured with parameter
FlsSectorOption as FLS_DF_SECTOR and the parameter Flacks in
FlsGeneral container is configured as FLS_DATAFLASH_ACCESS.

ERR092025: The 'FlsSector' container should be configured with
parameter ‘FlsSectorOption' as ‘FLS_CF_NORMAL_BLK_SECTOR',
since the parameter 'FlsAccess' in 'FlsGeneral' container is configured
as <FLS_CODEFLASH_ACCESS>.

This error occurs, if the FlsSector container is not configured with parameter
FlsSectorOption as FLS_CF_NORMAL_BLK_SECTOR and the parameter
FlsAccess in FlsGeneral container is configured as
FLS_CODEFLASH_ACCESS.

ERR092026: The 'FlsSector' container should be configured with
parameter ‘FlsSectorOption' as ‘FLS_CF_SMALL_BLK_SECTOR', since
the parameter 'FlsAccess' in 'FlsGeneral' container is configured as
<FLS_CODEFLASH_ACCESS>.

This error occurs, if the FlsSector container is not configured with parameter
FlsSectorOption as FLS_CF_SMALL_BLK_SECTOR and the parameter
FlsAccess in FlsGeneral container is configured as
FLS_CODEFLASH_ACCESS.

ERR092028: The value configured for the parameter
'FlsSectorStartaddress' should be within the range of <range of value> for
the <configured value of FlsSectorOption>.

This error occurs, if the value configured for the parameter
FlsSectorStartaddress is not within the below range.

FlsSectorOption
Range of value for FlsSectorStartaddress

0

FLS_DF_SECTOR
to

(value configured for FlsVirtualBoundaryAddress - 1)

(value configured for FlsVirtualBoundaryAddress)
FLS_CF_SMALL_BLK_SECTOR

to

(value configured for FlsVirtualBoundaryAddress +
value configured for FlsCFSmallBlockSize)

(value configured for FlsVirtualBoundaryAddress + value
FLS_CF_NORMAL_BLK_SECTOR
configured for FlsCFSmallBlockSize + 1)

to

(value configured for FlsVirtualBoundaryAddress + value
configured for FlsCFTotalSize)

ERR092029: The value configured for the parameter 'FlsTotalSize' should be
(FlsNumberOfSectors * FlsSectorSize) since the parameter 'FlsAccess' in
28

      Messages
    Chapter 8

'FlsGeneral' container is configured as <FLS_DATAFLASH_ACCESS>.

This error occurs, if the FlsGeneral container is not configured with parameter
FlsTotalSize as FlsDFTotalSize and the parameter FlsAccess in FlsGeneral
container is configured as FlsDataFlash.

ERR092030: The ‘FlsGeneral’ container should be configured with
parameter ‘'FlsTotalSize'' as ‘FlsCFTotalSize', since the parameter
'FlsAccess' in 'FlsGeneral' container is configured as <FlsCodeFlash>.

This error occurs, if the FlsGeneral container is not configured with parameter
FlsTotalSize as FlsCFTotalSize and the parameter FlsAccess in FlsGeneral
container is configured as FlsCodeFlash.

ERR092031: The ‘FlsGeneral’ container should be configured with
parameter ‘'FlsTotalSize'' as sum of ‘FlsCFTotalSize' and ‘ FlsDFTotalSize’ ,
since the parameter 'FlsAccess' in 'FlsGeneral' container is configured as
<FLS_DATA_CODE_FLASH_ACCESS >.
This error occurs, if the FlsGeneral container is not configured with parameter
FlsTotalSize as sum of FlsDFTotalSize and FlsCFTotalSize and the parameter
FlsAccess in FlsGeneral container is configured as
FLS_DATA_CODE_FLASH_ACCESS.

8.2  Warning Messages
                                              None

8.3  Information Messages

INF092001: The parameter 'parameter name' in the container
‘FlsConfigSet' is not configured.

This information occurs, if the parameters FlsJobEndNotification or
FlsJobErrorNotification in the container FlsConfigSet are not configured.

INF092002: The sub-container ‘FlsCodeFlash' and its parameters in
'FlsGeneral' container are not considered for the implementation, since
the parameter 'FlsAccess' in the ‘FlsGeneral' container is configured as
<FLS_DATAFLASH_ACCESS>.

This information occurs, if the sub-container FlsCodeFlash and its parameters
in FlsGeneral container are configured and the parameter FlsAccess in the
FlsGeneral container is configured as FLS_DATAFLASH_ACCESS.

INF092003: The sub-container ‘FlsDataFlash' and its parameters in
'FlsGeneral' container are not considered for the implementation, since
the parameter 'FlsAccess' in the ‘FlsGeneral' container is configured as
<FLS_CODEFLASH_ACCESS>.

This information occurs, if the sub-container FlsDataFlash and its parameters in
FlsGeneral container are configured and the parameter FlsAccess in the
FlsGeneral container is configured as FLS_CODEFLASH_ACCESS.

29

      Chapter 8
   Messages

INF092004: The container ‘FlsSector' having the short name <short name
of FlsSector container> and its parameters are not considered for the
implementation, since the parameter ‘FlsSectorOption' for this sector is
configured as <configured value of FlsSectorOption> and the parameter
'FlsAccess ' in the ‘FlsGeneral ' container is configured as
<FLS_DATAFLASH_ACCESS>.

This information occurs, if the container FlsSector with the parameter
FlsSectorOption is configured as FLS_CF_SMALL_BLK_SECTOR or
FLS_CF_NORMAL_BLK_SECTOR and the parameter FlsAccess in the
FlsGeneral container is configured as FLS_DATAFLASH_ACCESS.

INF092005: The container ‘FlsSector' having the short name <short name
of FlsSector container> and its parameters are not considered for the
implementation, since the parameter ‘FlsSectorOption' for this sector is
configured as <FLS_DF_SECTOR> and the parameter 'FlsAccess ' in the
‘FlsGeneral ' container is configured as <FLS_CODEFLASH_ACCESS>.

This information occurs, if the container FlsSector with the parameter
FlsSectorOption for this container is configured as FLS_DF_SECTOR and
the parameter FlsAccess in the FlsGeneral container is configured as
FLS_CODEFLASH_ACCESS.
30

Notes
Chapter 9

Chapter 9 Notes

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

31

Chapter 9
Notes

32

Revision History

Sl.No.  Description
Version
Date
1.
Initial Version
1.0.0
29-Oct-2013
2.
Following changes are made:
1.0.1
28-Jan-2014
•
Error messages ERR092010, ERR092018, ERR092029,
ERR092030 and ERR092031 are added.
•
Error message ERR092007is updated.

3.
Following changes are made:
1.0.2
2-Sep-2014
•
FlsUseInterrupts parameter is added in FlsGeneral container
in error message ERR092004 in section 8.1. Error Messages.

•
FlsSuspendTime parameter is added in
FlsPublishedInformation container in error message
ERR092004 in section 8.1.1. Error Messages.

•
FlsBlankCheckApi, FlsReadImmediateApi, FlsSuspendApi
and FlsResumeApi parameters are added in FlsDataFlash
container in error message ERR092004 in section 8.1.1.
Error Messages.

•
Error messages ERR092008, ERR092009 and ERR092010
are deleted and error message ERR092018 is updated in
section 8.1 Error Messages.
4
The following changes are made:
1.0.3
24-Apr-2015
•
Pdf name and version are updated in  Section 2.1
•
Added parameters FlsCancelTime and FlsCFCancelTime in
the list of mandatory parameters in Section 8.1.
•
The description of error ERR092029 is updated in Section
8.1.
•
Updated version number and copyright year.

33

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

Publication Date: Rev.0.01, April 24, 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)