D
LOCATOR ERROR MESSAGES
1 Introcuction
Error and warning messages of the locator start with a letter followed
by a number and an informational text. The error letter indicates the error
type:
2 Warnings (W)
W 100: Maximum buffer size for name is size (Adjusted)
For the given format, a maximum buffer size is defined.
W 101: Cannot create map file filename, turned
off -M option
The given file could not be created.
W 102: Only one -g switch allowed, ignored -g before name
Only one .out file can be debugged.
W 104: Found a negative length for section name,
made it positive
Only stack sections can have a negative length.
W 107: Inserted 'name' keyword at line line
A missing keyword in the description file was inserted.
W 108: Object name (name) differs from filename
Internal name of object file not the same as the filename. Maybe renamed?
W 110: Redefinition of system start point
Usually only one load module will access the system table (__lc_pm).
W 111: Two -o options, output name will be name
Second -o option, the message gives the effective
name.
W 112: Copy table not referenced, initial data is not copied
If you use a copy statement in the layout part, the initial data is
located in rom. Your start-up code should copy this data to their ram location.
W 113: No .out files found to locate
No files where specified at the invocation.
W 114: Cannot find start label label
W 116: Redefinition of name at line line
Identifier was defined twice.
W 119: File filename not found in the argument
list
All files to be located must be given as an argument.
W 120: unrecognized name option <name>
at line line (inserted 'name')
Wrong option assignment. Check the manual for possibilities.
W 121: Ignored illegal sub-option 'name' for name
An illegal format sub option was detected. See the format description for this format in the manual.
W 122: Illegal option: option (-H or -\? for help)
An illegal option was detected.
W 123: Inserted character at line line
The given character was missing in the description file.
W 124: Attribute attribute at line line
unknown
An unknown attribute was specified in the description file.
W 125: Copy table not referenced, blank sections are not cleared
Sections with attribute blank are detected, but the copy table is
not referenced. The locator generates info for the startup module in
the copy table for clearing blank sections at startup. See __lc_cp in
the manual.
W 127: Layout name not found
The used layout in the named file must be defined in the layout part.
W 130: Physical block name assigned for the second
time to a layout
It is not possible to assign a block more than once to a layout block.
W 136: Removed character at line line
The character is not needed here.
W 137: Cluster name declared twice (layout part)
The named cluster is declared twice. Duplicate cluster names are allowed in the layout part under conditions, because the clusters
are referred only. In the layout part the cluster is declared, which may
be done only once.
W 138: Absolute section name at non-existing memory
address 0xhexnumber
Absolute section with an address outside physical memory. Either the address is not correct, or the memory description for your target
is not consistent.
W 139: message
W 140: File filename not found as a parameter
All processes defined in the locator description file (software part)
must be specified on the invocation line.
W 141: Unknown space <name> in -S option
An unknown space name was specified with a -S option.
W 142: No room for section name in read-only memory,
trying writable memory ...
A section with atribute read-only could not be placed in read-only memory, the section will be placed in writable memory.
W 143: Section names has different page size than
previous group members
Section has a different page size then other sections in the same
group.
W 144: Filename name is too long, truncated to name
Filename is too long and is truncated.
W 145: Conflicting output options c (chip level) and
s (start record), s ignored
Output sub-options 's' and 'c' are conflicting sub-options. The s
option is ignored.
W 146: Address width in output format (number bytes)
is too small for address address(hex). Only first occurrence reported.
The width of the address format is too small to contain the complete address.
3 Errors (E)
E 200: Absolute address 0xhexnumber occupied
An absolute address was requested, but the address was already occupied by another section.
E 201: No physical memory available for section name
An absolute address was requested, but there is no physical memory
at this address.
E 202: Section name with mau size size
cannot be located in an addressing mode with mau size size
A bit section cannot be located in a byte oriented addressing mode.
E 203: Illegal object, assignment of non existing var var
The MUFOM variable did not exist. For some variables this is an error.
E 204: Cannot duplicate section 'name' due to hardware
limitations
The process must be located more than once, but the section is mapped to a virtual space without memory management possibilities.
E 205: Cannot find section for name
Found a variable without a section, should not be possible.
E 206: Size limit for the section group containing section name exceeded by 0xhexnumber bytes
Small sections do not fit in a page any more.
E 207: Cannot open filename
A given file was not found.
E 208: Cannot find a cluster for section name
No writable memory available, or unknown addressing mode. Often this error occurs due to an error in the description file.
E 210: Unrecognized keyword <name> at line line
An unknown keyword was used in the description file.
E 211: Cannot find 0xhexnumber bytes for section
name (fixed mapping)
One of virtual or physical memory was occupied, or there was no physical memory at all!
E 213: The physical memory of name cannot
be addressed in space name
A mapping failed. There was no virtual address space left.
E 214: Cannot map section name, virtual memory
address occupied
An absolute mapping failed. The memory on the virtual target address was already occupied.
E 215: Available space within name exceeded by number bytes for section name
The available addressing space for an addressing mode has been exceeded.
E 217: No room for name in cluster name
The size of the cluster as defined in the .dsc file is too small.
E 218: Missing identifier at line line
This identifier must be specified.
E 219: Missing ')' at line line
Matching bracket missing.
E 220: Symbol 'symbol' already defined in <name>
A symbol was defined twice.
E 221: Illegal object, multi assignment on var
The MUFOM variable was assigned more than once, probably due to an error of the object producer.
E 223: No software description found
Each input file must be described in the software description in the .dsc file.
E 224: Missing <length> keyword in block 'name'
at line line
No length definition found in hardware description.
E 225: Missing <keyword> keyword in space 'name' at line line
For the given mapping, the keyword must be specified.
E 227: Missing <start> keyword in block 'name'
at line line
No start definition found in hardware description.
E 230: Cannot locate section name, requested
address occupied
An absolute address was requested, but the address was already occupied by another process or section.
E 232: Found file filename not defined in the description
file
All files to be located need a definition record in the description
file.
E 233: Environment variable too long in line line
Found environment variable in the dsc file contains too many characters.
E 235: Unknown section size for section name
No section size found in this .out file. In fact a corrupted .out
file.
E 236: Unrecoverable specification at line line
An unrecoverable error was made in the description file.
E 238: Found unresolved external(s):
At locate time all externals should be satisfied.
E 239: Absolute address addr.addr
not found
In the given space the absolute address was not found.
E 240: Virtual memory space name not found
In the description files software part for the given file, a non existing memory space was mentioned.
E 241: Object for different processor characteristics
Bits per MAU, MAU per address or endian for this object differs with the first linked object.
E 242: message
Error generated by the object. These errors are in fact generated
by the assembler. It has been caused by a jump instruction which is out of range.
E 243: Cannot find global symbol symbol
Global symbol was not in the .out file where it should be. The filename (before the ':' in the symbol) was linked with the -B
option to the current .out file. Probable this file was changed since the invocation
of the linker.
E 244: Missing name part
The given part was not found in the description file, possibly due
to a previous error.
E 245: Illegal namevalue at line line
A non valid value was found in the description file
E 246: Identifier cannot be a number at line line
A non valid identifier was found in the description file
E 247: Incomplete type specification, type index = Thexnumber
An unknown type was referenced by the given file. Corrupted object file.
E 250: Address conflict between block block1 and
block2 (memory part)
Overlapping addresses in the memory part of the description file.
E 251: Cannot find 0xhexnumber bytes for section
section in block block
No room in the physical block in which the section must be located.
E 255: Section 'name' defined more than once at
line line
Sections cannot be declared more than once in one layout/loadmod part.
E 258: Cannot allocate reserved space for process number
The memory for a reserved piece of space was occupied.
E 261: User assert: message
User-programmed assertion failed. These assertions can be programmed in the layout part of the description file.
E 262: Label 'name' defined more than once in the
software part
Labels defined in the description file must be unique.
E 264: message
E 265: Unknown section address for absolute section name
No section address found in this .out file. In fact a corrupted .out
file.
E 266: funcionality not (yet) supported
The requested functionallity is not (yet) supported in this release.
4 Fatal Errors (F)
F 400: Cannot create file filename
The given file could not be created.
F 401: Cannot open filename
A given file was not found.
F 402: Illegal object: Unknown command at offset offset
An unknown command was detected in the object file. Corrupted object file.
F 403: Illegal filename (name) detected
A filename with an illegal extension was detected on the command line.
F 404: Illegal object: Corrupted hex number at offset offset
Wrong byte count in hex number. Corrupted object file.
F 405: Illegal section index
A section index out of range was detected. This could be a corrupted object file, but also a previous error like E231 (Missing section)
is responsible for this message.
F 406: Illegal object: Unknown hex value at offset offset
An unknown variable was detected in the object file. Corrupted object file.
F 407: No description file found
The locator must have a description file with the description of the hardware and the software of your system.
F 408: message
No protection key or not an IBM compatible PC.
F 410: Only one description file allowed
The locator accepts only one description file.
F 411: Out of memory.
An attempt to allocate more memory failed.
F 412: Illegal object, offset offset
Inconsistency found in the object module.
F 413: Illegal object
Inconsistency found in the object module at unknown offset.
F 415: Only processor .out files can be located
It is not possible to locate object for other processors.
F 416: Unrecoverable error at line line, name
An unrecoverable error was made in the description file in the given part.
F 417: Overlaying not yet done
Overlaying is not yet done for this .out file, link it first without
-r flag!
F 418: No layout found, or layout not consistent
If there are syntax errors in the layout, it may occur that the layout
is not usable for the locator. Syntax errors in the description file
must be resolved!
F 419: message
F 420: Demonstration package limits exceeded
One of the limits in this demo version was exceeded.
F 421: Error writing file name
An error occurred when writing to the file.
F 422: Input file name same as output file
Input file and output file cannot be the same.
5
Verbose (V)
V 000: File currently in progress:
Verbose message. On the next lines single filenames are printed as
they are processed.
V 001: Output format: name
Verbose message for the generated output format.
V 002: Starting pass number
Verbose message, start of given pass.
V 003: Abort !
The program was aborted by the user.
V 004: Warning level number
Verbose message, report the used warning level.
V 005: Removing file file
Verbose message cleaning up. Temporary files are always removed, map file and .out file are removed if switch -e is
on and the exit code is unequal zero.
V 006: Found file <filename> via path pathname
The description (include) file was not found in the standard directory. The locator searches also in the install directory
etc, in which
the file was found.
V 007: message
Copyright © 2000 TASKING, Inc.