SW500009 Microchip Technology, SW500009 Datasheet - Page 362

• Manufacturer Part Number: SW500009
• Description: HI-TECH FOR DSPIC/PIC24
• Manufacturer: Microchip Technology
• Type: Compilerr
• Series: PIC24 & DsPICr

Specifications of SW500009

• Supported Families: PIC24
• Core Architecture: PIC, DsPIC
• Software Edition: Standard
• Kit Contents: Software And Docs
• Tool Type: Compiler
• Mcu Supported Families: PIC24 MCUs And DsPIC DSCs
• Lead Free Status / RoHS Status: Not applicable / RoHS Compliant
• For Use With/related Products: DSPIC3X/PIC24
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: 025; 778-1003; 778-1003

(524) unable to open list file "*": *
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 generated during the compilation
stage. Alternatively, remove the assembler list file generation option from the link step.
(525) too many address (memory) spaces; space (*) ignored
The limit to the number of address spaces (specified with the PSECT assembler directive) is currently
16.
(526) psect "*" not specified in -P option (first appears in "*")
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.
(528) no start record; entry point defaults to zero
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.
(529) usage: objtohex [-Ssymfile] [object-file [hex-file]]
Improper usage of the command-line tool objtohex. If you are invoking objtohex directly then
please refer to Section
you should contact HI-TECH Software technical support with details.
(593) can’t find 0x* words (0x* withtotal) for psect "*" in segment "*"
See error (491) on page 343.
(594) undefined symbol:
The symbol following is undefined at link time. This could be due to spelling error, or failure to link
an appropriate module.
(595) undefined symbols:
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.
348
5.13
for more details. Otherwise this may be an internal compiler error and
Error and Warning Messages
(Objtohex)
(Linker)
(Linker)
(Linker)
(Linker)
(Linker)
(Linker)
(Linker)