Microchip Technology SA5 Series, User Manual

Page: 31 / 63

Command Line Interface

2019 Microchip Technology Inc. DS50002938A-page 31
A sequence number will be included in a response if one was provided in the command.
Similarly, a checksum will be included in a response if a checksum was given for the
command.
4.2.1 Error Responses
An error response indicates a problem with the command. It is identified by a ‘!’ char-
acter instead of ‘=’ following the optional message sequence number.
The following table lists all error numbers returned by the device:
#XX
The sequence number in the corresponding command (XX
= two hex digits).
Only when a
sequence
command is sent
=
The response type. A normal response type is indicated by
a ‘=’ character. An error response is indicated by a ‘!’ char-
acter.
Always
value
The response value. It may be a number, alphanumeric, or
quoted string. The meaning of the value depends upon the
command. Max Length is 4096 characters.
Always
|CC
The 8-bit checksum of the response message. (CC = two
hex digits).
Only when a
checksum
command is sent
]
Indicates the end of a response. Always
<CR>
A carriage return character. Always
<LF>
A linefeed/newline character. Always
TABLE 4-4: ERROR RESPONSES
Error Number Error Message Cause(s)
1 Invalid command Unrecognized command name, invalid syntax.
2 Insufficient arguments
Not enough arguments provided for the com-
mand.
3 Bad checksum
Checksum does not match the message
received.
100 Invalid parameter
The given parameter name or id is unrecog-
nized.
101 Invalid argument
One of the command arguments was semanti-
cally invalid. See the command’s documenta-
tion for details.
102 Read-only parameter
The parameter’s value cannot be written by the
user.
301, 303 Corrupt file contents The firmware file contents are corrupted.
302 Bad file checksum There was an error in the file transfer.
304 Incomplete file The firmware file contents are incomplete.
310
Transfer failed –
too many retries The file transfer was aborted after too many
retries.
311
Transfer failed –
canceled by client
The client aborted the file transfer.
312 Synchronization error A file transfer synchronization error occurred.
313
Transfer failed –
Unsupported request The file transfer was aborted due to an unsup-
ported request.
TABLE 4-3: RESPONSE STRUCTURE
Field Description Usage