https://devzone.nordicsemi.com/f/nordic-q-a/53468/nrf_ecb-peripheral-does-not-always-generate-endecb-eventHi, We use the ECB peripheral to encrypt and decrypt data with a proprietary driver implementation (which is not that different from the one in the SDK). It is working fine most of the time, but on rare occasions it appears to hang while waiting foren-USTelligent Community 13Thu, 31 Oct 2019 08:30:13 GMThttps://devzone.nordicsemi.com/thread/217687?ContentTypeID=1Thu, 31 Oct 2019 08:30:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5eaee8aa-a3d8-45f6-86b9-38312b0aecd6faberd<p>Hi,</p> <p>Thank you for your response. Turned out we were suffering from a memory corruption bug, that caused this behavior. So it is no longer an issue.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/216063?ContentTypeID=1Tue, 22 Oct 2019 07:26:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5150743c-ce6a-4147-9fee-f41f4590ce66Einar Thorsrud<p>Hi,</p> <p>This should not happen, and I have not found any previous reports of this. The expected behavior is that ENDECB is always (and only) generated after the START task was triggered and block encryption has successfully been run to the end without being interrupted or corrupted. If not,&nbsp;ERRORECB should be generated. (Always one or the other).</p> <p>I am not aware of any other way of handling this since you write that you don&#39;t get the&nbsp;ERRORECB vent in this case (which should not happen). But you should get events every time. Could it be that you lose it in your firmware somehow? Missing consecutive interrupts, or putting the event in a queue with some issues or something similar?</p> <p>Do you have some code and a procedure that reproduces this on the DK?</p><div style="clear:both;"></div>