https://devzone.nordicsemi.com/f/nordic-q-a/58453/memory-corruption-when-using-cryptocell310-s-aes-ccm-moduleHello, I am developing a driver that can handle cryptographic operations and I am using example code from nRF5_SDK_16.0.0_98a08e2 /examples/crypto/nrf_cc310/aes to get started with encryption using AES-CCM. While developing my driver, I came acrossen-USTelligent Community 13Wed, 04 Mar 2020 01:33:22 GMThttps://devzone.nordicsemi.com/thread/237896?ContentTypeID=1Wed, 04 Mar 2020 01:33:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1cbc18c1-796d-4ef5-bbdb-5b9406a2fc9agreenek<p>Thanks Jorgen. Using the nrf_crypto frontend with the CC310 backend solved these issues.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/237249?ContentTypeID=1Fri, 28 Feb 2020 20:21:50 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3294a158-b779-4bd5-87e5-a00c875258faJ&#248;rgen Holmefjord<p>Hi,</p> <p>1. This could maybe be related to the comment in&nbsp;components\libraries\crypto\backend\cc310\cc310_backend_aes_aead.c:</p> <p><pre class="ui-code" data-mode="c_cpp">/* CC310 backend always needs 16 bytes buffer for MAC calculation. */</pre></p> <p>In general, the CC310 API is quite hard to use, and there is not much checking if things are done correctly. We rather recommend using the nrf_crypto library, with the CC310 backend. This should do a lot more checking, to make sure every parameter and placement is valid.</p> <p>2. There should not be any problems with using the CC310 together with the softdevice.</p> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>