SC18IS600(2006) View Datasheet(PDF) - NXP Semiconductors.
Part Name
Description
Manufacturer
SC18IS600 Datasheet PDF : 28 Pages
| |||
NXP Semiconductors
SC18IS600/601
SPI to I2C-bus interface
6.6.2 Read N bytes from I2C-bus slave device
SPI host sends
0x01
NUMBER
COMMAND OF BYTES
SLAVE ADDRESS
+R
CS
SCLK
MOSI
command 0x01
number of bytes D[7:0] slave address A[7:1] 1
002aab719
Fig 13. Read N bytes from I2C-bus slave device
Once the host issues this command, the SC18IS600/601 will start an I2C-bus read
transaction on the I2C-bus to the specified slave address. Once the data is received, the
SC18IS600/601 will place this data in the receiver buffer, and will generate an interrupt on
the INT pin. The ‘transaction completed’ status can be read in the I2CStat. Note that the
data is not returned until a read buffer command is performed (see Section 6.6.4 “Read
buffer”).
Note that the third byte sent by the host is the device slave address. The SC18IS600/601
will ignore the least significant bit so a read will always be performed even if the least
significant bit is a ‘0’. The maximum number of bytes to be read is 96.
6.6.3 I2C-bus read after write
SPI host sends
0x02
COMMAND
NUMBER OF
WRITE
BYTES
NUMBER OF
READ
BYTES
SLAVE
ADDRESS
+W
DATA
WRITE
BYTE 0
Fig 14. I2C-bus read after write
DATA
WRITE
BYTE N
SLAVE
ADDRESS
+R
002aab720
Once the host issues this command, the SC18IS600/601 will start a write transaction on
the I2C-bus to the specified slave address. Once the data is written, the SC18IS600/601
will read data from the specified slave, place the data in the Receiver Buffer and generate
an interrupt on the INT pin. The ‘transaction completed’ status can be read in I2CStat.
Note that the data is not returned until a ‘read buffer’ command is performed.
6.6.4 Read buffer
Fig 15. Read buffer
SPI host sends
0x06
DATA
COMMAND BYTE 1
DATA
BYTE N
002aab868
SC18IS600_601_3
Product data sheet
Rev. 03 — 13 December 2006
© NXP B.V. 2006. All rights reserved.
13 of 28
Share Link: 