https://devzone.nordicsemi.com/f/nordic-q-a/22598/aes-ccm-and-sd130-132Hi, We&#39;re using nRF51822 and in the future we&#39;ll use nRF52832. We do use bluetooth, but as far as I know, we don&#39;t use encryption (code is based on the HRS example, and I removed anything regarding bonding). We&#39;d like to be able to use AES-CCM hardwareen-USTelligent Community 13Wed, 07 Jun 2017 12:40:03 GMThttps://devzone.nordicsemi.com/thread/88887?ContentTypeID=1Wed, 07 Jun 2017 12:40:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3d78102c-6185-48d0-a48e-4215a2ad355dbjorn-spockeli<p>Hi Jonathan,</p> <p>The CCM peripheral will be blocked from application access while the S130 SoftDevice is enabled, this is stated <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.sds/dita/softdevices/s130/sd_resource_reqs/hw_block_interrupt_vector.html?cp=3_7_2_0_6_0">here</a> in the S130 Product Specification.</p> <p>You can use the ECB peripheral to perform encryption while the SoftDevice is enabled, i.e. there are SoftDevice APIs for accessing it. However, if you need to use the AES-CCM peripheral you will need to either use the <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.sds/dita/softdevices/s130/concurrent_multiprotocol_tsl_api/concurrent_multiprotocol_tsl_api.html?cp=3_7_2_0_8_1">S130 Timeslot API</a> or disable the SoftDevice, use the AEs-CCM peripheral and then re-enable it when you&#39;re done. The latter implies that the BLE connection will be broken and you will have to reconnect after re-enabling the SoftDevice.</p> <p>Best regards</p> <p>Bjørn</p><div style="clear:both;"></div>