Slave Arbitration-Lost Detection (Sale Bit) - Renesas RX100 Series User Manual

RX13T Group
Condition for arbitration-lost during NACK transmission
 When the internal SDA output level does not match the SDA0 line (ACK is received) during transmission of NACK
(ICMR3.ACKBT bit = 1)
24.9.3

Slave Arbitration-Lost Detection (SALE Bit)

The RIIC has a function to cause arbitration to be lost if the data for transmission (i.e. the internal SDA output level) and
the level on the SDA0 line do not match (the high output as the internal SDA output; i.e. the SDA0 pin is in the high-
impedance state and the low level is detected on the SDA0 line in slave transmit mode). This arbitration-lost detection
function is mainly used when transmitting a UDID (Unique Device Identifier) over an SMBus.
When it loses slave arbitration, the RIIC is immediately released from the slave-matched state and enters slave receive
mode. This function can detect conflicts of data during transmission of UDIDs over an SMBus and eliminate subsequent
redundant processing (processing for the transmission of FFh).
The RIIC detects slave arbitration-lost when the following condition is met with the ICFER.SALE bit set to 1 (slave
arbitration-lost detection enabled).
Condition for slave arbitration-lost
 When transmit data excluding acknowledge (internal SDA output level) does not match the SDA0 line in slave
transmit mode (bits MST and TRS in the ICCR2 register are 01b)
[Conflict during data transmission]
2 3 4 5
SCL0
SDA0
Data
2 3 4 5
SCL0
SDA0
Data
BBSY
MST
TRS
AL
TDRE
Figure 24.36 Example of Slave Arbitration-Lost Detection (SALE = 1)
R01UH0822EJ0100 Rev.1.00
Jul 31, 2019
6 7 8 9 1
ACK
6 7 8 9 1
ACK
Write data to ICDRT register
Transmit data mismatch
(Arbitration lost)
2 3 4 5
1 1
2 3 4 5 6 7
0
Clear AL flag to 0
2
24. I C-bus Interface (RIICa)
Release SCL/SDA
8 9 1 2 3 3 4 4
ACK
Data
Page 788 of 1041
5 5 6 6