LPC47S457-NC SMSC [SMSC Corporation], LPC47S457-NC Datasheet - Page 136

• Manufacturer Part Number: LPC47S457-NC
• Description: Advanced I/O with X-Bus Interface
• Manufacturer: SMSC [SMSC Corporation]

6.18.1 SMBUS PROTOCOLS SUPPORTED BY SMBUS2
The SMBus2 supports two of the command protocols defined in the System Management Bus Specification, v1.1.
Note 1: In the Read Byte Protocol there is no stop condition before the repeated start condition, and a “Not
ACKnowledge” signifies the end of the read transfer.
6.18.2 COMMAND CODES
SMBus2 can access the SMBus2 Registers, nXCS0, XCS1, nXCS2, and nXCS3 through six predefined command
codes listed in the following table. The four MSB of the command code are used to identify which X-Bus device
should be accessed. The four LSB of the command code may be used as address or control bits and are mapped
directly to XA[3:0] (i.e., bit[0]=XA[0], bit[1]=XA[1], etc.)
LPC and SMBus2 arbitration registers control which interface is granted access to the X-Bus interface. Before the
SMBus initiates an I/O cycle on the X-Bus, it should request access to the X-Bus in the SMB_ARB Arbitration
Register located at offset 02h in the SMBus2 Registers. See 6.18.3 − X-Bus SMBus2/LPC Arbitration.
Note : When accessing the SMBus2 Registers, the four LSB are used as the address of the register that is to be read
from or written to. When accessing an LCD controller on XCS1, the four LSB are used to determine the type (i.e.,
Data/Command) and direction (i.e., R/W) of the transaction. It is important that the type and direction embedded in
the command code match the type and direction dictated by the SMBus protocol. Both of these SMBus transactions
require the Write Byte and Read Byte protocols.
SMSC LPC47S45x
S
Write Byte
Read Byte
After an SMBus transaction has been started, the first byte transmitted is always the Slave Address. Once a
device acknowledges ownership of the slave address, the next byte transmitted by the host/master is the
command code.
transferred with the most significant bit (MSB) first.
The Read Byte and Write Byte protocols are shown.
S
Slave Address
Slave Address
Each byte transferred on the bus must be followed by an acknowledge bit.
Wr
A
Command Code
Wr
FIGURE 10 − READ BYTE PROTOCOL
FIGURE 9 − WRITE BYTE PROTOCOL
Master to
Slave to
Master
A
Slave
DATASHEET
Command Code
Page 136 of 259
A
S
S
R/W = Read/Write
A
P
Slave Address
= Start
= Acknowledge
= Stop Condition
A
Rd
Data Byte
A
Data Byte
A
Rev. 06-01-06
Bytes are
P
A P