This anomaly applies to Revision 2, build code CAAA-Bxx.
It was inherited from the previous SoC revision Revision 1.
Symptoms
STOPPED event is set after clearing it.
Conditions
The STOP task is triggered during a transaction.
Consequences
STOPPED event occurs twice: When the STOP task is fired and when the master issues a stop condition on the bus. This could provoke an extra interrupt or a failure in the TWIS driver.
Workaround
The last STOPPED event must be accounted for in software.