Table of Contents
Advertisement
13.
Serial Bus Interface (I2C/SIO)
13.6
Data Transfer Procedure in the I2C Bus Mode
13.6.3.2
quest is generated, <PIN> is cleared to "0", and the SCL pin is pulled to the "Low" level.
ter a period of t
knowledgement signal depending on the contents of the second byte.
is carried out.
in the slave receiver mode.
INTSBI interrupt
if TRX = 0
Then go to other processing.
if AL = 0
Then go to other processing.
if AAS = 0
Then go to other processing.
SBICR1
SBIDBR
2019-02-06
Slave mode (<MST> = "0")
In the slave mode, the SBI generates the INTSBI interrupt request on four occasions:
1) when the SBI has received any slave address from the master.
2) when the SBI has received a general-call address.
3) when the received slave address matches its address.
4) when a data transfer has been completed in response to a general-call.
Also, if the SBI detects Arbitration Lost in the master mode, it switches to the slave mode.
Upon the completion of data word transfer in which Arbitration Lost is detected, the INTSBI interrupt re-
When data is written to or read from SBIDBR or when <PIN> is set to "1", the SCLx pin is released af-
.
LOW
However, the second byte of the general call is necessary to be controlled by software to generate an ac-
In the slave mode, the normal slave mode processing or the processing as a result of Arbitration Lost
SBISR<AL>, <TRX>, <AAS> and <ADO> are tested to determine the processing required.
"Table 13-2 Processing in Slave Mode"shows the slave mode states and required processing.
Example: When the received slave address matches the SBI's own address and the direction bit is "1"
←
X
X
X
1
←
X
X
X
X
Note: X; Don't care
0
X
X
X
Sets the number of bits to be transmitted.
X
X
X
X
Sets the transmit data.
Page 292
TMPM3V6/M3V4
Advertisement
Table of Contents
