5.1 Messages

(294) can’t allocate * bytes of memory

This is an internal application error. Contact Microchip Technical Support with details.

(378) can’t create * file “*”

This type of file could not be created. Is the file, or a file by this name, already in use?

(636) error in Intel HEX file “*” on line *

An error was found at the specified line in the specified Intel HEX file. The HEX file may be corrupt.

(941) bad “*” assignment; USAGE: **

An option to Hexmate was incorrectly used or incomplete. Follow the usage supplied by the message and ensure that the option has been formed correctly and completely.

(942) unexpected character on line * of file “*”

File contains a character that was not valid for this type of file, the file can be corrupt. For example, an Intel HEX file is expected to contain only ASCII representations of hexadecimal digits, colons (:) and line formatting. The presence of any other characters will result in this error.

(944) data conflict at address *h between * and *

Sources to Hexmate requested differing data to be stored to the same address. To force one data source to override the other, use the ‘+’ specifier with that source. If the two named sources of conflict are the same source, then the source can contain an error.

(945) range (*h to *h) contained an indeterminate value

The range for this calculation contained a value that could not be resolved. This can happen if the result was to be stored within the address range of the calculation.

(948) result width must be between 1 and 4 bytes

The requested byte size is illegal. Checksum results must be within 1 to 4 bytes wide. Check the parameters to the -CK option.

(949) start of range must be less than end of range

The -CK option has been given a range where the start is greater than the end. The parameters can be incomplete or entered in the wrong order.

(951) start of fill range must be less than end of range

The -FILL option has been given a range where the start is greater than the end. The parameters can be incomplete or entered in the wrong order.

(953) unknown -HELP sub-option: *

Invalid sub-option passed to -HELP. Check the spelling of the sub-option or use -HELP with no sub-option to list all options.

(956) -SERIAL value must be between 1 and * bytes long

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.

(958) too many input files specified; * file maximum

Too many file arguments have been used. Try merging these files in several stages rather than in one command.

(960) unexpected record type (*) on line * of “*”

Intel HEX file contained an invalid record type. Consult the Intel HEX format specification for valid record types.

(962) forced data conflict at address *h between * and *

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 cannot be what you expect.

(963) range includes voids or unspecified memory locations

The hash (checksum) range had gaps in data content. The runtime hash calculated is likely to differ from the compile-time hash due to gaps/unused byes within the address range that the hash is calculated over. Filling unused locations with a known value will correct this.

(964) unpaired nibble in -FILL value will be truncated

The hexadecimal code given to the -FILL option contained an incomplete byte. The incomplete byte (nibble) will be disregarded.

(965) -STRPACK option not yet implemented; option will be ignored

This option currently is not available and will be ignored.

(966) no END record for HEX file “*”

Intel HEX file did not contain a record of type END. The HEX file can be incomplete.

(1030) Hexmate - Intel HEX editing utility (Build 1.%i)

Indicating the version number of the Hexmate being executed.

(1031) USAGE: * [input1.HEX] [input2.HEX]... [inputN.HEX] [options]

The suggested usage of Hexmate.

(1032) use –HELP=<option> for usage of these command line options

More detailed information is available for a specific option by passing that option to the -HELP option.

(1033) available command-line options:

This is a simple heading that appears before the list of available options for this application.

(1034) type “*” for available options

It looks like you need help. This advisory suggests how to get more information about the options available to this application or the usage of these options.

(1198) too many “*” specifications; * maximum

This option has been specified too many times. If possible, try performing these operations over several command lines.

(1200) Found %0*lXh at address *h

The code sequence specified in a -FIND option has been found at this address.

(1201) all FIND/REPLACE code specifications must be of equal width

All find, replace and mask attributes in this option must be of the same byte width. Check the parameters supplied to this option. For example, finding 1234h (2 bytes) masked with FFh (1 byte) results in an error; but, masking with 00FFh (2 bytes) works.

(1202) unknown format requested in -FORMAT: *

An unknown or unsupported INHX format has been requested. Refer to documentation for supported INHX formats.

(1203) unpaired nibble in * value will be truncated

Data to this option was not entered as whole bytes. Perhaps the data was incomplete or a leading zero was omitted. For example, the value Fh contains only four bits of significant data and is not a whole byte. The value 0Fh contains eight bits of significant data and is a whole byte.

(1204) * value must be between 1 and * bytes long

An illegal length of data was given to this option. The value provided to this option exceeds the maximum or minimum bounds required by this option.

(1212) Found * (%0*lXh) at address *h

The code sequence specified in a -FIND option has been found at this address.

(1245) value greater than zero required for *

The align operand to the Hexmate -FIND option must be positive.

(1600) "*" argument : *

There is an error in an argument to a Hexmate option. The message indicates the offending argument and the problem.

(1601) "*" argument : *

There is a warning in an argument to a Hexmate option. The message indicates the offending argument and the potential problem.

(1602) contents of the hex-data (*) do not conform with the chosen output type (*)

There is data to be written to the HEX file that is not valid for the particular HEX file format chosen, for example, data might be at an address too large for the supported format. Consider a different output format or check the source of the offending data.

(1606) w[no-]error option has been passed an invalid or missing message identifier (Hexmate)

hexmate --werror=off -format=inhx32 main.hex -ofinal.hex

(2059) conflicting * register values found in Start Segment Address record (3)

Hexmate will pass through any type 3 records in the Hex files being processed, but if there is any conflict in the values specified for the CS or IP registers in these records, it will flag this error.

(2060) CRC polynomial unspecified or set to 0

If you are calculating a CRC hash value using Hexmate and the polynomial value is zero, this warning will be triggered to indicate that you will be getting a trivial hash result. Typically this will occur if you have forgotten to set the polynomial value in the checksum option.

(2061) word width required when specifying reserve byte order hash

If you are calculating a CRC reading data words in the Hex file in reverse order, you must specify a word width in bytes with Hexmate's r suboption to -CK. If you are using the Hexmate driver, this is specified using the revword suboption to -mchecksum.

(2062) word width must be * when specifying reserve byte order hash

If you are calculating a CRC reading data words in the Hex file in reverse order, the word width can only be one of the values indicated in the message. This value is specified with Hexmate's r suboption to -CK. If you are using the Hexmate driver, this is specified using the revword suboption to -mchecksum.

(2063) * address must be a multiple of the word width when performing a reverse byte order hash

If you are calculating a CRC reading data words in the Hex file in reverse order, the starting and ending addresses must be multiples of the word width specified in Hexmate's -CK option or the Hexmate's -mchecksum option.

(2071) could not find record containing hash starting address 0x*

Hexmate was asked to calculate a hash from data starting at an address that did not appear in the HEX file.

(2072) only SHA256 is currently supported (set width control to 256)

The width suboption can only be set to 256 or -256 when selecting a SHA hash algorithm. Alternatively, the width suboption can be omitted entirely.

(2074) word size for byte skip with hash calculation must be *

The argument to the s suboption of -CK, which indicates the size of the word in which bytes will be skipped or the purposes of calculating a hash value is not permitted.

hexmate main.hex -ck=0-ff@100+ffffg5w-2p1021s1

Oops, the argument to s must be larger than 1.

(2075) word size required when requesting byte skip with hash calculation

An argument to the s suboption of -CK is required. It represents the word width in which bytes will be skipped for the purposes of calculating a hash value.

hexmate main.hex -ck=0-ff@100+ffffg5w-2p1021s.2

Oops, a number is required after the s, for example s4.2.

(2076) number of bytes for byte skip with hash calculation must be *

The number of bytes to skip within each word is illegal.

hexmate main.hex -ck=0-ff@100+ffffg5w-2p1021s4.4

Oops, the number of bytes to skip must be less than 4, the skip word width, for example s4.2.

(2077) number of bytes required when requesting byte skip with hash calculation

An argument following the . in the s suboption of -CK is required. It represents the number of bytes to skip in each word for the purposes of calculating a hash value.

hexmate main.hex -ck=0-ff@100+ffffg5w-2p1021s4.

Oops, a number is required after the . in the s argument, for example s4.2.

(2078) the number of hash bytes to which the trailing code is appended (*) must be no greater than the hash width (*)

A trailing code has been requested to follow the specified number of bytes of the hash value, but this number is larger than that the entire hash.

hexmate main.hex -ck=0-ff@100+ffffg5w-2p1021t00.4

Oops, if the hash value is only 2 bytes long, asking for a trailing code to be appended after every 4 bytes makes no sense. Instead try t00.1, for example, to append the code to each byte.

(2079) the hash width (*) must be a multiple of the number of hash bytes appended with a trailing code (*)

A trailing code has been requested to follow the specified number of bytes of the hash value, but this number is not a multiple of the hash width.

hexmate main.hex -ck=0-ff@100+ffffg5w-4p1021t00.3

Oops, if the hash value is 4 bytes long, asking for a trailing code to be appended after every 3 bytes makes no sense. Instead try t00.2, for example, to append the code to every two bytes of the hash.