F0520003 |
[Message] |
#include file "file" includes itself. |
[Explanation] |
#include file "file" includes itself. Correct the error. |
F0520004 |
[Message] |
Out of memory. |
[Action by User] |
Out of memory. Close other applications, and perform the compile again. |
F0520005 |
[Message] |
Could not open source file "file". |
F0520013 |
[Message] |
Expected a file name. |
F0520035 |
[Message] |
#error directive: character string |
[Explanation] |
There is an "#error" directive in the source file. |
F0520143 |
[Message] |
Program too large or complicated to compile. |
F0520163 |
[Message] |
Could not open temporary file file name. |
F0520164 |
[Message] |
Name of directory for temporary files is too long file name. |
F0520182 |
[Message] |
Could not open source file file name (no directories in search list). |
F0520189 |
[Message] |
Error while writing "file" file. |
F0520563 |
[Message] |
Invalid preprocessor output file. |
F0520564 |
[Message] |
Cannot open preprocessor output file. |
F0520571 |
[Message] |
Invalid option: option |
F0520642 |
[Message] |
Cannot build temporary file name. |
F0520920 |
[Message] |
Cannot open output file: file name. |
F0523029 |
[Message] |
Cannot open rule file |
[Explanation] |
The file specified in the -Xmisra2004="file name" or -Xmisra2012="file name" option cannot be opened. |
F0523030 |
[Message] |
Incorrect description "file name" in rule file |
[Explanation] |
The file specified in the -Xmisra2004="file name" or -Xmisra2012="file name" option includes illegal code. |
F0523031 |
[Message] |
Rule "rule number" is unsupported |
[Explanation] |
The number of a rule that is not supported was specified. |
F0523054 |
[Message] |
regID is out of range |
[Action by User] |
Specify an usable value as regID. |
F0523055 |
[Message] |
selID is out of range |
[Action by User] |
Specify an usable value as selID. |
F0523056 |
[Message] |
NUM is out of range |
[Explanation] |
A value that is not usable as NUM in __set_il_rh(NUM, ADDR) was specified. |
F0523061 |
[Message] |
argument is incompatible with formal parameter of intrinsic function |
F0523062 |
[Message] |
return value type does not match the intrinsic function |
F0523073 |
[Message] |
core name does not support this intrinsic function. |
[Explanation] |
An intrinsic function not usable in the specified core was used. |
F0523089 |
[Message] |
Cannot read file "file name". |
F0530320 |
[Message] |
Duplicate symbol "symbol name". |
F0530321 |
[Message] |
Section "section name" conflicts. |
F0530800 |
[Message] |
Type of symbol "symbol-name" differs between files. |
F0530808 |
[Message] |
Alignment of variable "variable-name" differs between files. |
F0530810 |
[Message] |
#pragma directive for symbol "symbol-name" differs between files. |
F0533015 |
[Message] |
Symbol table overflow. |
[Explanation] |
The number of symbols generated by the compiler exceeded the limit. |
F0533021 |
[Message] |
Out of memory. |
[Explanation] |
Memory is insufficient. |
[Action by User] |
Close other applications and recompile the program. |
F0533301 |
[Message] |
Cannot close an intermediate file. |
[Explanation] |
A temporary file that was internally generated by the compiler cannot be closed. |
F0533302 |
[Message] |
Cannot read an intermediate file. |
[Explanation] |
An error occurred during reading of a temporary file. |
F0533303 |
[Message] |
Cannot write to an intermediate file. |
[Explanation] |
An error occurred during writing of a temporary file. |
F0533306 |
[Message] |
Compilation was interrupted. |
[Explanation] |
During compilation, an interrupt due to entry of the Cntl + C key combination was detected. |
F0533330 |
[Message] |
Cannot open an intermediate file. |
[Explanation] |
A temporary file that was internally generated by the compiler cannot be opened. |
F0540027 |
[Message] |
Cannot read file "file-name". |
F0540204 |
[Message] |
Illegal stack access. |
[Explanation] |
Attempted usage of the stack by a function has exceeded 2 Gbytes. |
F0540300 |
[Message] |
Cannot open an intermediate file. |
[Explanation] |
A temporary file that was internally generated by the compiler cannot be opened. |
F0540301 |
[Message] |
Cannot close an intermediate file. |
[Explanation] |
A temporary file that was internally generated by the compiler cannot be closed. |
F0540302 |
[Message] |
Cannot read an intermediate file. |
[Explanation] |
An error occurred during reading of a temporary file. |
F0540303 |
[Message] |
Cannot write to an intermediate file. |
[Explanation] |
An error occurred during writing of a temporary file. |
F0540400 |
[Message] |
Different parameters are set for the same #pragma "identifier". |
F0550503 |
[Message] |
Cannot open file file. |
[Action by User] |
Check the file. |
F0550504 |
[Message] |
Illegal section kind. |
[Action by User] |
Check the section type specification. |
F0550505 |
[Message] |
Memory allocation fault. |
[Action by User] |
Check free memory. |
F0550506 |
[Message] |
Memory allocation fault (string). |
[Action by User] |
Check free memory. |
F0550507 |
[Message] |
Overflow error (string). |
[Explanation] |
Ran out of working space while processing the expression. Change it to a simpler expression. |
[Action by User] |
Check the expression. |
F0550508 |
[Message] |
identifier undefined. |
[Action by User] |
Check the identifier. |
F0550509 |
[Message] |
Illegal pseudo(string) found. |
[Action by User] |
Check the directive. |
F0550510 |
[Message] |
string unexpected. |
[Action by User] |
Check the directive. |
F0550511 |
[Message] |
string unmatched. |
[Action by User] |
Check the conditional assembly control instruction. |
F0550512 |
[Message] |
$if, $ifn, etc. too deeply nested. |
[Explanation] |
4294967294 or more levels of nesting have been used in the conditional assembly control instruction. |
[Action by User] |
Check the nesting. |
F0550513 |
[Message] |
Unexpected EOF in string. |
[Explanation] |
There is no .endm directive corresponding to string directive. |
[Action by User] |
Check the directive. |
F0550514 |
[Message] |
Argument table overflow. |
[Explanation] |
4294967294 or more actual parameters have been used. |
[Action by User] |
Check the actual arguments. |
F0550516 |
[Message] |
Local symbol value overflow. |
[Explanation] |
The number of symbols generated automatically via the .local directive exceeds the maximum limit (4294967294). |
[Action by User] |
Check the directive. |
F0550531 |
[Message] |
Too many symbols. |
[Explanation] |
The maximum number of symbols that can be included in a single file has been exceeded. The maximum number of symbols that can be included is 4294967294, including symbols registered internally by the assembler. |
F0550532 |
[Message] |
Illegal object file (string). |
[Explanation] |
A file system-dependent error occurred while generating a linkable object file. |
[Action by User] |
Check the file system. |
F0550534 |
[Message] |
Too many instructions of one file. |
[Explanation] |
The maximum number of instructions for one file has been exceeded. The maximum is 10,000,000. |
[Action by User] |
Check the number of instructions. |
F0550537 |
[Message] |
Section(section) address overflowed out of range. |
[Explanation] |
The address of the absolute address section is beyond 0xffffffff. |
[Action by User] |
When you use .org to specify an absolute address for a section, the final instruction within the section must be allocated to an address up to 0xffffffff. |
F0550538 |
[Message] |
Section(section1) overlaps section(section2). |
[Explanation] |
The address range allocated to an absolute address section overlaps with the address range allocated to another section. |
[Action by User] |
Check the address specified with .org. |
F0550539 |
[Message] |
Relocation entry overflow. |
[Explanation] |
There are 16777216 or more symbols that have been registered and referenced. |
[Action by User] |
Check the number of symbols. |
F0550540 |
[Message] |
Cannot read file file. |
[Explanation] |
Illegal file, or file size is too long. |
[Action by User] |
Check the file. |
F0551608 |
[Message] |
Specify addresses. |
F0551609 |
[Message] |
Unreasonable include file nesting. |
[Explanation] |
The nesting level of the include is too deep or the function is recursively including itself. |
[Action by User] |
Review the include file. |
F0551610 |
[Message] |
Unreasonable macro nesting. |
[Explanation] |
The nesting level of the macro call is too deep or the function is recursively calling itself. |
[Action by User] |
Review the macro definition. |
F0563000 |
[Message] |
No input file |
[Explanation] |
There is no input file. |
F0563001 |
[Message] |
No module in library |
[Explanation] |
There are no modules in the library. |
F0563002 |
[Message] |
Option "option1" is ineffective without option "option2" |
[Explanation] |
The option option1 requires that the option option2 be specified. |
F0563003 |
[Message] |
Illegal file format "file" |
F0563004 |
[Message] |
Invalid inter-module optimization information type in "file" |
[Explanation] |
The file contains an unsupported link-time(inter-module) optimization information type. |
[Action by User] |
Check if the compiler and assembler versions are correct. |
F0563020 |
[Message] |
No cpu information in input files |
[Explanation] |
The CPU type cannot be identified from the input file. |
[Action by User] |
Check that the binary file is specified with the -binary option and the .obj or .rel files to be linked together exist. |
F0563100 |
[Message] |
Section address overflow out of range : "section" |
[Explanation] |
The address of section exceeded the area available. |
[Action by User] |
Change the address specified by the start option.
For details of the address space, see the user's manual of the device. |
F0563102 |
[Message] |
Section contents overlap in absolute section "section" [V1.05.00 or earlier]
Section contents overlap in absolute section "section" in "file" [V1.06.00 or later] |
[Explanation] |
Data addresses overlap within an absolute address section. |
[Action by User] |
Modify the source program. |
F0563103 |
[Message] |
Section size overflow : "section-name" |
[Explanation] |
Section "section-name" has exceeded the usable size. |
F0563110 |
[Message] |
Illegal cpu type "cpu type" in "file" |
[Explanation] |
A file with a different cpu type was input. |
F0563111 |
[Message] |
Illegal encode type "endian type" in "file" |
[Explanation] |
A file with a different endian type was input. |
F0563112 |
[Message] |
Invalid relocation type in "file" |
[Explanation] |
There is an unsupported relocation type in file. |
[Action by User] |
Ensure the compiler and assembler versions are correct. |
F0563115 |
[Message] |
Cpu type in "file" is not supported |
[Explanation] |
The CPU type specified in "file" is not supported. Check if the input file is correct. |
F0563150 |
[Message] |
Multiple files cannot be specified while processing "process" |
F0563200 |
[Message] |
Too many sections |
[Explanation] |
The number of sections exceeded the translation limit. It may be possible to eliminate this problem by specifying multiple file output. |
F0563201 |
[Message] |
Too many symbols |
[Explanation] |
The number of symbols exceeded the translation limit. It may be possible to eliminate this problem by specifying multiple file output. |
F0563202 |
[Message] |
Too many modules |
[Explanation] |
The number of modules exceeded the translation limit. |
[Action by User] |
Divide the library. |
F0563203 |
[Message] |
Reserved module name "rlink_generates" |
[Explanation] |
rlink_generates_** (** is a value from 01 to 99) is a reserved name used by the optimizing linkage editor. It is used as an .obj or .rel file name or a module name within a library. |
[Action by User] |
Modify the name if it is used as a file name or a module name within a library. |
F0563204 |
[Message] |
Reserved section name "$sss_fetch" |
[Explanation] |
sss_fetch** (sss is any string, and ** is a value from 01 to 99) is a reserved name used by the optimizing linkage editor. |
[Action by User] |
Change the symbol name or section name. |
F0563300 |
[Message] |
Cannot open file : "file" |
[Explanation] |
file cannot be opened. |
[Action by User] |
Check whether the file name and access rights are correct. |
F0563301 |
[Message] |
Cannot close file : "file" |
[Explanation] |
file cannot be closed. There may be insufficient disk space. |
F0563302 |
[Message] |
Cannot write file : "file" |
[Explanation] |
Writing to file is not possible. There may be insufficient disk space. |
F0563303 |
[Message] |
Cannot read file : "file" |
[Explanation] |
file cannot be read. An empty file may have been input, or there may be insufficient disk space. |
F0563310 |
[Message] |
Cannot open temporary file |
[Explanation] |
A temporary file cannot be opened. |
[Action by User] |
Check to ensure the HLNK_TMP specification is correct, or there may be insufficient disk space. |
F0563314 |
[Message] |
Cannot delete temporary file |
[Explanation] |
A temporary file cannot be deleted. There may be insufficient disk space. |
F0563320 |
[Message] |
Memory overflow |
[Explanation] |
There is no more space in the usable memory within the optimizing linker. |
[Action by User] |
Increase the amount of memory available. |
F0563410 |
[Message] |
Interrupt by user |
[Explanation] |
An interrupt generated by (Ctrl) + C keys from a standard input terminal was detected. |
F0563430 |
[Message] |
The total section size exceeded the limit of the evaluation version of version. Please consider purchasing the product. |
F0563431 |
[Message] |
Incorrect device type, object file mismatch. |
F0563600 |
[Message] |
Option "option" requires parameter |
F0563601 |
[Message] |
Invalid parameter specified in option "option" : "parameter" |
F0563602 |
[Message] |
"character string" option requires "edition". |
[Explanation] |
The "character string" option requires the "edition". |