F001: protection error: <cause>
An error occurred during the copy protection check. The <cause> provides more
details of the problem.
F002: unrecognized file format: "<file>"
The linker does not recognize the format of <file>. Perhaps the file is
corrupted.
F003: unrecognized archive format: "<archive>"
The linker does not recognize the format of <archive>. Perhaps the archive is
corrupted.
F004: cannot open "<file>" (<cause>)
The linker cannot open the <file> for reading. Check if the file exists and
has the correct permissions. The <cause> is the reason for the error, obtained
from the operating system.
F005: cannot create "<file>" (<cause>)
The linker cannot create the <file> for writing. Check if the directory exists
and has the correct permissions. The <cause> is the reason for the error,
obtained from the operating system.
F006: read error: <cause>
The linker cannot read from a file. The <cause> explains the reason of the
error.
F007: write error: <cause>
The linker cannot write to a file. The <cause> explains the reason of the
error.
F008: out of memory error
The linker cannot allocate enough memory.
F009: internal error: <cause>
The linker received an error while handling data in the intermediate object
file. The <cause> explains the reason of the error.
F010: object reader error for "<file>": <cause>
The linker received an error while reading the object file <file>. The <cause>
explains the reason of the error.
F011: object writer error for "<file>": <cause>
The linker received an error while writing the object file <file>. The <cause>
explains the reason of the error.
F012: expression evaluation error: <cause>
The linker encountered an error while evaluating an expression: <cause>.
F013: core name missing for task: <task>
The linker requires a core name to be set for each task, using the -C<core
name> option. This core must be defined in the LSL file.
F014: core <core> specified on commandline not found in LSL file
The core specified on the commandline is not found in the LSL file.
F015: core <core> specified on commandline found in multiple processor
definitions in LSL file
The core specified on the commandline is found in multiple processor
definitions in the LSL file.
F016: invalid MAU size
The linker encountered sections with a different MAU size than specified in
the LSL file. Please check your LSL file.
F017: an internal error occurred: <problem>
The linker encountered an internal error. <problem> gives an indicaton of what
went wrong.
F018: <error>, aborting...
The linker encountered a fatal error and aborted processing of input files.
F019: unrecoverable error: <cause>
The linker is in such a state that continuation of execution is not possible.
The <cause> explains the reason for the error.
F020: more than <maxerrors> errors, aborting
The maximum amount of <maxerrors> errors has been exceeded.
F021: cannot execute: "<command>"
The linker could not execute <command>.
F022: "<command>" terminated by signal <signal>
The execution of <command> raised the given <signal>.
F023: program execution failed: "<command>"
The linker could not execute <command> succesfully.
F024: cannot set environment variables
The linker was not able to set the correct environment variables for
execution.
E100: unexpected error: <message>
An unexpected error <message> occurred.
E101: command line error: <cause>
An error occurred while processing the command line arguments. The <cause>
explains the reason for the error.
E102: unknown option: "<option>"
The <option> is unknown to the linker.
E103: unsupported option: <cause>
The option is not supported in this context. The <cause> explains the reason
of the error.
E104: inconsistent input file: <cause>
An error occurred while checking the input files for consistency. The <cause>
explains the reason of the error.
E105: task endianness <x> not supported by selected core
The task was assigned an endianness, either by default or the --endianness
option, that is not supported by the core.
E106: unresolved external: <message>
The linker could not resolve all external symbols. This is an error when the
incremental linking option is not enabled. The <message> indicates the symbol
that is unresolved.
E107: unresolved symbol for shared memory reference: "<symbol>" in task <task>
The linker could not resolve the symbol <symbol> that refers to something
located in shared memory for a different core.
E108: multiple definitions of symbol "<symbol>" in both "<file1>" and
"<file2>"
The linker detected multiple non-weak definitions of <symbol>.
E109: LSL assignment in address space "<space>" to symbol "<symbol>" declared
in different address space
The symbol <symbol> assigned in the LSL file in address space <space> is
declared in a different address space.
E112: cannot locate <count> section(s):
The linker was unable to locate the sections summarized below. Any special
requirements are summarized too. See the mapfile for more information (use
-m2).
E116: invalid restriction: <restriction>
The linker could not process a restriction because it is inconsistent with
itself or the hardware description.
E117: Conflicting restriction for sections <section1> and <section2>: <cause>
The linker could not locate the sections because they are part of conflicting
restrictions. The <cause> explains the reason of the error.
E119: unable to map the address <addr> (symbol "<symbol>") from space <space1>
to <space2> via shared memory
The linker was unable to map the address specified by <addr> from space
<space1> to <space2> through a shared memory location.
E120: expression evaluation error in "<task>": <cause>
An error occurred while evaluating relocation expressions to absolute values,
for task <task>. The <cause> explains the reason of the error.
E121: relocation error in "<task>": <cause>
An error occurred while patching the result of the evaluated relocation
information into the data in the objectfile, for task <task>. The <cause>
explains the reason of the error.
E122: copy table construction error for "<task>": <cause>
An error occurred with the construction of the copy table. The <cause>
explains the reason of the error.
E123: section <section> requires initialization code in task "<task>" for
symbol "<symbol>"
The linker detected that section <section> must be initialized at application
startup time, but no code was supplied for this purpose. Provide your own, or
use the default. Check if the symbol <symbol> is referred to from your
(startup) code or LSL file.
E124: section <section> is not aligned at <align>
The linker detected that section <section> was not aligned at <align>, which,
in this case, is considered an error. The previous error message declares the
context in which to interpret this error message.
E125: mpu data table construction error for "<task>": <cause>
An error occurred with the construction of the mpu data table. The <cause>
explains the reason of the error.
W127: could not find system library "<lib>"
The linker was unable to find the system library <lib>. Use the -L option to
add a directory to the library search path. A description of the library
search algorithm can be found in the reference manual.
W128: section attribute conflict for <section>: <cause>
The linker detected conflicting attributes for @(section). The <cause>
explains the reason of the error.
W129: a section_reference_restriction refers to safety class 0 but this has no
effect
Safety class 0 is the default safety class and can be used for code that runs
with the MPU disabled. Therefore no entry in the MPU table is present for this
default safety class. A section reference restriction that refers to safety
class 0 has no effect.
W130: a section_reference_restriction refers to safety class <class