370 Chapter 9. Linker/Locator
Fatal Errors
9 |
Error |
Error Message and Description |
|
201INVALID COMMAND LINE SYNTAX
A syntax error is detected in the command line. The command line is displayed up to and including the point of error.
202INVALID COMMAND LINE, TOKEN TOO LONG
The command line contains a token that is too long. The command line is displayed up to and including the point of error.
203EXPECTED ITEM MISSING
An expected item is missing in the command line. The command line is displayed up to and including the point of error.
204INVALID KEYWORD
The invocation line contains an invalid keyword. The command line is displayed up to and including the point of error.
205CONSTANT TOO LARGE
A constant in the invocation line is larger than 0FFFFH. The command line is displayed up to and including the point of error.
206INVALID CONSTANT
A constant in the invocation line is invalid; e.g., a hexadecimal number with a leading letter. The command line is displayed up to and including the point of error.
207INVALID NAME
A module or segment name is invalid. The command line is displayed up to and including the point of error.
208INVALID FILENAME
A filename is invalid. The command line is displayed up to and including the point of error.
209FILE USED IN CONFLICTING CONTEXTS
FILE: filename
A specified filename is used for multiple files or used as an input as well as an output file.
210I/O ERROR ON INPUT FILE: system error message
FILE: filename
An I/O error is detected by accessing an input file. A detailed error description of the EXCEPTION messages is described afterwards.
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
371 |
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Error |
Error Message and Description |
|
|
|
|
|
|
|
|
|
9 |
|
211 |
I/O ERROR ON OUTPUT FILE: |
|
|
||
|
|
|
system error message |
|
|
|
|
|
|
FILE: filename |
|
|
|
|
|
|
An I/O error is detected by accessing an output file. A detailed error description of |
|
|
|
|
|
|
the EXCEPTION messages is described afterwards. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
212I/O ERROR ON LISTING FILE: system error message
FILE: filename
An I/O error is detected by accessing a listing file. A detailed error description of the EXCEPTION messages is described afterwards.
213I/O ERROR ON WORK FILE:
system error message
An I/O error is detected by accessing a temporary work file of BL51. A detailed error description of the EXCEPTION messages is described afterwards.
214INPUT PHASE ERROR
MODULE: filename (modulename)
This error occurs when BL51 encounters different data during pass two. This error could be the result of an assembly error.
215CHECK SUM ERROR
MODULE: filename (modulename)
The checksum does not correspond to the contents of the file.
216INSUFFICIENT MEMORY
The memory available for the execution of BL51 is used up.
217NO MODULE TO BE PROCESSED
No module to be processed is found in the invocation line.
218NOT AN OBJECT FILE
FILE: filename
The specified file is not an object file.
219NOT AN 8051/X51 OBJECT FILE FILE:filename
The specified file is not a valid x51 object file.
220INVALID INPUT MODULE
FILE: filename
The specified input module is invalid. This error could be the result of an assembler error.
|
372 |
|
|
Chapter 9. Linker/Locator |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Error |
Error Message and Description |
|
|
9 |
|
|
|
|
|
|
|
221 |
MODULE SPECIFIED MORE THAN ONCE |
|
|||
|
|
|
The invocation line contains the specified module more than once. The command |
|
|
|
|
|
|
|
|
||
|
|
|
|
line is displayed up to and including the point of error. |
|
|
|
|
|
|
|
|
|
|
|
222 |
SEGMENT SPECIFIED MORE THAN ONCE |
|||
|
|
|
|
The invocation line contains the specified segment more than once. The |
||
|
|
|
|
command line is displayed up to and including the point of error. |
||
224DUPLICATE KEYWORD OR CONFLICTING CONTROL
The same keyword is contained in the invocation line more than once or contradicts with other keywords. The command line is displayed up to and including the point of error.
225SEGMENT ADDRESS ARE NOT IN ASCENDING ORDER
The base addresses for the segments are not displayed in ascending order during the location control. The command line is displayed up to and including the point of error.
226SEGMENT ADDRESS INVALID FOR CONTROL
The base addresses for the segments are invalid for the location control. The command line is displayed up to and including the point of error.
227PARAMETER OUT OF RANGE
The specified value for the PAGEWIDTH or PAGELENGTH control is out of the acceptable range. The command line is displayed up to and including the point of error.
228RAMSIZE PARAMETER OUT OF RANGE
The specified value for the RAMSIZE control is out of the acceptable range. The command line is displayed up to and including the point of error.
229INTERNAL PROCESS ERROR
Lx51 detects an internal processing error. Please contact your dealer.
230START ADDRESS SPECIFIED MORE THAN ONCE
The invocation line contains more than one start address for unnamed segment group. The command is displayed up to and including the point of error.
231ADDRESS RANGE FOR BANKAREA INCORRECT
The address space specified with the BANKAREA control is invalid.
232APPLICATION CONTAINS TOO MANY RECURSIONS
The application contains to many recursive calls. Refer to “RECURSIONS” on page 356 for more information.
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
373 |
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Error |
Error Message and Description |
|
|
|
|
|
|
233 |
ILLEGAL USE OF * IN OVERLAY CONTROL |
|
|
9 |
|
|
|
|
The use of “* ! *” or “* ~ *” with the OVERLAY control is illegal. |
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
234USE RTX251 OR RTX51 CONTROL
The application uses RTXx51 tasks.
233ILLEGAL USE OF * IN OVERLAY CONTROL
command line
The use of “* ! *” or “* ~ *” with the OVERLAY control is illegal.
234USE RTX-251 SWITCH
The application uses a real-time operating system RTX251 Full or RTX251 Tiny. The L251 linker/locater must be invoked with the RTX251 or RTX251TINY control.
235TOO MANY ADDRESS RANGES
You are using to many address ranges.
236ADDRESSES ARE NOT IN ASCENDING ORDER
The address range does not contain addresses in ascending order.
237INVALID CLASS NAME
The class name given in the CLASSES control is not valid.
238BIT ADDRESS INVALID FOR THIS CLASS TYPE
The CLASSES control contains a bit address for a memory class which cannot be used for bit objects.
239BASE ADDRESS ALREADY GIVEN FOR THIS CLASS
The CLASSES control contains a base address, but the class has already a base address specified with a previous CLASSES control.
240BASE ADDRESS MUST BE THE FIRST ARGUMENT
The base address must be the first argument in the CLASSES control.
241BASE ADDRESS CANNOT BE GIVEN FOR THIS CLASS
A base address cannot be given for this memory class in the CLASSES control.
242WRONG SYNTAX FOR THE EXECUTION ADDRESS
The execution address field contains a wrong syntax.
243EXECUTION ADDRESS REQUIRED IF SPACE IS NOT RESERVED
You need to specify an execution address, if the execution space should not be reserved.
|
374 |
|
|
Chapter 9. Linker/Locator |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Error |
Error Message and Description |
|
|
9 |
|
|
244 |
OVERLAPPING CLASS RANGE |
|
|
|
|
|
The address ranges in the classes control are overlapping. |
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
245ADDRESS RANGE INVALID FOR THIS CLASS TYPE
The address range given in the CLASSES control is not valid for this memory class type.
246SYMBOL SPECIFIED MORE THAN ONCE
The symbol name is already used.
249MODULE USES AN UNKNOWN OMF VERSION
MODULE: filename (modulename)
The module uses an un-known or unsupported OMF version.
250CODE SIZE LIMIT IN RESTRICTED VERSION EXCEEDED
You are using modules that are created with an evaluation version or a code size limited version and the size limit is exceeded.
251RESTRICTED MODULE IN LIBRARY NOT SUPPORTED
A library contains a module that is created with an evaluation version or a code size limited version. This is not supported.