R20UT3727EJ0101-AUTOSARs
AUTOSAR MCAL R4.0.3
User’s Manual
SPI Driver Component Ver.1.0.12
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
2
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
4
Abbreviations and Acronyms
Abbreviation / Acronym
Description
AUTOSAR
AUTomotive Open System ARchitecture
BSWMDT
Basic Software Module Description Template
CSIH
Enhanced Queued Clocked Serial Interface.
DEM
Diagnostic Event Manager
EB
External Buffer
ECU
Electronic Control Unit
e.g
Example
Hz
Hertz
HW
Hardware
IB
Internal Buffer
Id
Identifier
MCAL
MicroController Abstraction Layer
MCU
Micro Controller Unit
PCLK
Peripheral Clock
Rx
Receive
SPI
Serial Peripheral Interface
Tx
Transmit
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 SPI 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
6
Table of Contents
Chapter 1
Introduction ...................................................................................... 9
1.1
Document Overview .......................................................................................................... 9
Chapter 2
Reference ....................................................................................... 11
2.1
Reference Documents ..................................................................................................... 11
2.2
Trademark Notice ............................................................................................................ 11
Chapter 3
SPI Driver Generation Tool Overview ........................................... 13
Chapter 4
Input Files ....................................................................................... 15
Chapter 5
Output Files .................................................................................... 17
Chapter 6
Precautions .................................................................................... 19
Chapter 7
User Configuration Validation ...................................................... 21
Chapter 8
Messages........................................................................................ 23
8.1
Error Messages ................................................................................................................ 23
8.2
Warning Messages .......................................................................................................... 41
8.3
Information Messages ..................................................................................................... 43
Chapter 9
Notes ............................................................................................... 47
7
List of Figures
Figure 3-1
Overview of SPI Driver Generation Tool .................................................................... 13
List of Tables
Table 5-1
Output Files Description ....................................................................................................... 17
Table 8-1
Parameters and Containers related to ERR083004 ................................................................... 23
Table 8-2
Parameters and Containers related to ERR083024 ................................................................... 28
Table 8-3
Parameters and Containers related to ERR083084 ................................................................... 36
Table 8-4
Parameters and Containers related to ERR083085 ................................................................... 37
Table 8-5
Parameters and Containers related to ERR083091 ................................................................... 38
Table 8-6 Parameter values related to INF083003 ................................................................................. 44
8
Introduction
Chapter 1
Chapter 1 Introduction
The SPI Driver component provides the service for initializing the whole SPI
structure of the microcontroller.
The SPI Driver Component comprises of two sections as Embedded Software
and the Generation Tool to achieve scalability and configurability.
The document describes the features of the SPI Driver Generation Tool. SPI
Driver Generation Tool is a command line tool that extracts information from
ECU Configuration Description File and generates SPI Driver C Source and C
Header files (Spi_Cfg.h, Spi_Cbk.h, Spi_PBcfg.c and Spi_Lcfg.c).
This document contains information on the options, input and output files of
the SPI 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 SPI
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 (SPI Driver
Provides the component overview of SPI 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 SPI 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 SPI 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_SWS_SPIHandlerDriver.pdf
3.2.0
2.
P1M Parameter Definition File
1.0.8
R403_SPI_P1M_04_05_12_13_20_21.arxml
3.
P1M Parameter Definition File
1.0.8
R403_SPI_P1M_10_11_14_15_18_19_22_23.arxml
2.2
Trademark Notice
Microsoft and Windows are trademarks/registered trademarks of Microsoft
Corporation.
11
Chapter 2
Reference
12
SPI Driver Generation Tool Overview
Chapter 3
Chapter 3 SPI Driver Generation Tool Overview
SPI Driver Generation Tool overview is shown below.
ECU
Configuration
Description
Spi_Cfg.h,
File, BSWMDT
SPI Driver
Spi_Cbk.h,
File, Translation
Generation
Spi_Lcfg.c,
XML File and
Tool
Spi_PBcfg.c
Configuration
XML File
Figure 3-1 Overview of SPI Driver Generation Tool
SPI 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 SPI 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 Spi.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:
Spi_Lcfg.c, Spi_PBcfg.c, Spi_Cfg.h and Spi_Cbk.h.
Spi_Cfg.h and Spi_Cbk.h will be compiled and linked with SPI Driver
Component. Spi_Lcfg.c and Spi_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.
• SPI Driver Generation Tool uses “Common Published Information” from SPI
module specific BSWMDT File. SPI module specific BSWMDT File should
not be updated manually since it is ”Static Configuration” file.
13
Chapter 3 SPI Driver Generation Tool Overview
14
Input Files
Chapter 4
Chapter 4 Input Files
SPI Driver Generation Tool accepts ECU Configuration Description File(s),
BSWMDT File, Translation XML File and Configuration XML File as input.
SPI Driver Generation Tool needs information about SPI Driver module.
Hence ECU Configuration Description File should contain configuration of
SPI 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
P1x Parameter Definition File referred in Reference Documents section.
15
Chapter 4 Input Files
16
Output Files
Chapter 5
Chapter 5 Output Files
SPI Driver Generation Tool generates configuration details in C Header and C
Source files (Spi_Lcfg.c, Spi_PBcfg.c, Spi_Cbk.h and Spi_Cfg.h).
The content of each output file is given in the table below:
Table 5-1 Output Files Description
Output File
Details
Spi_Cfg.h
This file contains pre-compile time parameters and handles.
Spi_Cbk.h
This file contains callback function prototype declarations to be used by application.
Spi_PBcfg.c
This file contains post-build time parameters.
Spi_Lcfg.c
This file contains structures of link time parameters.
Remark Output files generated by SPI 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 SPI Driver module.
• Default Translation XML File (Spi_X1x.trxml) should be present in same
location of Spi_X1x.dll when the variant specific trxml file is not given as input
in command line.
• Default Configuration XML File (Spi_X1x.cfgxml) must be present in same
location of Spi_X1x.dll.
• If Translation XML File is not provided on the command line,
Spi_X1x.trxml which is present in same location of Spi_X1x.dll is
considered as ‘default’ Translation XML File.
• If Configuration XML File is not provided on the command line,
Spi_X1x.cfgxml which is present in same location of Spi_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 SPI 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 SPI 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 SPI 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 SPI 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>: 083 - SPI Driver Module Id (083) 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
ERR083001: 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.
ERR083002: 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.
ERR083003: 'SPI Driver/MCU Driver/DEM' Component is not present in
the input file(s).
This error will occur, if SPI Driver or MCU Driver or DEM component is not
present in the input ECU Configuration Description File(s).
ERR083004: 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 Containers related to ERR083004
Parameter Name
Container Name
SpiCancelApi
SpiChannelBuffersAllowed
SpiDevErrorDetect
SpiHwStatusApi
SpiInterruptibleSeqAllowed
SpiGeneral
SpiLevelDelivered
SpiSupportConcurrentSyncTransmit
SpiVersionInfoApi
SpiDmaMode
SpiDataConsistencyCheckEnable
SpiDataWidthSelection
SpiMaxBaudrate
SpiSyncSeqEndNotificationEnable
SpiPersistentHWConfiguration
SpiDmaTypeUsed
SpiHighPriorityHwHandlingEnable
SpiCriticalSectionProtection
23
Chapter 8 Messages
Parameter Name
Container Name
SpiDeviceName
Spi
General
SpiAlreadyInitDetCheck
SpiVersionCheckExternalModules
SpiGeneral
SpiSeqStartNotificationEnable
SpiTimeOut
SpiLoopBackSelfTest
SpiECCSelfTest
SpiInterruptConsistencyCheck
SpiCSIGHWriteVerify
SpiDMAWriteVerify
SpiMaxChannel
SpiMaxJob
SpiDriver
SpiMaxSequence
SpiChannelId
SpiChannelType
SpiDataWidth
SpiChannel
SpiEbMaxLength
SpiIbNBuffers
SpiTransferStart
SpiCsPolarity
SpiDataShiftEdge
SpiShiftClockIdleLevel
SpiCsIdentifier
SpiEnableCs
SpiHwUnit
SpiTimeClk2Cs
SpiExternalDevice
SpiClk2CsCount
SpiBaudrateConfiguration
SpiInputClockSelect
SpiInterruptDelayMode
SpiParitySelection
SpiBroadcastingPriority
SpiClockFrequencyRef
SpiBaudrate
SpiJobId
SpiJob
SpiJobPriority
SpiDeviceAssignment
SpiInterruptibleSequence
SpiSeqStartNotification
SpiSequence
SpiSequenceId
SpiHighPriorityHwSequence
SpiJobAssignment
SpiHwUnitSelection
SpiMemoryMode
SpiMemoryModeSelection
SpiTxDmaChannel
SpiRxDmaChannel
SpiDma
SpiDmaHwUnit
24
Messages Chapter 8
Parameter Name
Container Name
SPI_E_HARDWARE_ERROR
Spi
S G
pi e
D ne
em ral
Ev entParameterRefs
SPI_E_DATA_TX_TIMEOUT_FAILURE
SpiChannelIndex
SpiChannelList
SpiChannelAssignment
SpiMaxHwUnit
SpiPublishedInformation
Remark If the containers SpiMemoryMode and SpiDmaMode are configured, then
the respective parameters which are mandatory should be configured.
ERR083005: In general per configuration set, the value of
'SpiChannelId' should be unique and less than 'SpiMaxChannel' in
'SpiDriver' container
This error occurs, if the value for parameter SpiChannelId present in the
SpiChannel is not unique or not less than the value present in the
SpiMaxChannel.
ERR083006: The value of the parameter 'SpiChannelType' in the
container 'SpiChannel' should be same for SPI Channels (having
same channel Id) across multiple configuration sets.
This error occurs, if the value of parameter SpiChannelType in the
container SpiChannel is not same for SPI Channels (having same
channel Id) across multiple configuration sets.
ERR083007: The number of SPI channels configured should be
same across the multiple configurations set container 'SpiDriver'.
This error occurs, if the number of SPI channels configured is not same
across the multiple configurations set container SpiDriver.
ERR083008: The value of the parameters 'SpiEbMaxLength' and
'SpiIbNBuffers' in the container 'SpiChannel' should be same for
SPI Channels (having same channel Id) across multiple
configuration sets.
This error occurs, if the value for parameters SpiEbMaxLength and
SpiIbNBuffers are not same for all SPI Channels (having same channel
Id) across multiple configuration sets in ECU Configuration Description
File.
ERR083009: The short name of the container 'SpiChannel' should be
same for channel having same 'SpiChannelId' <value for
SpiChannelId> across multiple configurations set container
'SpiDriver'.
This error occurs, if the short name of the container SpiChannel is not
same for channel having same SpiChannelId across multiple
configurations set in the container SpiDriver.
ERR083010: The value of the parameter 'SpiChannelType' in the
container 'SpiChannel' should be configured as <EB>, since the
value of the parameter 'SpiChannelBuffersAllowed' in the container
'SpiGeneral' is configured as <1>.
This error occurs, if SpiChannelBuffersAllowed in the container
25
Chapter 8 Messages
SpiGeneral is configured as 1 and the parameter SpiChannelType in the
container SpiChannel is not configured as EB.
ERR083011: The value of the parameter 'SpiChannelType' in the
container 'SpiChannel' should be configured as <IB>, since the value
of the parameter 'SpiChannelBuffersAllowed' in the container
'SpiGeneral' is configured as <0>.
This error occurs, If SpiChannelBuffersAllowed in the container
SpiGeneral is configured as 0 and the parameter SpiChannelType in the
container SpiChannel is not configured as IB.
ERR083012: The SPI channels configured for a specific job should
not be repeated when the parameter 'SpiMemoryModeSelection' in
the container 'SpiMemoryMode' is configured as
<DUAL_BUFFER_MODE/ TX_ONLY_MODE>.
This error occurs, if the value for channels configured for a specific
job is repeated when the parameter SpiMemoryModeSelection in the
container SpiMemoryMode is configured as DUAL_BUFFER_MODE
or TX_ONLY_MODE.
ERR083013: The SPI channels configured for a specific job should
have same value for the parameters 'SpiDataWidth' and
‘SpiTransferStartof’ of container 'SpiChannel' since the parameter
'SpiMemoryModeSelection' in the container 'SpiMemoryMode' is
configured as <value of SpiMemoryModeSelection> within a
sequence.
This error occurs, if the value configured for the parameters SpiDataWidth
or SpiTransferStart in the container SpiChannel for a specific job are
different and the parameter SpiMemoryModeSelection in the container
SpiMemoryMode is configured as DUAL_BUFFER_MODE or
TX_ONLY_MODE or FIFO_MODE.
ERR083014: The total number of buffers configured for all jobs
linked to one CSIH HW Unit should be less than or equal to <64/128>
since the value of the parameter 'SpiMemoryModeSelection' in the
container 'SpiMemoryMode' is configured as <TX_ONLY_MODE> and
the parameter 'SpiDataWidth' in the container 'SpiChannel' is
configured as less than or equal to <16>.
This error occurs, if the total number of buffers configured for all jobs
linked to one CSIH HW Unit is more than 64/128 when the value of the
parameter SpiMemoryModeModeSelection in the container
SpiMemoryModeMode is configured as TX_ONLY_MODE and the
parameter SpiDataWidth in the container SpiChannel is configured as less
than or equal to 16.
ERR083015: The total number of buffers configured for all jobs
linked to one CSIH HW Unit should be less than or equal to <32/64>
since the value of the parameter 'SpiMemoryModeSelection' in the
container 'SpiMemoryMode' is configured as
<DUAL_BUFFER_MODE> and the parameter 'SpiDataWidth' in the
container 'SpiChannel' is configured as greater than <16>.
This error occurs, if the total number of buffers configured for all jobs
linked to one CSIH HW Unit is more than 32/64 when the value of the
parameter SpiMemoryModeModeSelection in the container
SpiMemoryModeMode is configured as DUAL_BUFFER_MODE and the
26
Messages Chapter 8
parameter SpiDataWidth in the container SpiChannel is configured as
greater than 16.
ERR083016: The value of the parameter ‘SpiDataWidth’ in the
container ‘SpiChannel’ should be less than or equal to 8 since the
parameter ‘SpiDataWidthSelection’ in the container ‘SpiGeneral’ is
configured as <BITS_8>.
This error occurs, if the value of the parameter SpiDataWidth in the
container SpiChannel is not less than or equal to 8 when the parameter
SpiDataWidthSelection in the container SpiGeneral is configured as
BITS_8.
ERR083017: The value of the parameter ‘SpiDataWidth’ in the
container ‘SpiChannel’ should be less than or equal to 16 since the
parameter ‘SpiDataWidthSelection’ in the container ‘SpiGeneral’ is
configured as <BITS_16>.
This error occurs, if the value of the parameter SpiDataWidth in the
container SpiChannel is not less than or equal to 16 when the parameter
SpiDataWidthSelection in the container SpiGeneral is configured as
BITS_16.
ERR083018: In general per configuration set, the value of 'SpiJobId'
should be unique and less than 'SpiMaxJob' in 'SpiDriver' container.
This error occurs, if the value for parameter SpiJobId present in the
container SpiJob is not unique or not less than the value present in the
SpiMaxJob.
ERR083019: The number of SPI Jobs configured should be same
across the multiple configurations set container ‘SpiDriver’.
This error occurs, if the number of SPI jobs configured is not same across
the multiple configurations set container SpiDriver.
ERR083020: The value of the parameter ‘SpiJobEndNotification’
configured in the container ‘SpiJob’ should be unique for jobs
with hardware units of different memory modes.
This error occurs, if the parameter SpiJobEndNotification of the container
SpiJob is not unique for jobs with hardware units of different memory
modes.
ERR083021: The value of the parameter ‘SpiJobEndNotification’
present in the container ‘SpiJob’ should be same for SPI jobs
(having same Job Id).
This error occurs, if the parameter SpiJobEndNotification in the
container SpiJob is not same for SPI jobs (having same Job Id)
across multiple configuration sets in ECU Configuration Description
File.
ERR083022: The value for the parameter ‘SpiHwUnitSynchronous’ in
the container ‘SpiJob' should be same for jobs that are associated
with same sequence.
This error occurs, if the value for the parameter SpiHwUnitSynchronous in
the container SpiJob is not same for jobs that are associated with same
sequence. In general, the transfer mode of the jobs (that are associated
27
Chapter 8 Messages
with same sequence) should be same.
ERR083023: The value of the parameter ‘SpiHwUnitSynchronous’ in
the container ‘SpiJob’ should be same for all jobs that are having
same value for the parameter ‘SpiHwUnit’ in the container
‘SpiExternalDevice’ within a configuration set.
This error occurs, if the value of the parameter SpiHwUnitSynchronous in
the container SpiJob is different for all jobs that are having same value for
the parameter SpiHwUnit in the container SpiExternalDevice within a
configuration set.
ERR083024: 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
below does not adhere to C syntax i.e., the value should not contain
characters other than (a-z, A-Z, 0-9 or “_”) and it also should start with an
alphabet.
Table 8-2 Parameters and Containers related to ERR083024
Parameter Name
Container Name
SpiJobEndNotification
SpiJob
SpiSeqEndNotification
SpiSequence
ERR083025: The jobs configured for the parameter
'SpiJobAssignment' in the container ‘SpiSequence’ should not be
repeated since the parameter ‘SpiMemoryModeSelection’ in the
container ‘SpiMemoryMode’ is configured as
<DUAL_BUFFER_MODE/TX_ONLY_MODE>.
This error occurs, if the parameter SpiMemoryModeSelection in the
container SpiMemoryMode is configured as DUAL_BUFFER_MODE or
TX_ONLY_MODE and the jobs configured for the parameter
SpiJobAssignment in the container SpiSequence is repeated.
ERR083026: The value of the parameter
‘SpiMemoryModeSelection’ in the container ‘SpiMemoryMode’
should be same across the multiple configurations set container
‘SpiDriver’.
This error occurs, if the value of the parameter SpiMemoryModeSelection
in the container SpiMemoryMode is not same across the multiple
configurations set container SpiDriver.
ERR083027: The value of the parameter ‘SpiHwUnit’ in the container
‘SpiExternalDevice’ should be same when the parameter
‘SpiMemoryModeSelection’ in the container ‘SpiMemoryMode’ is
configured as <value of the parameter SpiMemoryModeSelection>
within a sequence.
This error occurs, if the value of the parameter SpiHwUnit in the container
SpiExternalDevice is not same when the parameter
SpiMemoryModeSelection in the container SpiMemoryMode is configured
as DUAL_BUFFER_MODE and TX_ONLY_MODE within sequence.
ERR083028: The short name of the container ‘SpiJob’ should be
same for job having same 'SpiJobId' <value for SpiJobId> across
28
Messages Chapter 8
multiple configurations set container ‘SpiDriver’.
This error occurs, if the short name of the container SpiJob is not same for
SPI jobs (having same job Id) across multiple configurations set container
SpiDriver.
ERR083029: The value of the parameter ‘SpiHwUnit’ in the container
‘SpiExternalDevice’ is configured as <value of SpiHwUnit>. The value
<value of SpiHwUnit> is not configured for the parameter
‘SpiHwUnitSelection’ in the container ‘SpiMemoryMode’.
This error occurs, if the value of the parameter SpiHwUnit in the
container SpiExternalDevice is configured as CSIHn and the same
value is not configured to the parameter SpiHwUnitSelection in the
container SpiMemoryMode. Here n is integer numbers e.g. 0, 1, etc.
ERR083030: The value of the parameter 'SpiHwUnit' in the container
‘SpiExternalDevice’ is not configured for the same memory mode as
the memory mode of the other jobs in the respective sequence.
This error occurs, if the value of the parameter SpiHwUnit in the container
SpiExternalDevice is not configured for the same memory mode as the
memory mode of the other jobs in the respective sequence.
ERR083031: The value <value of SpiHwUnitSelection> configured
for the parameter 'SpiHwUnitSelection’ present in the container
'SpiMemoryMode’ should be unique within configuration set
container
'SpiDriver'.
This error occurs, if the value of the parameter SpiHwUnitSelection in
the container SpiMemoryMode is not unique within configuration set
container SpiDriver.
ERR083032: The same value should be configured for the parameter
‘SpiHwUnit’ in the container 'SpiExternalDevice' across the
multiple configuration sets.
This error occurs, if the value configured for the parameter SpiHwUnit in
the container SpiExternalDevice is not same across multiple
configuration sets.
ERR083033: The value of the parameter 'SpiHwUnitSelection' in the
container 'SpiMemoryMode' is configured as <value for
SpiHwUnitSelection>, but none of the container 'SpiExternalDevice'
has configured 'SpiHwUnit' as <value for SpiHwUnitSelection>.
This error occurs, if the hardware unit configured in the container
SpiMemoryMode is not present in any of the SpiExternalDevice container.
ERR083034: The number of SPI sequences configured should be
same across multiple configurations set container ‘SpiDriver’.
This error occurs, if the numbers of SPI sequences configured are not
same across the multiple configurations set container SpiDriver.
ERR083035: The value of parameter 'SpiSeqEndNotification' present
in the container 'SpiSequence' should be unique for the sequences
having jobs with hardware units of different memory modes.
This error occurs, if the value of parameter SpiSeqEndNotification present
29
Chapter 8 Messages
in the container SpiSequence is not unique for the sequences having jobs
with hardware units of different memory modes.
ERR083036: The parameter ‘SpiSeqEndNotification’ in the container
‘SpiSequence’ should be same for sequences having same
'SpiSequenceId' <value for SpiSequenceId> across
multiple configurations set container ‘SpiDriver’.
This error occurs, if the parameter SpiSeqEndNotification in the container
SpiSequence is not same for SPI Sequences (having same Sequence Id)
across multiple configurations set container SpiSequence.
ERR083037: In general per configuration set, the value of
'SpiSequenceId' should be unique and less than 'SpiMaxSequence'
in 'SpiDriver' container.
This error occurs, if the value for parameter SpiSequenceId present in
the container SpiSequence is not unique or not less than the value
present in the SpiMaxSequence.
ERR083038: The short name of the container ‘SpiSequence’ should
be same for sequence having same 'SpiSequenceId' <value for
SpiSequenceId> across multiple configurations set container
‘SpiDriver’.
This error occurs, if the short name of the container SpiSequence is not
same for SPI Sequences (having same Sequence Id) across multiple
configurations set container ‘SpiDriver’.
ERR083039: The value of parameter ‘SpiPortPinSelect’ in the
container ‘SpiJob’ should not be configured as <value of the
parameter SpiPortPinSelect> since the value of the parameter
‘SpiCsSelection’ present in the container ’SpiExternalDevice’ is
configured as <value of the parameter SpiCsSelection>.
This error occurs, if the value of the parameter SpiPortPinSelect in the
container SpiJob is configured as CSLn and the parameter
SpiCsSelection present in the container SpiExternalDevice is configured
as CS_VIA_GPIO. Here n is the integer number e.g. 0, 1, etc.
ERR083040: The value of parameter ‘SpiPortPinSelect’ in the
container ‘SpiJob’ should not be configured as <value of the
parameter SpiPortPinSelect> since the value of the parameter
‘SpiCsSelection’ present in the container ’SpiExternalDevice’ is
configured as <value of the parameter SpiCsSelection>.
This error occurs, if the value of the parameter SpiPortPinSelect in the
container SpiJob is configured as Port group related pins and the
parameter SpiCsSelection present in the container SpiExternalDevice is
configured as CS_VIA_PERIPHERAL_ENGINE.
ERR083041: The value of parameter ‘SpiChannelType’ in the
container ‘SpiChannel’ should be configured as <IB> since the
parameter
‘SpiMemoryModeSelection’ in the container
‘SpiMemoryMode’ is configured with one of the values from
<value of the parameter SpiMemoryModeSelection>.
This error occurs, if the value of the parameter
SpiMemoryModeSelection in the container SpiMemoryMode is
configured as DUAL_BUFFER_MODE or TX_ONLY_MODE and the
30
Messages Chapter 8
parameter SpiChannelType in the container SpiChannel is not
configured as IB.
The value of the parameter SpiChannelType in the SpiChannel
container can be configured as EB, if the parameter
SpiHighPriorityHwHandlingEnable is configured as true in SpiGeneral
container and if this channel is linked to a job which is linked to a high
priority sequence.
ERR083042: The parameter ‘SpiHwUnit’ present in the container
‘SpiExternalDevice’ is configured as <value of the parameter
SpiHwUnit> and all of the following parameters
(SpiCsIdleEnforcement, SpiCsIdleTiming, SpiCsHoldTiming,
SpiCsInterDataDelay and SpiCsSetupTime) should be configured.
This error occurs, if the parameter SpiHwUnit present in the container
SpiExternalDevice is configured as CSIHm and any of the parameters
SpiCsIdleEnforcement, SpiCsIdleTiming, SpiCsHoldTiming,
SpiCsInterDataDelay and SpiCsSetupTime is not configured. Here m is
integer number e.g. 0, 1, etc.
ERR083043: The parameter ‘SpiPortPinSelect’ in the container
‘SpiJob’ configured should be only one unique value, since the
value of parameter ‘SpiHwUnit’ present in the container
‘SpiExternalDevice’ is configured as <value of the parameter
SpiHwUnit>.
This error occurs, if the value of the parameter SpiHwUnit present in
the container SpiExternalDevice is configured as CSIGn and more
than one unique value is configured for the parameter
SpiPortPinSelect in the container SpiJob. Here n is integer number e.g.
0, 1, etc.
ERR083044: The value of the parameter ‘SpiMaxChannel’ should
be equal to the total number of 'SpiChannel' container configured
within each 'SpiDriver' container.
This error occurs, if the value of the parameter SpiMaxChannel present in
container SpiDriver is not equal to total number of channels configured
within each SpiDriver container in ECU Configuration Description File.
ERR083045: The value of the parameter ‘SpiMaxJob’ should be equal
to the total number of 'SpiJob' container configured within each
'SpiDriver' container.
This error occurs, if the value of the parameter SpiMaxJob in the
container SpiDriver is not equal to the total number of jobs configured
within each SpiDriver container in ECU Configuration Description File.
ERR083046: The value of the parameter ‘SpiMaxSequence’ should
be equal to the total number of 'SpiSequence' container configured
within each 'SpiDriver' container.
This error occurs, if the value of the parameter SpiMaxSequence in the
container SpiDriver is not equal to the total number of jobs configured
within each SpiDriver container in ECU Configuration Description File.
ERR083048: The value of the parameter
‘SpiMemoryModeSelection’ in the container ‘SpiMemoryMode’
should be configured as <DIRECT_ACCESS_MODE> since the
31
Chapter 8 Messages
value configured for the parameter ‘SpiLevelDelivered’ in the
container ‘SpiGeneral’ is <0>.
This error occurs, if the value configured for the parameter
SpiLevelDelivered in the container SpiGeneral is 0 and the value of the
parameter SpiMemoryModeSelection in the container SpiMemoryMode is
not configured as DIRECT_ACCESS_MODE.
ERR083049: At least one instance of the container 'SpiDma' should
be configured as the value of parameter 'SpiDmaMode' present in
the container 'SpiGeneral' is configured as <true>.
This error occurs, if the parameter SpiDmaMode present in the container
SpiGeneral is configured as true and no instance of the container
SpiDma is configured.
ERR083050: The value configured for the parameters
‘SpiTxDmaChannel’ and ‘SpiRxDmaChannel’ should be unique
within a configuration set.
This error occurs, if the same DMA channel is configured for
SpiTxDmaChannel or SpiRxDmaChannel of SpiDma container for
hardware units (SpiDmaHwUnit) within a configuration set. DMA channel
(Tx or Rx) should be unique within a configuration set.
ERR083051: The number of SPI DMA configured should be same
across multiple configurations set container ‘SpiDriver’.
This error occurs, if the number of SPI DMA configured is not same
across multiple configurations set container SpiDriver.
ERR083052: The value configured in the parameters
‘SpiTxDmaChannel’ and ‘SpiRxDmaChannel’ in the container
‘SpiDma’ should be same across multiple configuration sets.
This error occurs, if the value configured in the parameters
SpiTxDmaChannel and SpiRxDmaChannel in the container SpiDma is
not same across multiple configuration set.
ERR083053: The value configured for the parameter 'SpiDmaHwUnit'
in the container 'SpiDma' should be configured in any of the
hardware units selected for jobs.
This error occurs, if the value configured for the parameter SpiDmaHwUnit
in the container SpiDma is not configured in any of the hardware units
selected for jobs.
ERR083054: The 'SpiDataWidthSelection' parameter in 'SpiGeneral'
container, has to be fixed to 'BITS_16' as SpiDmaMode parameter is
configured as true.
This error occurs, if the configured value of the parameter
SpiDataWidthSelection in the container SpiGeneral is other than BITS_16
and the SpiDmaMode parameter is configured as true.
ERR083055: The value of parameter 'SpiPortPinSelect' <value of the
SpiPortPinSelect> in the container 'SpiJob' should not be same since
the hardware units configured for respective jobs are not same.
This error occurs, if the value of parameter SpiPortPinSelect is configured
in the container SpiJob is same and the hardware units configured for
respective jobs are different. This error is applicable only for CSIG
32
Messages Chapter 8
hardware unit related jobs.
ERR083056: The DMA HW unit configured in 'SpiDmaHwUnit'
parameter of the container 'SpiDma' is invalid as 'SpiDmaMode'
parameter is configured as <true> and the same DMA HW unit is
configured as <SYNCHRONOUS> in the parameter
‘SpiHwUnitSynchronous’ of the container ‘SpiJob’.
This error occurs, if the SpiDmaMode parameter is configured as true and
the same DMA HW unit is configured as SYNCHRONOUS in the
parameter SpiHwUnitSynchronous of the container SpiJob.
ERR083057: The value of the parameter ‘SpiChannelIndex’
configured in container ‘SpiChannelList’ should be <Expected value
of SpiChannelIndex>. In general per Spi Job, the value of
‘SpiChannelIndex’ parameter should start with <0> and should be
sequential without any gaps.
This error occurs, if value of the parameter SpiChannelIndex in the
container SpiChannelList is not starting with 0 and not sequential for any
SpiJobId parameter in the container SpiJob.
ERR083058: The reference path <path> provided for the parameter
‘parameter name’ in the container ‘container name’, having short
name<container short name> is incorrect.
This error occurs, if incorrect reference provided for any of the
reference parameters (SPI_E_HARDWARE_ERROR,
SpiClockFrequencyRef, SpiDemEventParameterRefs,
SpiDeviceAssignment, SpiChannelAssignment and
SpiJobAssignment).
ERR083059: The value of the parameter ‘SpiHwUnitSynchronous’ in
the container ‘SpiJob’ should be same for all jobs that are having
same value for the parameter ‘SpiHwUnit’ in the container
‘SpiExternalDevice’ across multiple configurations set container
‘SpiDriver’.
This error occurs, if the value of the parameter SpiHwUnitSynchronous in
the container SpiJob is different for all jobs that are having same value for
the parameter SpiHwUnit in the container SpiExternalDevice across
multiple configurations set container SpiDriver.
ERR083061: The value of the parameter ‘SpiCsSelection’ in the
container ‘SpiExternalDevice’ should not be configured as <value of
the parameter SpiCsSelection> since the value of the parameter
‘SpiHwUnit’ is configured as <value of the parameter SpiHwUnit>.
This error occurs, if the value of the parameter SpiHwUnit in the container
SpiExternalDevice is configured as CSIG<n> and the value of the
parameter SpiCsSelection in the container SpiExternalDevice is configured
as CS_VIA_PERIPHERAL_ENGINE. Here <n> is an integer number e.g. 0,
1 etc.
ERR083062: The value of the parameter ‘SpiCsSelection’ in the
container ‘SpiExternalDevice’ should be configured, since the value of
the parameter ‘SpiEnableCs’ in the container ‘SpiExternalDevice’ is
configured as <true>.
This error occurs, if the value of the parameter SpiEnableCs in the
container SpiExternalDevice is configured as true and the parameter
33
Chapter 8 Messages
SpiCsSelection in the container SpiExternalDevice is not configured.
ERR083063: The value of the parameter ‘SpiPortPinSelect’ in
the container ‘SpiJob’ should be configured, since the value
of the parameter ‘SpiEnableCs’ in the container
‘SpiExternalDevice’ is configured as <true>.
This error occurs, if the value of the parameter SpiEnableCs in the
container SpiExternalDevice is configured as true and the parameter
SpiPortPinSelect in the container SpiJob is not configured.
ERR083064: The value of the parameter ‘SpiCsSelection’ in the
container ‘SpiExternalDevice’ should not be configured, since the
value of the parameter ‘SpiEnableCs’ in the container
‘SpiExternalDevice’ is configured as <false>.
This error occurs, if the value of the parameter SpiEnableCs in the
container SpiExternalDevice is configured as false and the
parameter SpiCsSelection in the container SpiExternalDevice is
configured.
ERR083065: The value of the parameter ‘SpiPortPinSelect’ in
the container ‘SpiJob’ should not be configured, since the
value of the parameter ‘SpiEnableCs’ in the container
‘SpiExternalDevice’ is configured as <false>.
This error occurs, if the value of the parameter SpiEnableCs in the
container SpiExternalDevice is configured as false and the parameter
SpiPortPinSelect in the container SpiJob is configured.
ERR083066: The DMA HW unit configured in ‘SpiDmaHwUnit’
parameter of ‘SpiDma’ container is invalid as the memory mode of
the respective hardware unit is configured as
<Configured memory mode> when the ‘SpiHighPriorityHwSequence’
in the container ‘SpiSequence' is configured as false in the
respective sequence.
This error occurs, if DMA HW unit configured for the parameter
SpiDmaHwUnit in the container SpiDma is configured with the memory
mode DUAL_BUFFER_MODE or TX_ONLY_MODE and the
SpiHighPriorityHwSequence is configured as false in the respective
sequence.
ERR083067: The value of the parameter ‘SpiHwUnitSynchronous’ in
the container ‘SpiJob’ should be configured, since the value of the
parameter ‘SpiLevelDelivered’ in the container ‘SpiGeneral’ is
configured as <2>.
This error occurs, if the value of the parameter SpiLevelDelivered in
the container SpiGeneral is configured as 2 and the parameter
SpiHwUnitSynchronous in the container SpiJob is not configured.
ERR083068: The value for the parameter ‘SpiLevelDelivered’ in
the container ‘SpiGeneral’ is configured as <2> and the
parameter ‘SpiMemoryModeSelection’ in the container
‘SpiMemoryMode’ should be configured as
<DIRECT_ACCESS_MODE>, since the respective HW Unit is
configured for <SYNCHRONOUS> in the parameter
‘SpiHwUnitSynchronous’ of the container ‘SpiJob’.
This error occurs, if the value of the parameter
SpiMemoryModeSelection in the container SpiMemoryMode is
34
Messages Chapter 8
configured as DIRECT_ACCESS_MODE and the respective HW Unit is
configured for SYNCHRONOUS in the parameter
SpiHwUnitSynchronous of the container SpiJob with the value
configured for the parameter SpiLevelDelivered in the container
SpiGeneral is 2.
ERR083069: The SPI channel configured across jobs should not be
repeated when the parameter ' SpiMemoryModeSelection' in the
container ' SpiMemoryMode' is configured as
<DUAL_BUFFER_MODE/ TX_ONLY_MODE>.
This error occurs, if the value of the parameter
SpiMemoryModeSelection in the container SpiMemoryMode is
configured as DUAL_BUFFER_MODE or TX_ONLY_MODE and the
channels configured for respective jobs are repeated.
ERR083070: The parameter 'SpiInterruptibleSequence' in the container
'SpiSequence' should be configured as <false>, since the jobs
connected to the sequence having the value of the parameter
'SpiMemoryModeSelection' in the container
'SpiMemoryMode' is configured as
<DUAL_BUFFER_MODE/TX_ONLY_MODE>.
This error occurs, if the jobs connected to the sequence having the value
of the parameter SpiMemoryModeSelection in the container
SpiMemoryMode is configured as DUAL_BUFFER_MODE or
TX_ONLY_MODE and the value of the parameter
SpiInterruptibleSequence in the container SpiSequence is not configured
false.
ERR083072: The value of the parameter ‘SpiDataWidth’ in the
container ‘SpiChannel’ is not in the range of <2 to 32> since the value
of the parameter ‘SpiHwUnit’ in the container SpiExternalDevice’ is
configured as CSIHn.
This error will occur, if the value of the parameter SpiDataWidth in the
container SpiChannel is not in the range of 2 to 32 and the value of
the parameter SpiHwUnit in the container SpiExternalDevice is
configured as CSIH<n>. Here <n> is integer numbers e.g. 0, 1, etc.
ERR083075: The chip select for the job <SpiJob short name> should
not be configured as <Chip select value>, since this chip select is
associated with a sequence <SpiSequence short name> which is
having ‘SpiHighPriorityHwSequence' parameter is configured as
<true>.
This error occurs, if the chip select for the job is configured as Chip
select value and this chip selects is associated with sequence which is
having SpiHighPriorityHwSequence parameter is configured as true.
ERR083076: Maximum acceptable baud rate for the Job
<SpiJob short name> should be less than or equal to PCLK/4 in
external device <SpiExternal device short name> in the
configuration set <SpiDriver short name>.
This error occurs, when maximum acceptable baud rate for the job is
greater than PCLK/4.
ERR083078: The value of parameter ‘SpiHighPriorityHwSequence'
35
Chapter 8 Messages
present in the container ‘SpiSequence' should be configured as
<true> for at least one of the sequences, since the parameter
‘SpiHighPriorityHwHandlingEnable' present in the container
'SpiGeneral' is configured as <true>.
The error occurs, if the value of the parameter SpiHighPriorityHwSequence
present in the container SpiSequence is not configured as true for none of
the sequences and the value of parameter
SpiHighPriorityHwHandlingEnable present in the container SpiGeneral is
configured as true.
ERR083080: The value configured for the parameter
'SpiSeqStartNotification' should follow C Syntax < [a-zA-Z] [a-zA-Z0-
9_]>.
This error occurs, if the value of configuration parameters mentioned below
does not adhere to C syntax i.e., the value should not contain characters
other than (a-z, A-Z, 0-9 or “_”) and it also should start with an alphabet.
ERR083081: The value of parameter 'SpiSeqStartNotification' present
in the container 'SpiSequence' should be unique for the sequences
having jobs with hardware units of different memory modes.
The error occurs, if the value configured for the parameter
'SpiSeqStartNotification' in the 'SpiSequence' container is same for the
sequences having jobs with hardware units of different memory modes.
ERR083082: The short name of the container ‘SpiSequence’ should be
same for sequence having same 'SpiSequenceId' <value for
SpiSequenceId> across multiple configurations set container
‘SpiDriver’.
This error occurs, if the short name of the container SpiSequence is not
same for SPI Sequences (having same Sequence ID) across multiple
configurations set container ‘SpiDriver’.
ERR083084: The parameter ‘SpiSeqStartNotification’ in the container
‘SpiSequence’ should be same for sequences having same
'SpiSequenceId' <value for SpiSequenceId> across multiple
configurations set container ‘SpiDriver’.
This error will occur, if the parameter SpiSeqStartNotification in the
container SpiSequence is not same for SPI Sequences (having same
Sequence ID) across multiple configurations set container SpiSequence.
Table 8-3 Parameters and Containers related to ERR083084
Parameter Name
Container Name
SpiSeqStartNotificationEnable
SpiGeneral
SpiSeqStartNotification
SpiSequence
ERR083085: The parameter 'SpiSeqEndNotification' in the container
'SpiSequence' should not be configured, when the parameter
'SpiHwUnitSynchronous' in the container ‘SpiJob’ is configured with
value 'SYNCHRONOUS' since the pre-compile parameter
36
Messages Chapter 8
'SpiSyncSeqEndNotificationEnable' in the 'SpiGeneral' container is
configured as false.
This error will occur if value of the parameter SpiHwUnitSynchronous in
the container ‘SpiJob’ is configured as ‘Synchronous’ , when the
parameter ‘SpiSyncSeqEndNotificationEnable’ in SpiGeneral container is
FALSE and the sequence to which the ‘SpiJob’ belongs has Sequence
end notification configured.
Table 8-4 Parameters and Containers related to ERR083085
Parameter Name
Container Name
SpiSyncSeqEndNotificationEnable
SpiGeneral
SpiSeqEndNotification
SpiSequence
ERR083086: The value of the parameter 'SpiInputClockSelect' in the
container '/Renesas/Spi0/SpiDriverx/SpiExternalDevicex' should be
same for all Jobs using the same SpiHwUnit 'CSIHx'.
The error occurs, if value of the parameter ‘SpiInputClockSelect’ in the
container SpiExternalDevice is not same for all jobs using the same
SpiHwUnit.
ERR083087: The value of the parameter 'SpiBaudrateConfiguration' for
'CSIH_BAUDRATE_REGISTER_x' in the container
'/Renesas/Spi0/SpiDriverx/SpiExternalDevicex' should be same for all
Jobs using the same SpiHwUnit 'CSIHx'
The error occurs, if value of the parameter ‘SpiBaudrateConfiguration’ for a
baudrate register in the container SpiExternalDevice is not same for all
SpiExternalDevices using the same baudrate register for all jobs using the
same SpiHwUnit.
ERR083088: The value of the parameter 'SpiPortPinSelect' in the
container '/Spi0/SpiDriverx/SpiJobz' used for
'/Renesas/Spi0/SpiDriverx/SpiExternalDevicex' should not be used for
'/Renesas/Spi0/SpiDriverx/SpiExternalDevicey' in
'/Spi0/SpiDriver0/SpiJobw'.
The error occurs, if the same value of the parameter SpiPortPinSelect
used by an SpiExternalDevice in a SpiJob container is configured for an
another SpiPortPinSelect used by another SpiExternalDevice in an
another SpiJob.
ERR083089: The value of the parameter 'SpiCsPolarity' in the
Container 'SpiExternalDevicex' used for '<HardwareUnit_Name
SpiPortPinSelect_Name>’ should be same as the value of the
parameter 'SpiCsPolarity' in the container 'SpiExternalDevicey' used
for <HardwareUnit_Name SpiPortPinSelect_Name>’.
The error occurs, if the value of the parameter SpiCsPolarity in the
container SpiExternalDevice, is not same across all the external devices
using the same SpiHwUnit CSIHx using the same chipselect.
37
Chapter 8 Messages
ERR083090: The value of the parameter <Parameter_Name> across the
containers 'SpiExternalDevicex' and 'SpiExternalDevicey' should be
same as they are referring the same SpiHw <HardwareUnit_Name>
when ‘SpiPersistentHWConfiguration’ or
‘SpiHighPriorityHwHandlingEnable’ is configured as <true>.
This error occurs, if any of the parameters SpiCsInactiveAfterLastData,
SpiShiftClockIdleLevel, SpiInputClockSelect or SpiInterruptDelayMode in
the SpiExternalDevice container are not same across the External devices
mapped to the same SpiHwUnit when SpiPersistentHWConfiguration or
SpiHighPriorityHwHandlingEnable is configured as true.
ERR083091: The value of the parameter 'SpiTransferStart' across the
containers 'SpiChannelx' and 'SpiChannely' should be same as they
are referring the same SpiHw 'CSIHn'.
The error occurs, if value of the parameters SpiDataWidth,
SpiTransferStart present in SpiChannel container are not same across all
the channel containers using the same SpiHw Unit and
SpiPersistentHWConfiguration is configured as true.
In case of CSIHx SpiHw Unit the values of the parameters SpiDataWidth,
SpiTransferStart present in SpiChannel container are not same across all
the channel containers using the same CSIHx SpiHw and the same
chipselect lines and SpiPersistentHWConfiguration is configured as true.
In case of CSIGn SpiHw Unit the values of the parameters SpiDataWidth,
SpiTransferStart present in SpiChannel container are not same across all
the channel containers using the same CSIGn SpiHw and
SpiPersistentHWConfiguration is configured as true.
Table 8-5 Parameters and Containers related to ERR083091
Container
Parameters
SpiDataWidth
SpiChannel
SpiTransferStart
SpiGeneral
SpiPersistentHWConfiguration
ERR083092: The reference path <path> provided for the parameter
‘parameter name’ in the container ‘container name’, having short name
<container short name> is incorrect.
This error occurs, if incorrect reference provided for the reference
parameter (‘SPI_E_DATA_TX_TIMEOUT_FAILURE’).
ERR083093: The reference path <path> configured for the
parameters ‘parameter name’ and ‘parameter name’ in the container
‘container name’ should be unique.
This error occurs, if the reference path provided for the parameters
SPI_E_HARDWARE_ERROR and SPI_E_DATA_TX_TIMEOUT_FAILURE,
are not unique.
38
Messages Chapter 8
ERR083094: The reference path for parameter
'SPI_E_DATA_TX_TIMEOUT_FAILURE/ SPI_E_HARDWARE_ERROR'
in the container 'SpiDemEventParameterRefs' should be same
across multiple configuration set.
This error occurs, if the reference path provided for the parameters
'SPI_E_DATA_TX_TIMEOUT_FAILURE/ SPI_E_HARDWARE_ERROR is
not same across multiple configuration sets.
ERR083107: The value configured for the parameter
‘SpiDmaTrigCtrlOnCS’ should be same across multiple configuration
set.
This error occurs, when the value configured for the parameter
SpiDmaTrigCtrlOnCS is not same across multiple configuration set.
ERR083108: When the parameter ‘SpiDmaHwUnit’ is configured as
<value of parameter SpiDmaHwUnit> and the parameter
‘SpiDmaTrigCtrlOnCS’ is configured as <value of parameter
SpiDmaTrigCtrlOnCS> in the container ‘SpiDma’, then the chip selects
configured in ‘SpiDmaHwUnit’, ‘SpiDmaTrigCtrlOnCS’ and the
parameter ‘SpiPortPinSelect’ in the container SpiJob should match.
This error occurs, when the parameter SpiDmaHwUnit’ is configured as
<value of parameter SpiDmaHwUnit> and the parameter
SpiDmaTrigCtrlOnCS is configured as <value of parameter
SpiDmaTrigCtrlOnCS> and the chip selects configured in ‘SpiDmaHwUnit’,
‘SpiDmaTrigCtrlOnCS’ and the parameter ‘SpiPortPinSelect’ in the
container SpiJob does not match.
ERR083117: The value of parameter ‘SpiCsSelection‘ in the
container ‘SpiExternalDevice’ should not be configured as
<CS_VIA_GPIO> since the value of the parameter ‘SpiHwUnit’ is
configured as < CSIH>.
This error occurs, if the value of the parameter SpiHwUnit in the
container SpiExternalDevice is configured as CSIH<n> and the value
of the parameter SpiCsSelection in the container SpiExternalDevice is
configured as CS_VIA_GPIO. Here <n> is an integer number e.g. 0, 1
etc.
ERR083120: The parameter 'SpiPortPinSelect' value in the container
'SpiJob<x>', should be configured as CSL<n> since 'CSIH<x>' is
configured.
This error will occur if SpiPortPinSelect is not configured when
SpiHwUnit is configured with CSIHn device.
ERR083121: The value of the parameter ‘SpiDataWidth’ in the
container ‘SpiChannel’ is not in the range of <7 to 32> since the
value of the parameter ‘SpiHwUnit’ in the container
‘SpiExternalDevice’ is configured as CSIGn.
This error will occur, if the value of the parameter SpiDataWidth in the
container SpiChannel is not in the range of 7 to 32 and the value of the
parameter SpiHwUnit in the container SpiExternalDevice is configured as
39
Chapter 8 Messages
CSIG<n>. Here <n> is integer numbers e.g. 0, 1, etc.
ERR083122: The SPI channel having channel id <value of the
parameter SpiChannelId> configured in the container ‘SpiChannel’
should be referred by any of the SPI job.
This error occurs, if configured SPI channel is not referred by any of the
SPI job.
ERR083123: "The value of parameter 'SpiEnableCs' in the container
'SpiExternalDevice' should not be configured as false, since the value
of the parameter 'SpiHwUnit' in the container 'SpiExternalDevice' is
configured as CSIH.
This error occurs, if CSIH hardware unit is configured and 'SpiEnableCs' is
configured as false.
ERR083124: “The parameter 'SPI_E_ECC_SELFTEST_FAILURE' in the
container 'SpiDemEventParameterRefs’ to be configured when the
parameter 'SpiECCSelfTest' is configured as <ECC_Init> or
<ECC_Init_RunTime> in 'SpiGeneral' container.”
This error occurs when 'SpiECCSelfTest' is configured as <ECC_Init> or
<ECC_Init_RunTime> and reference path for the dem error
'SPI_E_ECC_SELFTEST_FAILURE' is not configured.
ERR083125: “The parameter 'SpiECCSelfTest'should not be
configured as <ECC_Init> or <ECC_Init_RunTime> in ‘SpiGeneral’
container when there are no <CSIH> hardware units configured.”
This error occurs when 'SpiECCSelfTest' is configured as <ECC_Init> or
<ECC_Init_RunTime> and there are no CSIH hardware units configured.
ERR083126: “The parameter 'SPI_E_INT_INCONSISTENT' in the
container 'SpiDemEventParameterRefs0' has to be configured when
the parameter 'SpiInterruptConsistencyCheck' is configured as true in
'SpiGeneral' container.”
This error occurs when 'SpiInterruptConsistencyCheck' is configured as
true and reference path for the dem error 'SPI_E_INT_INCONSISTENT' is
not configured.
ERR083127: “The parameter 'SPI_E_REG_WRITE_VERIFY' in the
container 'SpiDemEventParameterRefs0' has to be configured when
the parameter 'SpiCSIGHWriteVerify' or 'SpiDMAWriteVerify' are
enabled in 'SpiGeneral' container.”
This error occurs when 'SpiCSIGHWriteVerify' or 'SpiDMAWriteVerify' is
configured as true and reference path for the dem error
SPI_E_REG_WRITE_VERIFY is not configured.
ERR083118: “The parameter
'SPI_E_LOOPBACK_SELFTEST_FAILURE' in the container
'SpiDemEventParameterRefs0' has to be configured when the
parameter 'SpiLoopBackSelfTest’ is configured as <LoopBack_Init>
or <LoopBack_Init_RunTime> in 'SpiGeneral' container.”
This error occurs when 'SpiLoopBackSelfTest’ is configured as
<LoopBack_Init> or <LoopBack_Init_RunTime> and reference path for the
dem error 'SPI_E_LOOPBACK_SELFTEST_FAILURE' is not configured.
40
Messages Chapter 8
ERR083128: “The SPI channels configured for a specific job should
be consecutive in order when the parameter
'SpiMemoryModeSelection' in the container 'SpiMemoryMode' is
configured as <DUAL_BUFFER_MODE/TX_ONLY_MODE>.”
This error occurs when multiple channels are configured for a specific job
and are not in consecutive order when the parameter
'SpiMemoryModeSelection' in the container 'SpiMemoryMode' is configured
as <DUAL_BUFFER_MODE/TX_ONLY_MODE>.
ERR083131: “The SPI jobs having Job Id <value of the parameter
‘SpiJobId’> configured in the container ‘SpiJob’ should be referred by
any of the SPI sequence.”
This error occurs, if configured SPI job is not referred by any of the SPI
sequence in ECU Configuration Description File.
ERR083129: “The parameter 'Spi_UseWriteVerifyErrorInterface' in the
'SpiGeneral’ container should be configured when any of the
parameters 'SpiCSIGHWriteVerify' or 'SpiDMAWriteVerify' are enabled'.
This error occurs, if 'Spi_UseWriteVerifyErrorInterface' is configured but
'SpiCSIGHWriteVerify' or 'SpiDMAWriteVerify' are not configured.
ERR083130: “The parameter 'SpiWriteVerifyErrorInterface' in the
'SpiGeneral' container should be configured when the parameters
'Spi_UseWriteVerifyErrorInterface' is configured as 'true'.
This error occurs, if 'Spi_WriteVerifyErrorInterface' is not configured while
'Spi_UseWriteVerifyErrorInterface' is configured as 'true'.
ERR083095: The value configured for the parameter 'SpiDmaHwUnit'
should be same across multiple configuration set.
This error occurs, if 'SpiDmaHwUnit' is not configured with the same value
across multiple configurations. It should be same across multiple
configurations.
8.2 Warning Messages
WRN083002: The value of parameter 'SpiDeviceAssignment' from
the container ‘short name of SpiJob container of one
SpiPortPinSelect’ and ‘short name of SpiJob container of another
SpiPortPinSelect’ should be same since the value of parameter
'SpiPortPinSelect' of respective jobs is same, the memory mode of
the respective Job's hardware unit is configured as
<DUAL_BUFFER_MODE or TX_ONLY_MODE> and the respective
jobs belong to the same sequence.
This warning occurs, if SpiDeviceAssignment parameter in SpiJob is not
same for the jobs having same SpiHwUnit and SpiPortPinSelect with in the
same SpiSequence and the memory mode of the respective Job's
hardware unit is configured as DUAL_BUFFER_MODE or
TX_ONLY_MODE.
WRN083004: The value for ‘SpiDmaMode’ should be configured as
<false> since the value of the parameter ‘SpiLevelDelivered’ is
configured as <0>. Hence configuration value for DMA will be ignored
for this configuration.
41
Chapter 8 Messages
This warning occurs, if the value for parameter SpiLevelDelivered is 0 and
SpiDmaMode is configured as true.
WRN083005: The value of parameter 'SpiDataWidth' from
'SpiChannel' container is <value of parameter SpiDataWidth> and
the value of parameter 'SpiDefaultData' is <value of parameter
SpiDefaultData>. Hence only Least Significant Byte is considered
from the value of parameter 'SpiDefaultData'.
This warning occurs, if the value configured in the parameter
SpiDefaultData of container SpiChannel is greater than the value
(2 SpiDataWidth – 1) of the same container when, the value of
SpiDataWidthSelection in the container SpiGeneral is configured as
BITS_8.
WRN083006: The value of parameter 'SpiDataWidth' from
'SpiChannel' container is <value of parameter SpiDataWidth> and
the value of parameter 'SpiDefaultData' is <value of parameter
SpiDefaultData>. Hence only Least Significant Word is considered
from the value of parameter 'SpiDefaultData'.
This warning occurs, if the value configured in the parameter
SpiDefaultData of container SpiChannel is greater than the value
(2 SpiDataWidth – 1) of the same container when, the value of
SpiDataWidthSelection in the container SpiGeneral is configured as
BITS_16.
WRN083009: The value of parameter 'SpiDmaMode' from the
container 'SpiGeneral' is configured as <false> and the container
'SpiDma' is configured. In this case, the configuration provided in
'SpiDma' container is ignored.
This warning occurs, if the value of parameter SpiDmaMode from the
container SpiGeneral is configured as false and the container SpiDma is
configured. In this case, the configuration provided in SpiDma container is
ignored.
WRN083010: The value for parameter ‘SpiCsPolarity’,
‘SpiCsInactive’, ‘SpiInterruptDelayMode’, ‘SpiInputClockSelect’
or ‘SpiBaudrateConfiguration' from the container
'SpiExternalDevice' should be same since the memory mode of the
respective hardware unit is configured as <DUAL_BUFFER_MODE
or TX_ONLY_MODE> and the respective jobs belong to the same
sequence. Only the configured value(s) for the first Job is
considered.
This warning occurs, if the value for parameter SpiCsPolarity,
SpiCsInactive, SpiInterruptDelayMode, SpiInputClockSelect or
SpiBaudrateConfiguration from the container SpiExternalDevice is not
same, the memory mode of the respective hardware unit is configured as
DUAL_BUFFER_MODE or TX_ONLY_MODE and the respective jobs
belong to the same sequence. Only the configured value(s) for the first
Job is considered.
WRN083012: SpiMemoryModeSelection for Spi jobs value of the
SpiJob short name of the value of the SpiSequence should be
<TX_ONLY_MODE>, since the parameter
SpiHighPriorityHwSequence in the SpiSequence container is
configured as <true> for this sequence. Hence the generation
42
Messages Chapter 8
tool ignores the value configured for the parameter
SpiHighPriorityHwSequence for this sequence.
This warning occurs, if the SpiMemoryModeSelection for Spi jobs value of
the SpiJob short name of the value of the SpiSequence should be
<TX_ONLY_MODE>, since the parameter SpiHighPriorityHwSequence in
the SpiSequence container is configured as <true> for this sequence.
Hence the generation tool ignores the value configured for the parameter
SpiHighPriorityHwSequence for this sequence.
WRN083079: The parameter 'SpiSeqStartNotification' in the container
'SpiSequence' should not be configured, since the pre-compile
parameter, SpiSeqStartNotificationEnable' in the 'SpiGeneral'
container is configured as false.
The warning occurs if value is configured for the parameter
'SpiSeqStartNotification ‘in the container 'SpiSequence' when the
parameter 'SpiSeqStartNotificationEnable' in the 'SpiGeneral' container is
configured as false.
WRN083081: The value of the parameter 'SpiCsInactiveAfterLastData'
in the container 'SpiExternalDevice' is ignored for any CSIH HW Unit
as 'SpiCsIdleEnforcement' is configured as true.
The warning will occur if the values are configured for parameters
SpiCsIdleEnforcement is true and SpiCsInactiveAfterLastData is false in
the container SpiExternalDevice for a CSIH HW Unit.
WRN083084: The parameter ‘SpiLevelDelivered’ is configured as <0>
and ‘SpiInterruptibleSeqAllowed’ in the container ‘SpiGeneral’ is
configured as <true>. Hence the value of parameter
‘SpiInterruptibleSeqAllowed’ in the container ‘SpiGeneral’ is ignored.
This warning occurs, if the parameter SpiLevelDelivered is configured as
0 (SPI Level 0 Driver) and SpiInterruptibleSeqAllowed in the container
SpiGeneral is configured as true. Hence value of the parameter
SpiInterruptibleSeqAllowed in the container SpiGeneral is ignored.
WRN083085: The parameter 'SpiHighPriorityHwSequence' in the
container ‘SpiSequence’ should not be configured as <true>. Since
the pre-compile parameter 'SpiHighPriorityHwHandlingEnable' in
the ‘SpiGeneral’ container is configured as <false>. Hence the
generation tool ignores the value configured for the parameter
'SpiHighPriorityHwSequence'.
This warning occurs, if the value of the parameter
SpiHighPriorityHwSequence configured in the container SpiSequence
is not to be configured as true. And the parameter
SpiHighPriorityHwHandlingEnable in the container SpiGeneral should be
false. On that moment Generation tool ignores the value configured for
the parameter SpiHighPriorityHwSequence.
8.3 Information Messages
INF083001: The value of the parameter ‘SpiShiftClockIdleLevel’ in the
container ‘SpiExternalDevice’ configured is ignored since the value of
parameter ‘SpiHwUnit’ present in the container 'SpiExternalDevice' is
configured as <CSIGn>.
43
Chapter 8 Messages
This information occurs, if the value of parameter SpiHwUnit present in the
container SpiExternalDevice is configured as CSIG<n> and the value of
the parameter SpiShiftClockIdleLevel in the container SpiExternalDevice is
configured. In this case the value of SpiShiftClockIdleLevel in the
container SpiExternalDevice is ignored. Here <n> is integer number e.g. 0,
1, etc.
INF083003: Calculated SPI baud rate for job ‘SpiJob’ in configuration
set ‘SpiDriver’ should be equal to <Calculated
Buadrate Hz>.
This information occurs to provide the calculated SPI baud rate for job
(SpiJob) in configuration set SpiDriver.
The calculation of baud rate is done as follows:
Baudrate = (Referred peripheral clock from MCU) /
[(2^m) * SpiBaudrateConfiguration * 2]
Table 8-6 Parameter values related to INF083003
SpiInputClockSelect
m
PCLK
0
PCLK_DIVBY_2
1
PCLK_DIVBY_4
2
PCLK_DIVBY_8
3
PCLK_DIVBY_16
4
PCLK_DIVBY_32
5
PCLK_DIVBY_64
6
INF083005: The parameters 'SpiCsIdleEnforcement', 'SpiCsIdleTiming',
'SpiCsHoldTiming', 'SpiCsInterDataDelay' and 'SpiCsSetupTime' from
the container 'SpiExternalDevice' should not be configured since the
parameter 'SpiHwUnit' present in the container 'SpiExternalDevice' is
configured as <CSIGn>.
This information occurs, if the parameters SpiCsIdleEnforcement,
SpiCsIdleTiming, SpiCsHoldTiming, SpiCsInterDataDelay and
SpiCsSetupTime are configured when the parameter SpiHwUnit in the
container SpiExternalDevice is configured as CSIG<n>. Here <n> is
integer number e.g. 0, 1, etc.
INF083006: The HW unit <value of the parameter SpiSynchHwUnit>
published in the parameter ‘SpiSynchHwUnit’ of the container
‘SpiCsig<m>/SpiCsih<n>’ is not configured as <SYNCHRONOUS>
for any of the hardware units selected for jobs.
This information occurs, if the value of the parameter SpiSynchHwUnit
configured in the container SpiCsig<m> or SpiCsih<n> is not configured
as SYNCHRONOUS for hardware units selected for any of the jobs.
Here <m> and <n> are integer numbers e.g. 0, 1, etc.
INF083008: The DMA trigger configured for hardware unit "CSIH1"
mentioned in the parameter 'SpiDmaTrigCtrlOnCS' does not match
with the hardware unit "CSIH0" of the parameter 'SpiDmaHwUnit' in
the container 'SpiDma', hence the value configured for the
parameter 'SpiDmaTrigCtrlOnCS' is ignored.
This information occurs, if the hardware unit configured in the parameter
SpiDmaTrigCtrlOnCS does not match with the hardware unit configured in
44
Messages Chapter 8
the parameter SpiDmaHwUnit of SpiDma container.
INF083009: The expected CS behavior may not be observed at high
baud rates in case of Direct Access Mode due to general limitation of
the serial controllers. A work around at high baud rates is to use FIFO
mode.
This information occurs when ever Direct Access Mode is configured to
notify the user that, at chip select behavior may not be as expected at
higher baud rate in Direct Access Mode.
INF083010: When the parameter <SpiCsPolarity> in the container
<SpiExternalDevice> is configured as high, then the setting of the
parameter <SpiDmaTrigCtrlOnCS> in the container <SpiDma> shall be
ignored.
This information occurs whenever the chip select polarity is high when DMA
is enabled and SpiDmaTrigCtrlOnCS is having values other than
<CSIHn>_<CSLn>_IC0_IR0_00.
Note: n = 0 or 1.
45
Chapter 8 Messages
46
Notes Chapter 9
Chapter 9 Notes
“Generation Tool” and “Tool” terminologies are used interchangeably to
refer SPI Driver Generation Tool.
47
Chapter 9 Notes
48
Revision History
Sl.No. Description
Version
Date
1.
Initial Version
1.0.0
24-Oct-2013
2.
Error message numbers updated.
1.0.1
28-Jan-2014
3.
Error message ERR083093 and ERR083094 are updated and
1
.0
.2
29-Apr-2014
ERR083118 and ERR083119 are added.
4.
The information message INF083003 is updated for baud rate
1.0.3
12-May-2014
formula.
5.
1. Parameter SpiReadBackConfiguration is removed from table of Error 1.0.4
23-Jul-2014
message ERR083004.
2. The information message INF083008 is added.
3. Parameter SpiLoopBackSelfTest is added in table of Error message
ERR083004.
4. Error message ERR083119 is removed, INF083004 is made as
WRN083084, ERR083072 is updated and ERR083121 is added.
5. INF083007 is made as WRN083085, Error message ERR083085 is
reformulated and for ERR083084 table is added.
6. ERR083120 is added.
6.
1. Error message ERR083118 is removed.
1.0.5
22-Oct-2014
2. Description of error message ERR083041 is updated.
3. Reference Documents section is updated.
4. Chapter 4 remark section is updated.
5. Chapter 6 is updated for the precautions.
6. Parameter SpiLoopBackSelfTest is removed in table of Error
message ERR083004.
7. Parameter SPI_E_SELF_TEST_FAILURE is removed from error
messages ERR083093 and ERR083094.
7.
1. Error messages ERR083005, ERR083018 and ERR083037 are
1.0.6
19-Nov-2014
rephrased.
8.
Following changes are made:
1.0.7
16-May-2015
1. Updated section 2.1 ‘Reference Documents’ to correct the name and
version of Parameter Definition Files.
2. Section 8.1 and Section 8.2 is modified for removing warning and
adding error message ( WRN083001 to ERR083122)
9.
Following changes are made:
1.0.8
28-Jan-2016
1. Updated Pdf versions in section 2.1 ‘Reference Documents’.
2. Mandatory parameters list updated to remove SpiFifoTimeOut
parameter in section 8.1.
3. Mandatory parameters list updated to add SpiLoopBackSelfTest,
SpiECCSelfTest, SpiInterruptConsistencyCheck, SpiWriteVerify and
SpiDmaWriteVerify parameters
4. Error messages ERR083118, ERR083124, ERR083125,
ERR083126, and ERR083127 are added.
5. Information message INF083009 is added for chip select behavior
with high baudrate.
6. ERR083054 is modified as part of fixing the ticket ARDAAAE-1452
7. ERR083090 is updated to remove ‘SpiFifoTimeOut' as per JIRA#
ARDAAAE-1334.
49
Sl.No. Description
Version
Date
10.
Following changes are made:
1.0.9
07-Apr-2016
1. ERR083013 is updated to add the validation for the parameter
SpiTransferStart as per ticket ARDAAAE1699.
2. ERR083128 is added for validating the order of channels.
3. As per ticket ARDAAAE-1584, ERR083090 message is updated for
the description.
4. As part of ticket ARDAAAE-1699 fixing, ERR083089 is updated to
brief the description in detail.
5. WRN083002 has been converted to error message ERR0830131.
11
Following changes are made:
1.0.10
15-Jul-2016
1. ERR083127 error message is updated.
2. Error messages ERR083129 and ERR083130 are added.
3. R-number is updated.
4. Removed the error messages ERR083109, ERR083110,
ERR083111, ERR083113, ERR083115, ERR083116, ERR083114
and ERR083112 and updated the error description of ERR083108.
5. Added information message INF083010.
6. Updated error description of ERR083066.
7. Renamed the macros SpiWriteVerify and SpiDmaWriteVerify to
SpiCSIGHWriteVerify and SpiDMAWriteVerify.
8. Removed the warning message WRN083080.
12
Following changes are made:
1.0.11
28-Oct-2016
1. Table numbers are added for tables present in Chapter 8.
2. Updated error description of ERR083016 and ERR083017.
13
Following changes are made:
1.0.12
17-Feb-2017
1.Updated Pdf versions in section 2.1 ‘Reference Documents’
2.Error messages ERR083005, ERR083018 and ERR083037 are
rephrased in the section 8.1
3.Error Message, ERR083095 is added in the section 8.1
4.R-number is updated.
5.Notice and Company addresses are updated
6.Copyright information is updated.
50
51
AUTOSAR MCAL R4.0.3 User's Manual
SPI Driver Component Ver.1.0.12
Generation Tool User's Manual
Publication Date: Rev.1.01, February 17, 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 1.0
AUTOSAR MCAL R4.0.3
User’s Manual
R20UT3727EJ0101
Document Outline
- Chapter 1 Introduction
- Chapter 2 Reference
- Chapter 3 SPI Driver Generation Tool Overview
- Chapter 4 Input Files
- Chapter 5 Output Files
- Chapter 6 Precautions
- Chapter 7 User Configuration Validation
- Chapter 8 Messages
- Chapter 9 Notes