Warning Messages: WM*

• List of Warning Messages, Part1: WB*

• List of Warning Messages, Part2: WC*

• List of Warning Messages, Part3: WI*

• List of Warning Messages, Part4: WL*

WMake21

All instances of class %1 will share the same parameter set

WMake22

%1 is empty for interpolation %2

WMake220

%3 %1 (original value %2) not found for interpolation %4, but exists after replacement of make variables

WMake221

Unknown interpolation ID "%1" in interpolation alias mapping file %2 – this mapping is ignored

WMake222

The interpolation "%1" is not an alias, but is mapped – this mapping is ignored

WMake223

The interpolation "%1" is an alias, but is the target of a mapping – this mapping is ignored

WMake224

Duplicate mapping of interpolation "%1" – this mapping is ignored

WMake28

ResolveSystemConstant=AtRunTime is not supported for SE targets

WMake30

The batch build process is deprecated – please enable the make build process

WMake40

target specific option %1="%2" not valid %3- use default: %4

WMake70

Invalid OS specification – task list must not be empty

WMdl0

please note: the feature <%1> is obsolete and will be removed in the future

WMdl00

please note: the value "%1" of project option "%2" is obsolete and will not be supported in the future – use value "%3" instead

WMdl000

please note: the value "%1" of project option "%2" is obsolete, when used together with value "%3" of option "%4" – use %5 instead

WMdl1

inline method <%1> not yet specified – generated method call

WMdl100

compiler inline of method "%1" ignored – not supported by selected compiler tool

WMdl104

<%1> – due to %2 – is not a lvalue and can not be used with a %3 method argument

WMdl105

method <%1> in service/prototype class has element <%2> of type <%3> – the layout is generated by ASCET (maybe only for experiments) and should therefore not be used externally

WMdl106

element <%1> in service/prototype class is of type <%2> – the layout is generated by ASCET (maybe only for experiments) and should therefore not be used externally

WMdl107

prototype class <%1> has local elements and is instanciated multiple times -- this is likely a modelling error, since no self pointer is generated for prototype classes

WMdl108

Array argument %1 in C code represents a structure – consider to use the macro ASD_USE_ARRAY_EXTERNAL to access the plain array

WMdl11

expected global variable <%1> for export – used local instead

WMdl111

usage of "%1" variable requires additional effort for ECU integration (in AUTOSAR context)

WMdl1191

RTE status variable may reference multiple status returns

WMdl1192

Label <%1> for Rte_StdReturnType is deprecated, please use <%2> instead

WMdl14

not supported for controller targets: process "%1" used in more than one task (%2)

WMdl140

target %1 does not support Timetable – use Alarm Timer instead

WMdl15

no tasks specified – will probable lead to errors in subsequent processing steps

WMdl150

Memory class "%1" specified for %2 is not declared in file "%3" – Please add declaration

WMdl151

Memory segment "%1" specified for %2 is not declared in file "%3" – Treated as "Automatic"

WMdl152

Unable to propagate memory segment "%1" to record because it is accessed via reference

WMdl153

Service Routine <%1> uses different memory classes (%2), but it is recommended to assign all local variables and the class itself to the same memory class

WMdl16

runnables of component "%1" not mapped to events – might lead to errors during compilation

WMdl160

element "%1" not passed to EHOOKS, since measurement of tables is not supported by ASAM 2MC 1.4 standard

WMdl161

message "%1" hooked to "%2" but not written in any bypass function

WMdl162

component "%1" not passed to EHOOKS (as single instance) for ASAM-2MC generation, since it is used as a %2

WMdl163

element "%1" not initialized with external bypass value since this feature is not supported by selected EHOOKS version ("%2") – init value used instead

WMdl164

assignment to message "%1" removed, since message has been mapped to diagnostic code, i.e. system constant

WMdl17

Element <%1> specified as redundant, but there is no verify call for this element

WMdl2

variable "dT" not specified, generate default variable

WMdl200

deprecated feature: implicit reference of <%1>. declare an explicit reference instead!

WMdl201

Method call argument "%2" used multiple times with OUT or INOUT direction in "%1", values may overwrite each other

WMdl202

explicit reference flag and deprecated asReference flag in C code component are not equal for element <%1>.

WMdl203

Model type %1 for element %2 is deprecated – use limitInt or wrapInt instead

WMdl204

deprecated feature: BDE temp variables

WMdl205

Use of reference for target %1 may lead to follow-up problems – see KIR #519264

WMdl206

Comparision of address of two instances <%1> and <%2> is always false/true – note: for non-scalar typed elements ASCET compares by address

WMdl207

Address of message <%1> used, but neither read nor write usage found – note: this may lead to follow-up problem, e.g., none defined message copies

WMdl211

operator uses temp variable and has maybe unsuitable type in physical/quantized generation

WMdl275

Mapping of record typed element "%1" requires all fields to be mapped; missing mappings for fields (%2)

WMdl276

Method call %1 cannot be generated as RTE call %2, because %3

WMdl2761

"%1" specified as return type of client/server operation "%2" not checked upon server call

WMdl277

The value <External Replacement> is not supported for <%1> in AUTOSAR version %2: <%3>

WMdl28

ResolutionTime set to "RunTime" for System Constant "%1" is not supported for SE targets

WMdl280

User defined System Constant "%1" uses missing Kind "%2" – Target Settings are used for resolution time

WMdl281

User defined System Constant "%1" has optimization "%3" which is incompatible with resolution time "%2" – default settings are used

WMdl2820

User defined System Constant "%1" has invalid resolution time "%2" – default settings are used

WMdl2821

User defined System Constant "%1" has invalid optimization "%2" – default settings are used

WMdl283

Invalid settings of AUTOSAR attributes for element "%1": %2="%3" and %4="%5" – use %6="%7" instead

EXAMPLE
Invalid settings of AUTOSAR attributes for element "<element_name>": swPolicy="QUEUED" and swCalibration="ReadOnly" - use swCalibration="NotAccessible" instead

WMdl285

Interrunnable Variable "%1" not used

WMdl286

Interrunnable Variable "%1" used in one runnable ("%2") only

WMdl288

Explicit access (%1) to explicit IRV "%2" ignored

WMdl2881

Explicit access (%1) to message "%2", which is not mapped to an IRV, is ignored

WMdl289

Implicit access (%1) to explicit IRV "%2" made explicit access

WMdl291

%1 preemptive priority levels exceed maximum of %2 (task priorities are in range)

WMdl292

%1 cooperative priority levels exceed maximum of %2 (task priorities are in range)

WMdl293

%1 software priority levels (cooperative + preemptive) exceed maximum of %2 (task priorities are in range)

WMdl3

used expr <%1> as a statement

WMdl3026

Unable to read from write-only element <%1>

WMdl3027

Reference element <%1> may point to stack-local element <%2>, but is not allowed to do so

WMdl3031

Stack variable "%1" of method "%2" of component "%3" with implementation "%4" has been converted to scalar type "%5"

WMdl309

Interpolation for element %5 between index %1 (value %2) and %3 (value %4) may lead to value 0, but element is specified as ZERO NOT INCLUDED

WMdl31

used assignment to <%1> as expression

WMdl310

application mode "%1" is assigned to several init tasks: %2 --- only one init task per application mode is allowed

WMdl311

application mode "%1" requires init task to be assigned to

WMdl312

read access to message "%1" in method "%2" might not return current value in context of %3 "%4" due to option "message usage variant" set to %5

WMdl313

write access to message "%1" in method "%2" might not affect current value in context of %3 "%4" due to option "message usage variant" set to %5

WMdl314

%1 access to message "%2" in function "%3", but not called from any task with option "message usage variant" set to %4

WMdl315

No task calls process "%1" defined in generic component "%2"

WMdl320

disabling message copy generation might be unsafe with respect to data integrity

WMdl35

unusual type <%1> for operation "%2"

WMdl385

%1 message "%2" not used

WMdl386

Unmapped message "%1" used in one runnable ("%2") only – generated as variable without access protection

WMdl387

Runnable "%1" requires event specification to be associated with

WMdl388

Duplicate name "%1" for AUTOSAR runnable and event specification may lead to integration failure.

WMdl40

public %1 "%2" specified as inline may not call private method "%3"

WMdl400

Element "%1" has both attributes >non volatile< and >virtual< set. This is not allowed anymore, please change settings manually.

WMdl42

External %1 access activated for element "%2" but generation of data structures for component "%3" disabled

WMdl47

Implementation of instance <%1> of non-rescalable component <%2> does not need a rescaling formula – will be ignored

WMdl472

The exported variable "%1" in project "%2" has no corresponding import

WMdl491

No dispatch point is connected to bypass function "%1"

WMdl492

Unknown process reference at index %1 in bypass function "%2" – will be ignored

WMdl50

Implementation type "%1" for logic typed element "%2" not supported by AUTOSAR – changed to "bool"

WMdl500

Implementation type "%1" for logic typed element "%2" not supported by %3 – changed to "bool"

WMdl501

%1 with external struct/typedef should be defined with user-defined order

WMdl51

Data Element "%1" of provide port "%2" (%3 "%4") not written to in SW Component

WMdl52

Not supported implementation specification "%1" for executable "%2" – removed %1 for generation

WMdl53

Not supported value "%1"%2 for implementation specification "%3" in "%4" – use value "%5" for generation

WMdl55

Different init values of %1 (%2) and mapped message "%3" (%4)

WMdl56

IRV "%1" not written to in SW Component

WMdl570

Component <%1> used although no element within the component is used – this analysis is done due to variant coded data structure generation

WMdl6

type mismatch with casting from <%1> (<%2>) to <%3>

WMdl606

type mismatch for method call ("%1"): expected VOID method, i.e. no return value

WMdl61

type mismatch: propagation of implementation for <%1> from <%2> to <%3>

WMdl611

Variable %1 without implementation is used as an OUT argument – default implementation is used

WMdl612

Variable %1 without implementation is used as an OUT argument and assigned later – implementation is taken from assignment

WMdl613

Variable %1 without implementation and discrete model type must have an integer implementation type and the identity formula – default implementation is used

WMdl614

Variable %1 without implementation and udisc model type will get a signed implementation type

WMdl615

Variable %1 without implementation and sdisc model type will get an unsigned implementation type

WMdl616

Variable %1 of type %2 without implementation is not supported – default implementation is used

WMdl620

Type mismatch in %1 mapping of message "%2". Boolean type ([0,1]) expected, got interval "%3"

WMdl621

Type mismatch in %1 mapping of message "%2". Enumeration type "%3" (%4) expected, got "%5" (%6)

WMdl622

Type mismatch in %1 mapping of message "%2". Float type "%3" expected, got "%4"

WMdl623

Type mismatch in %1 mapping of message "%2". Formula "%3" and interval %4 expected, got "%5" (%6)

WMdl625

Possible loss of precision in conversion. Intermediate type (float32) supports 23 signifiant bits only, but %1 "%2" has larger implementation interval "%3"

WMdl63

type mismatch: expected <%1>, got <%2> – the value has been implicitly converted

WMdl635

non identical types in %1 mapping for "%2" (defined in "%3") – %4: expected <%5>, got <%6>

WMdl65

type mismatch in array max size: <%1> and <%2> – accepted since larger matches smaller

WMdl651

Possible type mismatch in array max size: <%1> and <%2> – due to specified maximal array/matrix size – will be checked at compile time

WMdl652

Possible type mismatch in array max size: <%1> and <%2> – due to restrictions of the specified usage – will be checked at compile time

WMdl653

The option <%1> is not considered in AUTOSAR projects. It leads to inconsistent code for matrices.

EXAMPLE
The option <generate matrices one-dimensional> is not considered in AUTOSAR projects. It leads to inconsistent code for matrices.

WMdl655

Mismatch of physical unit %1 and %2

WMdl656

Mismatch of physical unit category %1 and %2

WMdl657

Instance <%1> of component without generic physical units <%2> does not need a concrete physical unit – will be ignored

WMdl66

mismatch of interpolation: %1 and %2

WMdl67

mismatch of extrapolation: %1 and %2

WMdl68

implicit casting of array/matrix <%1> to fixed array/matrix of size 1 for method call to <%2>

WMdl681

Ignoring difference in model type/limit flags for <%1> for method call to <%2>

WMdl7

init value <%1> of element "%2" does not match specified physical interval %3 of selected implementation

WMdl70

init value <%1> of parameter "%2" does not match specified physical interval %3 of selected implementation – will be limited

WMdl71

Axis points for fixed char table %1 should have equal distances

WMdl72

Axis points of element %1 should be in strict monotonic %3 order %2

WMdl721

Interpolation potentially performed on a char table without previous search on "%1"

WMdl722

Interpolation potentially performed on a char table without previous search on imported distribution "%1"

WMdl73

Char table axis with only one element, should be at least two

WMdl74

type <%1> of indexed expression "%2" allows negative values --- potential problem for indexing

WMdl75

Converting array <%1> with component implementation <%2> to <%3>, which enlarges the implementation interval

WMdl8

Non-volatile variable "%1" not supported for target %2

WMdl82

read access to method local variable "%1" possibly prior to assignment

WMdl821

read access to method local variable "%1" possibly prior to initialization of reference

WMdl822

read access to reference without init value "%1" possibly prior to initialization of reference

WMdl823

Method local references may be discouraged by modeling guidelines ("%1")

WMdl83

Evaluation order may not be preserved in the compiled code and lead to unexpected behaviour

WMdl84

Evaluation order may not be preserved in the compiled code and possibly lead to unexpected behaviour

WMdl85

Global Analysis not performed because of local code generation – please generate code in project context to get full analysis

WMdl86

send message "%1" probably used as receive message

WMdl87

receive message "%1" probably used as send message

WMdl880

message "%1" of type "matrix" not supported in SCOOP-IX with option "Array message flattening" enabled

WMdl881

Comparison of a continuous value for equality or inequality

WMdl882

An else-clause is missing in this if .. else if construct.

WMdl883

The default clause is not the last clause in this switch statement

WMdl884

The switch statement does not contain a case clause

WMdl885

The case or default clause is not empty and not terminated by an unconditional break or return

WMdl886

Comparison of fixed point values with unknown precision for equality or inequality

WMdl887

Comparison of a fixed point value and a constant value that needs to be rounded for equality or inequality

WMdl888

First clause of a for loop shall be empty or an assignment.

WMdl8881

Second clause of a for loop shall not have side effects.

WMdl8882

Second clause of a for loop shall use the loop counter <%1> and (optionally) loop control flags.

WMdl8883

%2 of a for loop shall not use an object that is modified in its body: <%1>

WMdl8884

Third clause of a for loop shall only modify the loop counter <%1> without any side effects.

WMdl8885

The loop counter in a for loop shall be of integer type with an ident formula: <%1>

WMdl8886

The loop condition is always <%1>

WMdl8891

The child statement of this %1-statement should not be an empty statement

WMdl89

Comparison of <%1> with itself evaluates to always %2

WMdl9

element "%1" already declared in component scope

WMdl912

method call to method <%1> without parenthesis

WMdl921

project option "Max. number of Iterations" set to 0 -- no infinite loop protection

WMdl922

Break operator is used inside a %1 loop

WMdl923

Return operator is used inside a %1 loop

WMdl93

obsolete feature: enum <%1> as index of <%2>, use "%3.value()" instead

WMdl94

Unknown enum label "%1", using variable with this name instead

WMdl941

Variable name "%1" has pattern _t<n>, where <n> is a decimal number, and is reserved for temporary variables

WMdl942

Enum label ambiguous, but treated as %1 – consider using a qualified label %2

WMdl95

method argument "%1" possibly not assigned, but needs assignment because of OUT direction

WMdl96

method argument "%1" never assigned although declared with INOUT direction

WMdl961

method "%1" is declared as side-effect-free, but has no return value

WMdl962

method "%1" is declared as side-effect-free, but return value is not used

WMdl97

method argument "%1" never read although declared with INOUT direction

WMdl98

BDE temp variable expression <%1> has side effects and option <Disable BDE Temp Variables> is set -- this may lead to problems, please adapt your model