<?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>AES CCM encryption by S132 timeslot API</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29142/aes-ccm-encryption-by-s132-timeslot-api</link><description>Hi, 
 I have posted the same question in the following URL.
 devzone.nordicsemi.com/.../ 
 It will be very helpful if you tell me how to get a correct MIC result by AES CCM mode encryption of nRF52832. 
 I send you my sample(blinky_ccm.zip). I&amp;#39;m using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 15 Jan 2018 10:18:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29142/aes-ccm-encryption-by-s132-timeslot-api" /><item><title>RE: AES CCM encryption by S132 timeslot API</title><link>https://devzone.nordicsemi.com/thread/115789?ContentTypeID=1</link><pubDate>Mon, 15 Jan 2018 10:18:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7fb61b3a-c7ce-497a-898b-7d5d616f54f0</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;What are you actually trying to do here? Calling ccm_crypt_pair_request_prepare doesn&amp;#39;t actually do anything, it only generates the pair_request_packet. This needs to be sent to the peer and applied there using the ccm_crypt_pair_request_accept function. Then you can use ccm_crypt_packet_encrypt to encrypt the packet, send it to the peer that can use ccm_crypt_packet_decrypt to un encrypt the packet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM encryption by S132 timeslot API</title><link>https://devzone.nordicsemi.com/thread/115788?ContentTypeID=1</link><pubDate>Thu, 28 Dec 2017 04:36:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b9effc89-256e-40c5-a00f-c4331193521c</guid><dc:creator>ALE</dc:creator><description>&lt;p&gt;Thank you for your comment. I have tried to call ccm_crypt_pair_request_prepare() for only one time after the first timeout. But it doesn`t work. We still cannot obtain the expected MIC . I have also tried to call ccm_crypt_pair_request_prepare() for only one time in the main(). And the MIC is also wrong.
Could you provide a sample so that I can get the expected MIC?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM encryption by S132 timeslot API</title><link>https://devzone.nordicsemi.com/thread/115787?ContentTypeID=1</link><pubDate>Wed, 20 Dec 2017 13:58:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ce9f09b-754f-48e1-a967-278a83d90556</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;As far as I can see you call ccm_crypt_pair_request_prepare every time the timer fires. Could you try to call this only once?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>