"path" specified by the "character string" option is a file. Specify a folder. |
|||||||
The folder "folder" specified by the "character string" option is not found. |
|||||||
The "character string2" option is ignored when the "character string1" option is specified at the same time. |
|||||||
The "-Xfloat" option is ignored because specified device does not have FPU. |
|||||||
"-C" option and "-Xcommon" option is mismatch. Instruction set by "character string1" option is ignored. Create common object for "character string2" instruction set. |
|||||||
"symbol name" specified in the "character string" option is not allowed for a preprocessor macro. |
|||||||
The "character string" option is specified more than once. The latter is valid. |
|||||||
The "character string2" option is ignored when the "character string1" option and the "character string2" option are inconsistent. |
|||||||
The "character string2" option is ignored when the "character string1" option is not specified. |
|||||||
Optimization itemoptions were cleared when "-Ocharacter string" option is specified. Optimization itemoptions need to specify after "-Ocharacter string" option. |
|||||||
Device file is not found in the folder specified by the "-Xdev_path" option. |
|||||||
Device file is not found in the folder specified by the "-Xdev_path" option. Will search standard device file folder. |
|||||||
"code" is invalid in the "language specifications (C or C++)". |
|||||||
"option-name" option is ignored due to the specification of another option. |
|||||||
"code" is ignored in the "language specifications (C or C++)". |
|||||||
Nothing to compile, assemble or link.(input and output combination) |
|||||||
The evaluation version is valid for the remaining number days. |
|||||||
The number of remaining days as the evaluation version is displayed. Register the license key of CC-RL. |
|||||||
Type qualifiers are meaningless in this declaration. Ignored. |
|||||||
Too many characters in character constant. Character constants cannot contain more than one character. |
|||||||
Since there is a preceding #else, this directive is illegal. |
|||||||
Shift count is negative. The behavior will be undefined in ANSI-C. |
|||||||
Storage class is not first. Specify the declaration of the storage class first. |
|||||||
A value of type "type1" cannot be used to initialize an entity of type "type2". |
|||||||
Declaration is incompatible with "declaration" (declared at line number). |
|||||||
Argument of type "type1" is incompatible with parameter of type "type2". |
|||||||
External/internal linkage conflict with previous declaration. |
|||||||
Floating-point value does not fit in required integral type. |
|||||||
Argument is incompatible with corresponding format string conversion. |
|||||||
A pointer to a bound function may only be used to call the function. |
|||||||
Declaring a void parameter list with a typedef is nonstandard. |
|||||||
A value of type "type1" cannot be assigned to an entity of type "type2". |
|||||||
Pointless comparison of unsigned integer with a negative constant. |
|||||||
Handler is potentially masked by previous handler for type "type". |
|||||||
Omission of exception specification is incompatible with previous name. |
|||||||
Transfer of control bypasses initialization of: type "symbol" (declared at line number). |
|||||||
name will not be called for implicit or explicit conversions. |
|||||||
Overloaded virtual function name1 is only partially overridden in name2. |
|||||||
Inline specification is incompatible with previous "symbol". |
|||||||
Using out-of-scope declaration of type "symbol" (declared at line number). |
|||||||
xxx, required for copy that was eliminated, is inaccessible. |
|||||||
xxx, required for copy that was eliminated, is not callable because reference parameter cannot be bound to rvalue. |
|||||||
Using-declaration ignored -- it refers to the current namespace. |
|||||||
Reference is to symbol1 -- under old for-init scoping rules it would have been symbol2. |
|||||||
Template parameter %sq may not be used in an elaborated type specifier. |
|||||||
Specifying a default argument when redeclaring an unreferenced function template is nonstandard. |
|||||||
Omission of exception specification is incompatible with name. |
|||||||
const object requires an initializer -- class type has no explicitly declared default constructor. |
|||||||
xxx has no corresponding operator deleteyyy (to be called if an exception is thrown during initialization of an allocated object). |
|||||||
Declaration of "size_t" does not match the expected type "type". |
|||||||
Ambiguous class member reference -- symbol1 used in preference to symbol2. |
|||||||
enum bit-fields are always unsigned, but enum %t includes negative enumerator. |
|||||||
Nonstandard local-class friend declaration -- no prior declaration in the enclosing scope. |
|||||||
Declared size for bit field is larger than the size of the bit field type; truncated to any-string bits. |
|||||||
Use of a type with no linkage to declare a variable with linkage. |
|||||||
operator new and operator delete cannot be given internal linkage. |
|||||||
Subtraction of pointer types "type name1" and "type name2" is nonstandard. |
|||||||
function2 is hidden by function1 -- virtual function override intended? |
|||||||
A variable with static storage duration cannot be defined within an inline function. |
|||||||
Standard requires that "symbol" be given a type by a subsequent declaration ("int" assumed). |
|||||||
type1 would have been promoted to "type2" when passed through the ellipsis parameter; use the latter type instead. |
|||||||
va_start should only appear in a function with an ellipsis parameter. |
|||||||
The prototype declaration of %nfd is ignored after this unprototyped redeclaration. |
|||||||
Nonstandard conversion between pointer to function and pointer to data. |
|||||||
Constant is too large for long long; given unsigned long long type (nonstandard). |
|||||||
xxx declares a non-template function -- add <> to refer to a template instance. |
|||||||
Fixed-point value implicitly converted to floating-point type. |
|||||||
Implicit conversion of a 64-bit integral type to a smaller integral type (potential portability problem). |
|||||||
Explicit conversion of a 64-bit integral type to a smaller integral type (potential portability problem). |
|||||||
Conversion from pointer to same-sized integral type (potential portability problem). |
|||||||
White space between backslash and newline in line splice ignored. |
|||||||
Some enumerator values cannot be represented by the integral type underlying the enum type. |
|||||||
Multicharacter character literal (potential portability problem). |
|||||||
No #pragma start_map_region is currently active: pragma ignored. |
|||||||
#pragma text must precede the definition of function "function". |
|||||||
#pragma text must precede the definition of function "function". The specification will be ignored. |
|||||||
#pragma character string coflicts with previous #pragma for this function "function". |
|||||||
Unrecognized symbol information "character string" is ignored. |
|||||||
"variable" has already been placed into "section" section in symbol file. The latter is ignored. |
|||||||
"variable" has already been placed into "section" section in symbol file. #pragma is ignored. |
|||||||
Definition at end of file not followed by a semicolon or a declarator. |
|||||||
The declaration at the end of the file lacked a semicolon to indicate its termination. |
|||||||
White space is required between the macro name "macro name" and its replacement text |
|||||||
Insert a space between the macro name and the text to be replaced. |
|||||||
Using "function item" function at influence the code generation of "SuperH" compiler |
|||||||
The use of "function item" may affect compatibility with the SuperH compiler. Confirm details of differences in the specification. |
|||||||
The same identifier was declared several times and different sections were specified for individual declarations. Only the first section declaration is valid. |
|||||||
argument is incompatible with formal parameter of intrinsic function |
|||||||
Address taken "variable-name". It may cause an upset endian indirect reference. |
|||||||
The address of an 8-byte variable "variable name", which was in the different endian from that specified by the endian option, was acquired. This may lead to an indirect reference with incorrect handling of endian. |
|||||||
The function is declared in a different format from the prototype. A function declaration in a format different from the prototype may degrade the efficiency when passing a near pointer as an argument. |
|||||||
This function call uses a function type without a prototype. When the defining function has a prototype, a mismatch may occur in passing of arguments. The call being made via the function pointer means that there is no prototype for the function pointer type. |
|||||||
Pointer to the object of even alignment holds the odd address |
|||||||
const qualifier for variable "variable-name" differs between files. |
|||||||
-Xswitch=table option is ignored, because the branch table for switch is overflow. |
|||||||
The branch table for switch is overflow. The -Xswitch=table option will be ignored if the difference between the maximum and minimum label values is greater than 8192. |
|||||||
Alignment of "section-name" sections is inconsistent. "value" is assumed. |
|||||||
There is an error in section naming. The same section name is specified for sections with different alignment numbers. |
|||||||
Endian of "section-name" sections is inconsistent. "endian type" is assumed. |
|||||||
There is an error in section naming. The same section name is specified for sections in different endian. |
|||||||
option option is not supported for core core. The option specification will be ignored. |
|||||||
Cannot find programmable peripheral I/O registers, ignored -Xprogrammable_io option. |
|||||||
Illegal displacement in inst instruction. Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
|||||||
Illegal operand (range error in immediate). Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
|||||||
Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
|||||||
Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
|||||||
Illegal register number, ignored. The invalid register will be ignored, and the assembly will continue. |
|||||||
The -C option is given precedence, and the target-device specified by the $PROCESSOR control instruction will be ignored. |
|||||||
string already specified, ignored. The previously specified number will be used. This specification will be ignored. |
|||||||
Duplicated option option, ignored. The previously specified option will be used. This specification will be ignored. |
|||||||
Start address of programmable io is out of range(0x0,value1-value2),ignored -Xprogrammable_io option. |
|||||||
Start address of programmable io is out of range(0x0,value1-value2),ignored -Xprogrammable_io option. The specified value will be ignored, and the initial value of the device will be used. |
|||||||
Illegal register number, aligned odd register(rXX) to be even register(rYY). |
|||||||
Odd-numbered registers (r1, r3, ... r31) have been specified. The only general-purpose registered that can be specified are even-numbered (r0, r2, r4, ... r30). Assembly will continue, assuming that even-numbered registers (r0, r2, r4, ... r30) have been specified. |
|||||||
The control control instruction differs from a previous specification. The previous specification will take precedence, and register modes specified by subsequent control control instructions will be ignored. |
|||||||
Duplicated reg_mode, ignored $REG_MODE. The "-Xreg_mode" option takes precedence, and register modes specified via the $REG_MODE control instruction will be ignored. |
|||||||
Can not use r0 as destination in mul/mulu in device-name core. |
|||||||
The use of the cache instruction as cll is not recommended. Use the cll instruction. |
|||||||
"path-name" specified by the "character string" option is a file. Specify a folder. |
|||||||
The folder "folder-name" specified by the "character string" option is not found. |
|||||||
The "character string2" option is ignored when the "character string1" option is specified at the same time. |
|||||||
"-C" option and "-Xcommon" option is mismatch. Instruction set by "character string1" option is ignored. Create common object for "character string2" instruction set. |
|||||||
"character string1" specified in the "character string2 option is not allowed for a preprocessor macro. Recognized only as an assembler symbol |
|||||||
The "character string" option is specifiedmore than once. The latter is valid. |
|||||||
The "character string2" option is ignored when the "character string1" option and the "character string2" option are inconsistent. |
|||||||
The "character string2" option is ignored when the "character string1" option is not specified. |
|||||||
Device file is not found in the folder specified by the "-Xdev_path" option. |
|||||||
Device file is not found in the folder specified by the "-Xdev_path" option. The compiler will search for the device file in the standard device-file folder. |
|||||||
Directive command .ALIGN is written in a section that does not have an ALIGN specification. |
|||||||
Check the position where directive command .ALIGN is written. Write an ALIGN specification in the section definition line of a section in which directive command .ALIGN is written. |
|||||||
The jump address can be a position that differs from an anticipated destination. |
|||||||
When writing an address in a branch instruction operand using a location symbol for offset, be sure to write the addressing mode, jump distance, and instruction format specifiers for all mnemonics at locations from that instruction to the jump address. |
|||||||
Check the floating-point value written in the source code. The value out of range is ignored. |
|||||||
Check the value of the operand in .ORG. Correct the source code. |
|||||||
The specified boundary alignment value does not match the other settings. |
|||||||
When endian=big is specified, the start address of the data area in the CODE section is aligned to a 4-byte boundary. |
|||||||
When endian=big is specified, the size of the data area in the CODE section is adjusted to a multiple of 4. |
|||||||
.STACK(stack value setting) is specified multiple times for a single symbol. |
|||||||
The specified section attribute does not match the other settings. |
|||||||
There are too many actual macro parameters. Extra macro parameters will be ignored. |
|||||||
The number of actual macro parameters is smaller than that of formal macro parameters. The formal macro parameters that do not have corresponding actual macro parameters are ignored. |
|||||||
The include file contains an .END statement. The software will ignore .END as it executes. |
|||||||
.END cannot be written in include files. Delete this statement. |
|||||||
Undefined global symbol "symbol" specified with "$EXT_FUNC". |
|||||||
Section "section" with section type(section type) not supported, ignored. |
|||||||
Input files have different register modes. use -Xregmode_info option for more information. |
|||||||
Illegal flash mask option access(file: "file" address:num1 bit:num2). |
|||||||
Section "section" alignment must be 4 in internal instruction RAM. |
|||||||
Section "section" attribute is illegal in internal ROM/internal instruction RAM. |
|||||||
Relocation entry in section "section" has unknown relocation type(number), ignored this entry. |
|||||||
Can not find numberth symbol table entry for relocation of reference at offset(offset) in "section" section, this relocation is ignored. |
|||||||
Relocation entry in relocation section "section1" used to relocate section "section2" has illegal r_offset(offset), ignored. |
|||||||
Can not find GP-symbol in segment "segment" of illegal label reference for local symbol in file "file2" (section:section2, offset;offset, type:relocation type).local symbol is allocated in section "section1" (file:file1). |
|||||||
Can not find GP-symbol in segment "segment" of illegal label reference for symbol "symbol" in file "file2" (section:section2, offset;offset, type:relocation type). "symbol" is allocated in section "section1" (file:file1). |
|||||||
Can not find GP-symbol in section "section" of file "file1" or illegal label reference for symbol "symbol" in file "file2" (section:section2, offset;offset, type:relocation type). "symbol" is allocated in section "section1" (file:file1). |
|||||||
Relocated value(value) of relocation entry(file:file, section:section, offset:offset, type:relocation type) for branch command become odd value. |
|||||||
Relocated value(value) of relocation entry(file:file, section:section, offset:offset, type:relocation type) for load/store command become odd value. |
|||||||
Symbol "symbol" (output section section1)is too far from output section "section2". (value:value, file:file input section:section3, offset;offset, type:relocation type) |
|||||||
Output section "section1" is too far from output section "section2". (value:value, file:file input section:section3, offset;offset, type:relocation type) |
|||||||
Output section "section1" overflowed or illegal label reference for symbol "symbol" in file "file". (value:value, input section:section2, offset;offset, type:relocation type). "symbol" is allocated in section "section1" (file:file) |
|||||||
Output section "section1" overflowed or illegal label reference for local symbol in file "file2". (value:value, input section:section2, offset;offset, type:relocation type). local symbol is allocated in section "section1" (file:file1) |
|||||||
Segment "segment" overflowed highest address of target machine. |
|||||||
"stirng" in segment directive is illegal when "-Xrelinkable_object" option specified, ignored. |
|||||||
No LOAD segments exist for mapping input section "section" in file "file". this section is mapped to non-LOAD *DUMMY* segment with no program header. |
|||||||
"stirng"is illegal in 1pass-mode, ignored, try in 2pass-mode ( "-Xtwo_pass_link"option). |
|||||||
"stirng" is illegal when "-Xalign_fill" option specified, ignored value of "stirng" |
|||||||
stringsymbol multiply defined to segment "segment", first defined symbol "symbol" used. |
|||||||
stringsymbol multiply defined, first defined symbol "symbol" used. |
|||||||
Segment "segment"(number1-number2) must be in string-relative-addressable range(number3-number4). |
|||||||
Segment "segment"(number1-number2) overflowed highest or lowest address of internal memory (number3-number4). |
|||||||
Segment "segment" (number1-number2) overlaps guarded area (number3-number4) |
|||||||
Segment "segment" (number1-number2) overlaps programmable peripheral I/O area (number3-number4) |
|||||||
Must be specified in link directive is illegal when address of segment "segment" is not specified. |
|||||||
"string1" option is illegal when "string2" option is specified, ignored "string1" option. |
|||||||
"stiring" option aligned odd value(value1) to be even value(value2). |
|||||||
Segment sort function is active, because new vector type exist in device file. |
|||||||
option1 and option2 cannot be specified simultaneously. option1 is ignored. |
|||||||
option and the option to divide the output file cannot be specified simultaneously. option is ignored. The first input file name is used as the output file name. |
|||||||
Fatal level message cannot be changed to other level : "number" |
|||||||
The level of an abort error message cannot be changed. The specification of number is ignored. Only errors at the information/warning/error level can be changed with the change_message option. |
|||||||
Subcommand file terminated with end option instead of exit option |
|||||||
There is no processing specification following the end option. Processing is done with the exit option assumed. |
|||||||
Duplicate specifications of option were found. Only the last specification is effective. |
|||||||
option was used to specify the same file twice. The second specification is ignored. |
|||||||
option was used to specify the same module twice. The second specification is ignored. |
|||||||
Duplicate symbol/section specified in option "option" : "name" |
|||||||
option was used to specify the same symbol name or section name twice. The second specification is ignored. |
|||||||
option was used to specify the same error number. Only the last specification is effective. |
|||||||
Section "section" is already defined by -Xrompsec_data option and therefor this section is ignored. |
|||||||
Section "section" is already defined by -Xrompsec_text option and therefor this section is ignored. |
|||||||
The symbol name or section name specified in option cannot be found. name specification is ignored. |
|||||||
"name" in rename option conflicts between symbol and section |
|||||||
name specified by the rename option exists as both a section name and as a symbol name. |
|||||||
The symbol specified by option has already been defined. Processing is continued without any change. |
|||||||
Invalid address value specified in option "option" : "address" |
|||||||
address specified by option is invalid. address specification is ignored. |
|||||||
A symbol other than symbol specified by the entry option is specified as the entry symbol on compiling or assembling. The option specification is given priority. |
|||||||
section has no addresses specified for it. section will be located at the rearmost address. |
|||||||
Specify the address of the section using the rlink option "-start". |
|||||||
Address cannot be assigned to absolute section "section" in start option |
|||||||
section is an absolute address section. An address assigned to an absolute address section is ignored. |
|||||||
Section address in start option is incompatible with alignment : "section" |
|||||||
The address of section specified by the start option conflicts with memory boundary alignment requirements. The section address is modified to conform to boundary alignment. |
|||||||
When the -selfw option is specified, the section is allocated to area. |
|||||||
When the -ocdtrw option is specified, the section is allocated to area. |
|||||||
When the -ocdhpiw option is specified, the section is allocated to area. |
|||||||
When the -selfw option is specified, the CRC result is placed in area. |
|||||||
When the -ocdtrw option is specified, the CRC result is placed in area. |
|||||||
When the -ocdhpiw option is specified, the CRC result is placed in area. |
|||||||
Section attribute mismatch in rom option : "section1,section2" |
|||||||
The attributes and boundary alignment of section1 and section2 specified by the rom option are different. The larger value is effective as the boundary alignment of section2. |
|||||||
Load address overflowed out of record-type in option "option" |
|||||||
A record type smaller than the address value was specified. The range exceeding the specified record type has been output as different record type. |
|||||||
Cannot fill unused area from "address" with the specified value |
|||||||
Specified data cannot be output to addresses higher than address because the unused area size is not a multiple of the value specified by the space option. |
|||||||
The symbol which is a pair of symbol indicating the range of the empty area could not be found. |
|||||||
The section specified in option does not have an externally defined symbol. |
|||||||
Directive command "control directive" is duplicated in "file" |
|||||||
control directive is written in multiple source files. The control directive cannot be written more than once across files. |
|||||||
Failed to write type of output code to the output file. The output file may not contain the address to which type of output code should be output. |
|||||||
The input file contains vector table section. The optimizing linker does not create section automatically. |
|||||||
Interrupt number "vector number" of "section" is defined in input file |
|||||||
The vector number specified by the VECTN option is defined in the input file. Processing is continued with priority given on the definition in the input file. |
|||||||
Interrupt number "vector number" of "section" is defined in input file |
|||||||
The vector number in the -debug_monitor option has already been defined in the input file or -vectn option. Continue processing with priority given to the specification of the -debug_monitor option. |
|||||||
Section "section" was moved other area specified in option "cpu=<attribute>" |
|||||||
The object size was modified through optimization of access to external variables. Accordingly, section in the area specified by the next cpu specification was moved. |
|||||||
Area of "FIX" is within the range of the area specified by "cpu=<attribute>" :"<start>-<end>" |
|||||||
In the cpu option, the address range of <start>-<end> specified for FIX overlapped with that specified for another memory type. The setting for FIX is valid. |
|||||||
section name, which is a data section without an initial value, cannot be initialized by the initial setup program. |
|||||||
Check the address range specified with -cpu and the sizes of pointer variables. |
|||||||
Section "section name" specified in option "option" is ignored |
|||||||
option specified for the section newly created due to -cpu=stride is invalid. |
|||||||
Section "section" in relocation "file"-"section"-"offset" is changed |
|||||||
The relocation section file offset now refers to a location in the new section created with the division of section. |
|||||||
To prevent division, declare the contiguous_section option for section. |
|||||||
Input file file1 was overwritten. A backup copy of the data in the previous version of file1 was saved in file2. |
|||||||
There is no debugging information in the input files. The "option" has been ignored. |
|||||||
Check whether the relevant option was specified at compilation or assembly. |
|||||||
No inter-module optimization information is present in the input files. The optimize option has been ignored. |
|||||||
Check whether the goptimize option was specified at compilation or assembly. |
|||||||
No stack information is present in the input files. The stack option is ignored. If all input files are assembler output files, the stack option is ignored. |
|||||||
An unsupported section was present in file. section has been ignored. |
|||||||
Debugging information in file is not dwarf2. The debugging information has been deleted. |
|||||||
The symbol named symbol is duplicated. The symbol in the first file input is given priority. |
|||||||
Multiple object files containing more than one entry symbol definition were input. Only the entry symbol in the first file input is effective. |
|||||||
Sections with the same name but different boundary alignments were input. Only the largest boundary alignment specification is effective. |
|||||||
Sections with the same name but different attributes were input. If they are an absolute section and relative section, the section is treated as an absolute section. If the read/write attributes mismatch, both are allowed. |
|||||||
Common symbols or defined symbols with different sizes were input. A defined symbol is given priority. In the case of two common symbols, the symbol in the first file input is given priority. |
|||||||
The attribute of symbol in file does not match the attribute of the same-name symbol in other files. |
|||||||
Section alignment in option "aligned_section" is small : "section" |
|||||||
Since the boundary alignment value specified for aligned_section is 16 which is smaller than that of section, the option settings made for that section are ignored. |
|||||||
The attribute of the allocation border of section of file differs from the others. |
|||||||
Since it is possible that the 64-K or (64K-1) byte boundary may be exceeded by optimization, the -start option specification is split at the start of section. |
|||||||
Optimization is not available when parentheses "( )" are specified in the start option. Optimization has been disabled. |
|||||||
Cannot optimize "file"-"section" due to multi label relocation operation |
|||||||
A section having multiple label relocation operations cannot be optimized. Section section in file has not been optimized. |
|||||||
Cannot generate effective bls file for compiler optimization |
|||||||
An invalid bls file was created. This optimization is not available even if optimization of access to external variables (map option) is specified for compilation. |
|||||||
The optimization of access to external variables (map option) in the compiler has the following restriction. Check if this restriction is applicable and modify the section allocation. Access to external variables cannot be optimized in some cases if a data section is allocated immediately after a data section when the base option is specified for compilation. Note: The bls file indicates the external symbol allocation information file. It contains the information to be used for the map option of the compiler. |
|||||||
There is no stack section, and so consistency of the stack size specified by the stack option on compiling cannot be checked. |
|||||||
To check the consistency of the stack size on compiling, the goptimize option needs to be specified on compiling and assembling. |
|||||||
The stack section size exceeded the stack size specified by the stack option on compiling. |
|||||||
Either change the option used on compiling, or change the program so as to reduce the use of the stack. |
|||||||
Different values for stack size are specified for multiple files. |
|||||||
Input file was compiled with option "smap" and option "map" is specified at linkage |
|||||||
The file with smap specification should not be compiled with the map option specification in the second build processing. |
|||||||
"user option byte/control value for the on-chip debug" in "section" created by device file |
|||||||
Check the option during compiling and the section specification of a source file. |
|||||||
-Xhex_symtab=global and -Xhex_symtab=all expect -Xhex_format=T. |
|||||||
-Xhex_symtab=all expect -Xhex_symtab=global and -Xhex_format=T. |
|||||||
Section "section" overflowed lowest address of internal memory. |
|||||||
Section "section" overflowed highest address of internal memory. |
|||||||
Section "section" overflowed lowest address of program memory. |
|||||||
The address of convert area exceeds the maximum value of the address that can be expressed in the Intel expanded hex format. |
|||||||
This message may be caused by one of the following.
Although the maximum address value is stated as 20 bits, it is actually in the vicinity of 20 bits. The 20-bit Intel extended hex-format address expression that is the cause of this message is calculated from the extended address record in the higher-order address, and the unique data record offset from there. If the higher-order address of the extended address record fits within 20 bits, then the address will be output successfully in Intel extended hex format even if the addition of the subsequent data record offset causes the result to be more than 20 bits, and it will not cause an error. |
|||||||
The address of convert area exceeds the maximum value of the address that can be expressed in the Motorola S type hex format (standard address). |
|||||||
This message may be caused by one of the following.
|
|||||||
The start address of convert area exceeds the maximum value of the address that can be expressed in the Intel expanded hex format. |
|||||||
This message may be caused by one of the following. (1) The section address is too large The address allocated to the section may be larger than the expressible range. Specify the start address of the area for hex conversion with the -Xhex_offset option, and offset from that address. (2) The value specified via the -Xhex_offset option is invalid It is possible handle the address as an offset from the specified value by specifying the -Xhex_offset option. The offset from this value may be larger than the expressible range. Specify an appropriate value. |
|||||||
The start address of convert area exceeds the maximum value of the address that can be expressed in the Motorola S type hex format (standard address). |
|||||||
This message may be caused by one of the following. (1) The section address is too large The address allocated to the section may be larger than the expressible range. Specify the start address of the area for hex conversion with the -Xhex_offset option, and offset from that address. (2) The value specified via the -Xhex_offset option is invalid It is possible handle the address as an offset from the specified value by specifying the -Xhex_offset option. The offset from this value may be larger than the expressible range. Specify an appropriate value. |
|||||||
"instance" was not decoded. The message is output using the encoding name. |
|||||||
If there is a subsequent file specified in the list file, then the applications proceeds to convert that file. |
|||||||
Input file specified on the command line is ignored when the "-l" option is specified. |
|||||||
A list file and input file cannot be specified simultaneously. The application will perform the conversions in the list file specified by the "-l" option, and the input file will be ignored. |
|||||||
The "-c" option specified on the command line is ignored when it does not match the specification in list file (file). |
|||||||
The list file and command line have different "-c" option specifications for the input file "file" specified in the list file. The conversion specified by the list file will be performed. |
|||||||
Cannot find input file 'file'. If there is a subsequent file specified in the list file, then the applications proceeds to convert that file. |
|||||||
The pre-conversion C-language source file could not be converted, because it contains an illegal #pragma statement. |
|||||||
Edit the C-language source file and correct any syntax errors. |
|||||||
Cannot convert __interrupt/__multi_interrupt inmacro definition. |
|||||||
Cannot convert __interrupt and __multi_interrupt described in the macro-definition. |
|||||||
Changed to a call from an assembly source, or declare the variable by adding the const qualifier. |
|||||||
Cannot find file(file name). Check that the specified file name is correct |
|||||||
Cannot open file to read(file name). Check that the file is readable. |
|||||||
Too many characters in one line in file (file name:line number). |
|||||||
Unknown function name (function name) in file(file name:line nember). Only functions explicitly referred to in the project are allowed. |
|||||||
The stack-size specification file specifies a function name not used in the project. Only functions that are defined in or directly called from a C source file can be specified. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Too long file name (file name) qualifying static function name in file(file name:line number). |
|||||||
The name of a file in which a static-function is defined (added in front of the static function in the stack-size specification file) is too long. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Too long function name (function name) in file (file name:line number). |
|||||||
The stack-size specification file contains a function name that is too long. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Illegal value (value) after "ADD=" in file (file name:line number). |
|||||||
The stack-size specification file contains an invalid added size specification. The added size must be in the format of "ADD=" followed by a decimal number, or a hexadecimal number preceded by "0x" or "0X". |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Multiple "ADD="s for one function in file (file name:line number). |
|||||||
The stack-size specification file contains an invalid added size specification. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Illegal value (value) after "RECTIME=" in file (file name:line number). |
|||||||
The stack-size specification file contains a specification of an invalid number of recursions. The number of recursions must be in the format of "RECTIME=" followed by a positive decimal number, or a positive hexadecimal number preceded by "0x" or "0X". |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Multiple "RECTIME="s for one function in file (file name:line number). |
|||||||
The stack-size specification file contains a specification of an invalid number of recursions. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Illegal "RECTIME=" for non-recursive function in file (file name:line number). |
|||||||
The stack-size specification file contains a specification of an invalid number of recursions. The "RECTIME=" recursion-count specification can only be used with recursive functions. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Missing function name after "CALL=" in file (file name:line number). |
|||||||
The stack-size specification file contains an invalid callee function specification. Specify "CALL=" followed by the function name. Functions that are not used in the project cannot be specified. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Multiple function names after "CALL=" in file (file name:line number). |
|||||||
The stack-size specification file contains an invalid callee function specification. "CALL=" can only specify one function. If you wish to specify more than one function, use the "CALL=" specification for each one. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Multiple specifications for one function in file (file name:line number1, line number2). |
|||||||
The stack-size specification file contains the same function on lines {line-number-1} and {line-number-2}. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Too many characters in one line in file (file name:line number). |
|||||||
The number of characters in line {line-number} of the stack-size specification file exceeds the maximum length (5,119). Reduce the callee function specifications. Even if you register all functions that are called, only the function with the largest stack size will be added to the stack size. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
The format of line line-number in the stack-size specification file is invalid. |
|||||||
Ignore the error and continue loading from the following line. Ignore the error and continue loading from the following line. Subsequent warnings of this type will be shown in the message display area, but this dialog box will not appear again. |
|||||||
Can not find stack size specification file for system library functions (file name). |
|||||||
No stack-size specification file was found for the standard library. The size information for skcx (same as default-file-name) will be used. |
|||||||
It may not have been installed correctly; try installing again. |
|||||||
Illegal format in stack size specification file for system library functions(file name:line number). |
|||||||
The format of the stack-size specification file for the standard library is invalid. |
|||||||
It may not have been installed correctly; try installing again. |
|||||||
A previous change to the stack size may not have been reflected. Check it, and configure it again if it is incorrect. |
|||||||
Cannot find CX generated assembly language source file. Select [Compile Options] tab in CubeSuite's property panel, and specify [Yes(-Xasm_path)] as [Output assembler source file] property in [Output File] category, then rebuild. |
|||||||
Perform the rebuild after doing the following: register a C source file in CubeSuite+; then from the Build Tool Property panel, select the [Compile Options] tab; next, under the [Output File] category, set the [Output assembler source file] property to [Yes(-Xasm_path)]. |
|||||||
Cannot find CX generated assembly language source file (file name). Check "Compiler Options" specified for the corresponding C source file and rebuild. |
|||||||
Perform the build after doing the following: from CubeSuite+, in the Property panel for the corresponding C source, select the [Individual Compile Options] tab; then under the [Output File] category, set the [Output assembler source file] property to [Yes(-Fs)]. |
|||||||
The format of line line-number in the intermediate assembler file is invalid. |
|||||||
The intermediate assembler file generated by CX may be missing. Check the file and rebuild. |
|||||||
Cannot accept CC name version generated assembler source module file. |
|||||||
The correct stack size cannot be calculated if a call to a runtime library or standard library is included, because the compiler version is out of date. |
|||||||
Assembler source module file for different device (file name). |
|||||||
Assembler source module file generated by different version of CC name(file name). |
|||||||
The assembly source module file was compiled using a different compiler version. |
|||||||
The project file is invalid. Check the file. This error occurs when the project file opened from the menu after startup is invalid. |
|||||||
Either change the function selection or output the largest path only. |
|||||||
Number of characters in one line reached limit(5119) in output. |
|||||||
The output result includes a line that is longer than 5,119 characters. Either change the function selection or output in text format. Text-format output will be displayed with line breaks. |
|||||||
The number of callee functions specified exceeds the limit. No more than 1,024 functions may be specified. Even if you register all functions that are called, only the function with the largest stack size will be added to the stack size. |
|||||||
The size configuration information exceeds the maximum number of characters (5,119). Reduce the callee function specifications. Even if you register all functions that are called, only the function with the largest stack size will be added to the stack size. The 5,119-character limit includes parameter names and separators (","). |
|||||||
An invalid value was specified as the additional size. The added size must be a decimal number, or a hexadecimal number preceded by "0x" or "0X". |
|||||||
An invalid value was specified as the number of recursions. Specify a positive number in decimal format, or in hexadecimal format preceded by "0x" or "0X". |
|||||||
The value specified as the additional size exceeds the limit (value). |
|||||||
Reduce the stack size, starting with the function with the largest path. |