Maxim Integrated
Page 6 of 24
1.1 Communicating with MAX32664C
A host should use the I
2
C bus to communicate with the MAX32664C (slave) using a series of
commands. A generic write command includes the following fields:
Slave_WriteAddress(1 byte)|Command_Family(1 byte)|Command_Index(1
byte)|Value(multiple bytes)
A generic response includes the following fields:
Slave_ReadAddress(1 byte)|Status(1 byte)|Value (multiple bytes)
Slave_WriteAddress
and
Slave_ReadAddress
are set to 0xAA and 0xAB, respectively.
The read status byte is an indicator of success (0x00) or failure as shown in
Table 1. Read Status Byte Value
STATUS BYTE
VALUE
DESCRIPTION
0x00
SUCCESS. The write transaction was successful.
0x01
ERR_UNAVAIL_CMD. Illegal Family Byte and/or Command Byte was used.
0x02
ERR_UNAVAIL_FUNC. This function is not implemented.
0x03
ERR_DATA_FORMAT. Incorrect number of bytes sent for the requested Family Byte.
0x04
ERR_INPUT_VALUE. Illegal configuration value was attempted to be set.
0x05
ERR_TRY_AGAIN. Device is busy. Try again.
0x80
ERR_BTLDR_GENERAL. General error while receiving/flashing a page during the
bootloader sequence.
0x81
ERR_BTLDR_CHECKSUM. Checksum error while decrypting/checking page data.
0x82
ERR_BTLDR_AUTH. Authorization error.
0x83
ERR_BTLDR_INVALID_APP. Application not valid.
0xFF
ERR_UNKNOWN. Unknown Error.
This document provides examples of commands for establishing communication with the
MAX32664B. For a complete list of commands and instructions for the I
2
C interface, see the