10-17
Configuring the Terminal
Invalid Image This error occurs if another record is received before the Header
Record. Ensure the Header Record is the first record downloaded.
Partition Not Defined The destination code is part of the Header record and is used as an
index into the partition table. The partition table entry located at this
index contains partition information for the data downloaded. If the
AutoSelect option is selected, a check is made to ensure that valid
partition information exists in the partition table at this index. The
check verifies that the Area Name and Sector Size are both non-zero.
If not, this error occurs.
Wrong Pa rtiti on If a specific partition is selected from the partition list, and the
destination code of the Header record downloaded does not match
the index of that partition, this error occurs.
Image Too Big The size of the image is also part of the Header record. If the data to
be written exceeds the size of the partition as indicated in the
partition table, this error occurs.
Incorrect Byte Count Image data is processed until the End Of File (EOF - Record Type 01)
record is received. This error occurs if IPL detects that the number of
bytes received does not equal the number of bytes sent.
Unable to Verify Partition Data If the Receive and Verify bit is set for that partition, the data is
verified, the flash sector erased, and the data written to the flash part.
If this data can not be verified, this error occurs.
Transmission Errors The following erro r messages may appear if an error occurs during
transmission:
Checksum Error occurs if an invalid checksum is detected in the
record.
Invalid Record occurs if a record is not defined in the Symbol Hex
File Format.
Connection Lost occurs if one of the handshaking lines is de-asserted
during download.
Address Out of Sequence occurs if the address of the data received is
not sequential.