NXP Semiconductors
SC18IS602/602B/603
I2C-bus to SPI bridge
the Function ID. There is no restriction on the number or combination of Slave Selects that
can be enabled for an SPI message. If more than one SSn pin is enabled at one time, the
user should be aware of possible contention on the data outputs of the SPI slave devices.
Table 3. Function ID 01h to 0Fh
7
6
5
4
0
0
0
0
3
SS3[1]
2
SS2[2]
1
SS1
0
SS0
[1] SS3 does not exist in the SC18IS603.
[2] SS2 does not exist in the SC18IS602 and SC18IS603. Only SC18IS602B supports this function.
The data on the SPI port will contain the same information as the I2C-bus data, but without
the slave address and Function ID. For example, if the message shown in Figure 7 is
transmitted on the I2C-bus, the SPI bus will send the message shown in Figure 8.
write to buffer
S
SLAVE ADDRESS W A
FUNCTION
ID
A
DATA 1
A
Fig 7. I2C-bus message
A DATA n A P
002aac448
SPI data
DATA 1
DATA n
002aac451
Fig 8. SPI message
The SC18IS602/602B/603 counts the number of data bytes sent to the I2C-bus port and
will automatically send this same number of bytes to the SPI bus. As the data is
transmitted from the MOSI pin, it is also read from the MISO pin and saved in the data
buffer. Therefore, the old data in the buffer is overwritten. The data in the buffer can then
be read back.
If the data from the SPI bus needs to be returned to the I2C-bus master, the process must
be completed by reading the data buffer. Section 8 gives an example of an SPI read.
7.1.4 Read from buffer
A read from the data buffer requires no Function ID. The slave address with the R/W bit
set to a ‘1’ will cause the SC18IS602/602B/603 to send the buffer contents to the I2C-bus
master. The buffer contents are not modified during the read process.
S SLAVE ADDRESS R A DATA 1 A
A DATA n NA P
002aac449
Fig 9. Read from buffer
A typical write and read from an SPI EEPROM is shown in Section 8.
SC18IS602_602B_603_4
Product data sheet
Rev. 04 — 11 March 2008
© NXP B.V. 2008. All rights reserved.
6 of 25