Microchip Technology XC8 Standard Compiler (Workstation) SW006021-1 SW006021-1 ユーザーズマニュアル
製品コード
SW006021-1
Error and Warning Messages
2012 Microchip Technology Inc.
DS52053B-page 425
(522) library "*" is badly ordered
(Linker)
This library is badly ordered. It will still link correctly, but it will link faster if better
ordered.
ordered.
(523) argument to -W option (*) illegal and ignored
(Linker)
The argument to the linker option -w is out of range. This option controls two features.
For warning levels, the range is -9 to 9. For the map file width, the range is greater than
or equal to 10.
For warning levels, the range is -9 to 9. For the map file width, the range is greater than
or equal to 10.
(524) unable to open list file "*": *
(Linker)
The named list file could not be opened. The linker would be trying to fixup the list file
so that it will contain absolute addresses. Ensure that an assembler list file was gener-
ated during the compilation stage. Alternatively, remove the assembler list file
generation option from the link step.
so that it will contain absolute addresses. Ensure that an assembler list file was gener-
ated during the compilation stage. Alternatively, remove the assembler list file
generation option from the link step.
(525) too many address (memory) spaces; space (*) ignored
(Linker)
The limit to the number of address spaces (specified with the PSECT assembler
directive) is currently 16.
directive) is currently 16.
(526) psect "*" not specified in -P option (first appears in "*")
(Linker)
This psect was not specified in a -P or -A option to the linker. It has been linked at the
end of the program, which is probably not where you wanted it.
end of the program, which is probably not where you wanted it.
(528) no start record; entry point defaults to zero
(Linker)
None of the object files passed to the linker contained a start record. The start address
of the program has been set to zero. This may be harmless, but it is recommended that
you define a start address in your startup module by using the END directive.
of the program has been set to zero. This may be harmless, but it is recommended that
you define a start address in your startup module by using the END directive.
(529) usage: objtohex [-Ssymfile] [object-file [HEX-file]]
(Objtohex)
Improper usage of the command-line tool objtohex. If you are invoking objtohex
directly then refer to Section 8.3 “OBJTOHEX” for more details. Otherwise, this may
be an internal compiler error and you should contact Microchip Technical Support with
details.
directly then refer to Section 8.3 “OBJTOHEX” for more details. Otherwise, this may
be an internal compiler error and you should contact Microchip Technical Support with
details.
(593) can’t find 0x* words (0x* withtotal) for psect "*" in segment "*"
(Linker)
See message (491).
(594) undefined symbol:
(Linker)
The symbol following is undefined at link time. This could be due to spelling error, or
failure to link an appropriate module.
failure to link an appropriate module.
(595) undefined symbols:
(Linker)
A list of symbols follows that were undefined at link time. These errors could be due to
spelling error, or failure to link an appropriate module.
spelling error, or failure to link an appropriate module.
(596) segment "*" (*-*) overlaps segment "*" (*-*)
(Linker)
The named segments have overlapping code or data. Check the addresses being
assigned by the -P linker option.
assigned by the -P linker option.
(599) No psect classes given for COFF write
(Cromwell)
CROMWELL
requires that the program memory psect classes be specified to produce a
COFF file. Ensure that you are using the -N option as per Section 8.5.2 “-N”.