26.8.6 Status

Name: STATUS
Offset: 0x10
Reset: 0x0000
Property: -

Bit 15141312111098 
 SYNCBUSY        
Access R/W 
Reset 0 
Bit 76543210 
 CLKHOLDLOWTOUT SRDIRRXNACKCOLLBUSERR 
Access R/WR/WRRRR/WR/W 
Reset 0000000 

Bit 15 – SYNCBUSY Synchronization Busy

This bit is set when the synchronization of registers between clock domains is started.

This bit is cleared when the synchronization of registers between the clock domains is complete.

Bit 7 – CLKHOLD Clock Hold

The Client Clock Hold (STATUS.CLKHOLD) bit is set when the Client is holding the SCL line low, stretching the I2C clock. Software must consider this bit a read-only status flag that is set when INTFLAG.DRDY or INTFLAG.AMATCH is set.

This bit is cleared when the corresponding interrupt is cleared. If this bit is written as ‘1’ while the SCL line is held low, the SCL line will be released. Writing '0' to this bit has no effect.

Bit 6 – LOWTOUT SCL Low Time-out

This bit is set if an SCL low time-out occurs.

This bit is cleared automatically if responding to a new start condition with ACK or NACK (write 3 to CTRLB.CMD) or when INTFLAG.AMATCH is cleared.

Writing a '0' to this bit has no effect.

Writing a '1' to this bit will clear the status.

ValueDescription
0 No SCL low time-out has occurred.
1 SCL low time-out has occurred.

Bit 4 – SR Repeated Start

When INTFLAG.AMATCH is raised due to an address match, SR indicates a repeated start or start condition.

This flag is only valid while the INTFLAG.AMATCH flag is one.

ValueDescription
0 Start condition on last address match
1 Repeated start condition on last address match

Bit 3 – DIR Read / Write Direction

The Read/Write Direction (STATUS.DIR) bit stores the direction of the last address packet received from a Host.

ValueDescription
0 Host write operation is in progress.
1 Host read operation is in progress.

Bit 2 – RXNACK Received Not Acknowledge

This bit indicates whether the last data packet sent was acknowledged or not.

ValueDescription
0 Host responded with ACK.
1 Host responded with NACK.

Bit 1 – COLL Transmit Collision

If set, the I2C Client was not able to transmit a high data or NACK bit, the I2C Client will immediately release the SDA and SCL lines and wait for the next packet addressed to it.

This flag is intended for the SMBus address resolution protocol (ARP). A detected collision in non-ARP situations indicates that there has been a protocol violation, and should be treated as a bus error.

This status will not trigger any interrupt, and should be checked by software to verify that the data were sent correctly. This bit is cleared automatically if responding to an address match with an ACK or a NACK (writing 0x3 to CTRLB.CMD), or INTFLAG.AMATCH is cleared.

Writing a '0' to this bit has no effect.

Writing a '1' to this bit will clear the status.

ValueDescription
0 No collision detected on last data byte sent.
1 Collision detected on last data byte sent.

Bit 0 – BUSERR Bus Error

The Bus Error bit (STATUS.BUSERR) indicates that an illegal bus condition has occurred on the bus, regardless of bus ownership. An illegal bus condition is detected if a protocol violating start, repeated start or stop is detected on the I2C bus lines. A start condition directly followed by a stop condition is one example of a protocol violation. If a time-out occurs during a frame, this is also considered a protocol violation, and will set STATUS.BUSERR.

This bit is cleared automatically if responding to an address match with an ACK or a NACK (writing 0x3 to CTRLB.CMD) or INTFLAG.AMATCH is cleared.

Writing a '1' to this bit will clear the status.

Writing a '0' to this bit has no effect.

ValueDescription
0 No bus error detected.
1 Bus error detected.