<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Crypto Engine</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39832/crypto-engine</link><description>Hello, 
 I would like to use the hardware crypto engine that is a part of nRF52832 chipset. I understand that the access to it is restricted as SoftDevice uses it. I wonder though whether I can freely access it if I don&amp;#39;t use security layer of BLE stack</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Oct 2018 06:38:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39832/crypto-engine" /><item><title>RE: Crypto Engine</title><link>https://devzone.nordicsemi.com/thread/154605?ContentTypeID=1</link><pubDate>Fri, 26 Oct 2018 06:38:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a74968c-078a-4671-8ef1-2c1b811f7276</guid><dc:creator>BarbaraTurner</dc:creator><description>&lt;p&gt;Thank you Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Crypto Engine</title><link>https://devzone.nordicsemi.com/thread/154452?ContentTypeID=1</link><pubDate>Thu, 25 Oct 2018 10:46:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0dde69fe-6922-49ee-a627-028a8f356ca2</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Barbara,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;As you can see from &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/sd_resource_reqs/hw_block_interrupt_vector.html?cp=2_3_1_0_6_0"&gt;Table 2. Peripheral protection and usage by SoftDevice&lt;/a&gt;, the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/ccm.html?cp=2_1_0_28#topic"&gt;AES CCM peripheral&lt;/a&gt; is blocked by the SoftDevice and cannot be used while it is enabled. This is regardless of whether it is in a encrypted BLE connection or not. The &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/ecb.html?cp=2_1_0_27#concept_vnj_kgy_xr"&gt;AES ECB peripheral&lt;/a&gt; on the other hand is &lt;em&gt;restricted&lt;/em&gt;, which means that it can only be used via the SoftDevice APIs. Therefore you have to use &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.0/group___n_r_f___s_o_c___f_u_n_c_t_i_o_n_s.html#ga79280d697e7ba03810c6473b0c7dab87"&gt;sd_ecb_block_encrypt()&lt;/a&gt;&amp;nbsp;or &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.0/group___n_r_f___s_o_c___f_u_n_c_t_i_o_n_s.html#ga30cc707e7aa4a73019fae00f8b4faa52"&gt;sd_ecb_blocks_encrypt()&lt;/a&gt;&amp;nbsp;instead of accessing the ECB HW registers directly.&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>