Error Messages: E*

• List of Error Messages, Part 1: E*

• List of Error Messages, Part 2: F*

• List of Error Messages, Part 3: G*

• List of Error Messages, Part 4: MB* – ML*

ECCg0

%1

ECCg10

Characteristic table/distribution must be parameter <%1>

ECCg11

Separate "search"/"interpolate" functions of characteristic tables are not supported. Please use "getAt" function instead.

ECCg12

Distribution of fixed characteristic <%1> must be regular.

ECCg13

Bit types are not supported for instance variables of classes: <%1>

ECCg41

Memory class <%1> specified for %2 is not declared in file "memorySections.xml" – Please add declaration

ECCg9

(CodeGenerator) Element <%1>: size of values (%2) exceed size of type (%3)

ECg1

logic has semantic errors; should not be able to generate Code

ECg2

Invalid %1 path name: %2

ECg5

%1 "%2", used as SHORT-NAME tag in AUTOSAR XML generation, must not %3

ECg84

Invalid template parameter(s) "%1" used for symbol "%2"

ECg85

"%1" is not a valid ANSIC identifier --- check symbol template "%2"

EIa1

Code Generation (internal) – %2

EIa2

Code Generation – %2. Try smaller intervals or larger quantizations

EIa3

Interval %1 does not fit in a valid integer type, with respect to option "maximum bit length"

EMake0

%1

EMake10

Cannot generate code because of a cyclic dependency of components in sub graph %1

EMake20

Component name "%1" is not unique in project "%2"

EMake21

Class %1 has parameters, so all instances must have the same data set

EMake22

Interpolation scheme must be the same in all instances of "%1" for element named "%2"

EMake220

%3 %1 (original value %2) not found for interpolation %4

EMake221

%1 is empty for interpolation %2

EMake222

Invalid interpolation mapping because of flag "%1"

EMake223

Alias interpolation "%1" is not mapped

EMake224

Interpolation %1 must allow increasing or decreasing axis points

EMake23

Cannot use experimental expander for controller code generation

EMake24

Object Based Controller Implementation can only be used together with an ASCET‑SE target

EMake241

Special implementation "Mixed_Physical_Implementation" for element "%1" can only be used together with physical code generation – please select another implementation

EMake25

Cannot use experimental code generation with controller target

EMake26

Generation of operating system configuration is required using experimental targets – please activate appropriate Build option

EMake27

Cannot create exported element "%2" due to multiple implementations of component "%1"

EMake28

maximum size of %1 defined in tool options has invalid value <%2>. Allowed range is <%3>.

EMake30

Names of datasets (%1) used in current project are not unique for component "%2"

EMake31

Dataset and implementation must be identical for all instances of Module "%1"

EMake32

Missing implementation set for component "%1

EMake33

Missing %1 set for element "%2" in component "%3"

EMake34

Inconsistent use of %1s in model: %2>>%3 vs. %2>>%4

EMake41

Module "%1" should be instantiated only once, due to single instance semantics

EMake42

Only one %1 can be used in an ASCET project

EMake43

AUTOSAR use case requires one instance of a %1 to be used in an ASCET project

EMake44

Cannot use "%1" code generation for AUTOSAR use case

EMake50

Multiple defined conversion name "%1" – used as formula as well as enumeration name

EMake51

"%1" instances can only be used in %2 components

EMake52

Instances of %1 components must not be used in %2 components

EMake60

Target type "%1" not unique, used in multiple declaration files: %2

EMake61

Memory segment ID "%1" not unique, used in multiple declarations

EMake610

Target %1 does not support %2 – please change option or target

EMake611

Unsupported value "%3" for target %1 related option "%2" – please change option

EMake62

Memory segment ID "%1" is reserved for internal use

EMake67

Unreadable read costs for memory section <%1> -- see memorySections.xml in your target directory

EMake68

Schema Validation Error for memory section <%1> -- see memorySections.xml in your target directory

EMake70

Invalid OS specification – task list must not be empty

EMake80

Component prefix "%1" is no valid ANSI C identifier; see project options

EMake81

Component name "%1" is no valid ANSI C identifier

EMake82

AUTOSAR SW Component name "%1" is reserved within AUTOSAR tool chain – please change

Invalid template "%2" – %1

EMake99

Invalid %1 build tool configuration: %2 not supported – please change setting

EOS1

no operating modes specified

EOS3

illegal identifier <%1> for task – must be compliant with ANSI C

EOS4

Operating system %1 is not supported for target %2