In some situations, e.g. if the external TWI master is not responding correctly, it may be required to terminate an ongoing transaction.
This can be achieved by triggering the STOP task. In this situation, a STOPPED event will be generated when the TWI has stopped independent of whether or not a STOP condition has been generated on the TWI bus. The TWI slave will release the bus when it has stopped and go back to its IDLE state.