Microchip Technology XC8 Standard Compiler (Workstation) SW006021-1 SW006021-1 User Manual
Product codes
SW006021-1
MPLAB
®
XC8 C Compiler User’s Guide
DS52053B-page 450
2012 Microchip Technology Inc.
(944) data conflict at address *h between * and *
(Hexmate)
Sources to Hexmate request differing data to be stored to the same address. To force
one data source to override the other, use the ’+’ specifier. If the two named sources of
conflict are the same source, then the source may contain an error.
one data source to override the other, use the ’+’ specifier. If the two named sources of
conflict are the same source, then the source may contain an error.
(945) checksum range (*h to *h) contained an indeterminate value
(Hexmate)
The range for this checksum calculation contained a value that could not be resolved.
This can happen if the checksum result was to be stored within the address range of
the checksum calculation.
This can happen if the checksum result was to be stored within the address range of
the checksum calculation.
(948) checksum result width must be between 1 and 4 bytes
(Hexmate)
The requested checksum byte size is illegal. Checksum results must be within 1 to 4
bytes wide. Check the parameters to the -CKSUM option.
bytes wide. Check the parameters to the -CKSUM option.
(949) start of checksum range must be less than end of range
(Hexmate)
The -CKSUM option has been given a range where the start is greater than the end.
The parameters may be incomplete or entered in the wrong order.
The parameters may be incomplete or entered in the wrong order.
(951) start of fill range must be less than end of range
(Hexmate)
The -FILL option has been given a range where the start is greater than the end. The
parameters may be incomplete or entered in the wrong order.
parameters may be incomplete or entered in the wrong order.
(953) unknown -HELP sub-option: *
(Hexmate)
Invalid sub-option passed to -HELP. Check the spelling of the sub-option or use -HELP
with no sub-option to list all options.
with no sub-option to list all options.
(956) -SERIAL value must be between 1 and * bytes long
(Hexmate)
The serial number being stored was out of range. Ensure that the serial number can be
stored in the number of bytes permissible by this option.
stored in the number of bytes permissible by this option.
(958) too many input files specified; * file maximum
(Hexmate)
Too many file arguments have been used. Try merging these files in several stages
rather than in one command.
rather than in one command.
(960) unexpected record type (*) on line * of "*"
(Hexmate)
Intel HEX file contained an invalid record type. Consult the Intel HEX format
specification for valid record types.
specification for valid record types.
(962) forced data conflict at address *h between * and *
(Hexmate)
Sources to HEXMATE force differing data to be stored to the same address. More than
one source using the ’+’ specifier store data at the same address. The actual data
stored there may not be what you expect.
one source using the ’+’ specifier store data at the same address. The actual data
stored there may not be what you expect.
(963) checksum range includes voids or unspecified memory locations
(Hexmate)
Checksum range had gaps in data content. The runtime calculated checksum is likely
to differ from the compile-time checksum due to gaps/unused byes within the address
range that the checksum is calculated over. Filling unused locations with a known value
will correct this.
to differ from the compile-time checksum due to gaps/unused byes within the address
range that the checksum is calculated over. Filling unused locations with a known value
will correct this.
(964) unpaired nibble in -FILL value will be truncated
(Hexmate)
The hexadecimal code given to the FILL option contained an incomplete byte. The
incomplete byte (nibble) will be disregarded.
incomplete byte (nibble) will be disregarded.